4,000+ servers built on vurb.ts
Vinkius

Apache APISIX MCP Server for CrewAIGive CrewAI instant access to 50 tools to Delete Consumer, Delete Consumer Group, Delete Global Rule, and more

MCP Inspector GDPR Free for Subscribers

Connect your CrewAI agents to Apache APISIX through Vinkius, pass the Edge URL in the `mcps` parameter and every Apache APISIX tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Ask AI about this MCP Server for CrewAI

The Apache APISIX MCP Server for CrewAI is a standout in the Loved By Devs category — giving your AI agent 50 tools to work with, ready to go from day one.

Built for AI Agents by Vinkius

Vinkius delivers Streamable HTTP and SSE to any MCP client

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
python
from crewai import Agent, Task, Crew

agent = Agent(
    role="Apache APISIX Specialist",
    goal="Help users interact with Apache APISIX effectively",
    backstory=(
        "You are an expert at leveraging Apache APISIX tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in Apache APISIX "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 50 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)
Apache APISIX
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Apache APISIX MCP Server

Connect your Apache APISIX instance to any AI agent to orchestrate high-performance traffic management through natural language.

When paired with CrewAI, Apache APISIX becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Apache APISIX tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

What you can do

  • Route Orchestration — List, inspect, create, or delete routes to match client requests and forward them to target upstreams.
  • Service Abstraction — Manage service entities that group common plugins and upstream configurations for easier API maintenance.
  • Upstream Management — Configure virtual host abstractions for load balancing, including node management and health checks.
  • Consumer Control — List and manage API consumers to handle authentication and per-user rate limiting.
  • Configuration as Conversation — Update complex JSON configurations for any gateway resource without manually using CURL or the Dashboard.

The Apache APISIX MCP Server exposes 50 tools through the Vinkius. Connect it to CrewAI in under two minutes — credentials fully managed, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

All 50 Apache APISIX tools available for CrewAI

When CrewAI connects to Apache APISIX through Vinkius, your AI agent gets direct access to every tool listed below — spanning api-gateway, traffic-management, cloud-native, and more. Every call runs in a secure, isolated environment with full audit visibility. Beyond a simple connection, you get real-time monitoring of agent activity, enterprise governance, and optimized token usage.

delete

Delete consumer on Apache APISIX

Delete an APISIX Consumer

delete

Delete consumer group on Apache APISIX

Delete an APISIX Consumer Group

delete

Delete global rule on Apache APISIX

Delete an APISIX Global Rule

delete

Delete plugin config on Apache APISIX

Delete an APISIX Plugin Config

delete

Delete proto on Apache APISIX

Delete an APISIX Proto

delete

Delete route on Apache APISIX

Delete an APISIX Route

delete

Delete service on Apache APISIX

Delete an APISIX Service

delete

Delete ssl on Apache APISIX

Delete an APISIX SSL certificate

delete

Delete stream route on Apache APISIX

Delete an APISIX Stream Route

delete

Delete upstream on Apache APISIX

Delete an APISIX Upstream

dump

Dump control discovery on Apache APISIX

Memory dump of discovered service endpoints

dump

Dump control plugin metadatas on Apache APISIX

Dump all plugin metadata from the Control API

dump

Dump control routes on Apache APISIX

Dump all configured Routes from the Control API

dump

Dump control services on Apache APISIX

Dump all configured Services from the Control API

dump

Dump control upstreams on Apache APISIX

Dump all configured Upstreams from the Control API

get

Get consumer on Apache APISIX

Get a specific APISIX Consumer by username

get

Get consumer group on Apache APISIX

Get a specific APISIX Consumer Group by ID

get

Get control healthcheck on Apache APISIX

Get health status of all upstream nodes

get

Get control resource healthcheck on Apache APISIX

Get health status for a specific resource

get

Get control schema on Apache APISIX

Get JSON schemas for all resources and enabled plugins

get

Get global rule on Apache APISIX

Get a specific APISIX Global Rule by ID

get

Get plugin config on Apache APISIX

Get a specific APISIX Plugin Config by ID

get

Get proto on Apache APISIX

Get a specific APISIX Proto by ID

get

Get route on Apache APISIX

Get a specific APISIX Route by ID

get

Get service on Apache APISIX

Get a specific APISIX Service by ID

get

Get ssl on Apache APISIX

Get a specific APISIX SSL certificate by ID

get

Get stream route on Apache APISIX

Get a specific APISIX Stream Route by ID

get

Get upstream on Apache APISIX

Get a specific APISIX Upstream by ID

list

List consumer groups on Apache APISIX

List APISIX Consumer Groups

list

List consumers on Apache APISIX

List APISIX Consumers

list

List global rules on Apache APISIX

List APISIX Global Rules

list

List plugin configs on Apache APISIX

List APISIX Plugin Configs

list

List protos on Apache APISIX

List APISIX Protos (Protocol Buffers)

list

List routes on Apache APISIX

List APISIX Routes

list

List services on Apache APISIX

List APISIX Services

list

List ssls on Apache APISIX

List APISIX SSL certificates

list

List stream routes on Apache APISIX

List APISIX Stream Routes (L4 routing)

list

List upstreams on Apache APISIX

List APISIX Upstreams

put

Put consumer on Apache APISIX

Create or update an APISIX Consumer

put

Put consumer group on Apache APISIX

Create or update an APISIX Consumer Group

put

Put global rule on Apache APISIX

Create or update an APISIX Global Rule

put

Put plugin config on Apache APISIX

Create or update an APISIX Plugin Config

put

Put proto on Apache APISIX

Create or update an APISIX Proto

put

Put route on Apache APISIX

Create or update an APISIX Route

put

Put service on Apache APISIX

Create or update an APISIX Service

put

Put ssl on Apache APISIX

Create or update an APISIX SSL certificate

put

Put stream route on Apache APISIX

Create or update an APISIX Stream Route

put

Put upstream on Apache APISIX

Create or update an APISIX Upstream

reload

Reload control plugins on Apache APISIX

Trigger a hot reload of plugins

trigger

Trigger control gc on Apache APISIX

Trigger full garbage collection in the HTTP Lua VM

Connect Apache APISIX to CrewAI via MCP

Follow these steps to wire Apache APISIX into CrewAI. The entire setup takes under two minutes — your credentials stay safe behind Vinkius.

01

Install CrewAI

Run pip install crewai
02

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com
03

Customize the agent

Adjust the role, goal, and backstory to fit your use case
04

Run the crew

Run python crew.py. CrewAI auto-discovers 50 tools from Apache APISIX

Why Use CrewAI with the Apache APISIX MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Apache APISIX through the Model Context Protocol.

01

Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

02

CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

03

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

04

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

Apache APISIX + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Apache APISIX MCP Server delivers measurable value.

01

Automated multi-step research: a reconnaissance agent queries Apache APISIX for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

02

Scheduled intelligence reports: set up a crew that periodically queries Apache APISIX, analyzes trends over time, and generates executive briefings in markdown or PDF format

03

Multi-source enrichment pipelines: chain Apache APISIX tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

04

Compliance and audit automation: a compliance agent queries Apache APISIX against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Example Prompts for Apache APISIX in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with Apache APISIX immediately.

01

"List all active routes in my APISIX gateway."

02

"Show me the configuration for upstream ID 'backend-cluster'."

03

"List all consumers to check who has access to the API."

Troubleshooting Apache APISIX MCP Server with CrewAI

Common issues when connecting Apache APISIX to CrewAI through Vinkius, and how to resolve them.

01

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.
02

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".
03

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.
04

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Apache APISIX + CrewAI FAQ

Common questions about integrating Apache APISIX MCP Server with CrewAI.

01

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.
02

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.
03

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.
04

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.
05

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.

Explore More MCP Servers

View all →