How to Use the Apache APISIX MCP in CrewAI

Q: Can CrewAI agents modify Apache APISIX global rules?

They can access putglobalrule if you grant the tool permission. The agents decide when to apply these rules based on the goals you set for the crew.

Deploy autonomous agent crews to monitor and defend your Apache APISIX infrastructure.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Apache APISIX MCP to CrewAI

Create your Vinkius account to connect Apache APISIX to CrewAI and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Apache APISIX with CrewAI

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Autonomous gateway monitoring with CrewAI

Assign a dedicated monitor agent to watch your gateway. It calls `get_control_healthcheck` constantly and alerts the main crew if nodes start showing latency. The crew acts on the data immediately. They can use `put_upstream` to divert traffic away from failing hardware before your users notice an issue.

Manage gateway protos and plugins

Your research agent can list current configurations using `list_protos` or `list_plugin_configs`. If it finds outdated definitions, it flags them for the moderator agent. The moderator verifies the change and executes `put_proto` to update your gateway. It turns a tedious manual task into a background background process.

Secure your API with agent crews

Deploy a security-focused agent to audit SSL certificates. It calls `list_ssls` and checks expiration dates against your internal policy. If a certificate is close to expiring, the agent triggers `put_ssl` to rotate it. It keeps your gateway secure without you needing to track calendars.

Setup guide

Set up Apache APISIX MCP in CrewAI

Prerequisites

Python 3.10+ installed
crewai package (pip install crewai)
Active Vinkius subscription with a valid endpoint token

1

Install CrewAI
Run pip install crewai to install the framework. MCP support is built-in via the mcps parameter.
2

Add the MCP URL to your agent
Pass your Vinkius endpoint directly to the mcps list. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. CrewAI handles tool discovery and caching automatically.
3

Kick off your crew
Create a Crew with your agent and tasks. Call crew.kickoff() — the agent will automatically invoke Apache APISIX tools as needed.

crew.py

from crewai import Agent, Task, Crew

agent = Agent(
    role="Apache APISIX Analyst",
    goal="Access and analyze Apache APISIX data via MCP.",
    backstory="Expert analyst with direct Apache APISIX access.",
    mcps=[
        "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    ],
)

task = Task(
    description="List recent Apache APISIX transactions",
    agent=agent,
    expected_output="A summary of recent activity",
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Get your connection token →

Prerequisites

Python 3.10+ installed
crewai + crewai-tools packages
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install crewai crewai-tools. The MCPServerAdapter handles lifecycle management and tool conversion.
2

Connect with MCPServerAdapter
Use MCPServerAdapter as a context manager with SseServerParameters pointing to your Vinkius endpoint. The adapter automatically manages connection lifecycle.
3

Assign tools and run
Pass the returned mcp_tools to your agent's tools parameter. The adapter converts MCP tools to native BaseTool objects compatible with all CrewAI agents.

crew.py

from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
from mcp import SseServerParameters

server_params = SseServerParameters(
    url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)

with MCPServerAdapter(server_params) as mcp_tools:
    agent = Agent(
        role="Apache APISIX Analyst",
        goal="Access and analyze Apache APISIX data via MCP.",
        backstory="Expert analyst with direct Apache APISIX access.",
        tools=mcp_tools,
    )

    task = Task(
        description="List recent Apache APISIX transactions",
        agent=agent,
        expected_output="A summary of recent activity",
    )

    crew = Crew(agents=[agent], tasks=[task])
    result = crew.kickoff()
    print(result)

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Apache APISIX. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Apache APISIX now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Apache APISIX MCP in CrewAI

You assign specific toolsets to your agents. One agent uses `get_route` to find issues, while another uses `put_route` to fix them, creating a collaborative loop.

They can access `put_global_rule` if you grant the tool permission. The agents decide when to apply these rules based on the goals you set for the crew.

You limit which tools each agent can access. An analyst agent might only get `get_upstream` and `list_services`, while your admin agent gets the write tools.

The gateway API processes requests in order. CrewAI manages the execution sequence to prevent conflicts when multiple agents try to update the same resource.

The MCP Server environment is isolated. Only your defined agents can request `dump_control_routes` or other sensitive config data, ensuring your gateway setup stays private.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript