CrewAIFramework

Apache APISIX MCP Server

Bring Api Gateway
to CrewAI

Name: Apache APISIX MCP Server
Price: 29 USD
Availability: InStock
Rating: 0.2 (1 reviews)
Author: Vinkius

Learn how to connect Apache APISIX to CrewAI and start using 50 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

GDPR Free for Subscribers

Delete ConsumerDelete Consumer GroupDelete Global RuleDelete Plugin ConfigDelete ProtoDelete RouteDelete ServiceDelete SslDelete Stream RouteDelete UpstreamDump Control DiscoveryDump Control Plugin MetadatasDump Control RoutesDump Control ServicesDump Control UpstreamsGet ConsumerGet Consumer GroupGet Control HealthcheckGet Control Resource HealthcheckGet Control SchemaGet Global RuleGet Plugin ConfigGet ProtoGet RouteGet ServiceGet SslGet Stream RouteGet UpstreamList Consumer GroupsList ConsumersList Global RulesList Plugin ConfigsList ProtosList RoutesList ServicesList SslsList Stream RoutesList UpstreamsPut ConsumerPut Consumer GroupPut Global RulePut Plugin ConfigPut ProtoPut RoutePut ServicePut SslPut Stream RoutePut UpstreamReload Control PluginsTrigger Control Gc

Unlock for AI Agents

Ask AI about this MCP Server ChatGPT Claude Perplexity

Compatible with every major AI agent and IDE

Claude

ChatGPT

Cursor

Gemini

Windsurf

VS Code

JetBrains

Vercel

+ other MCP clients

What is the Apache APISIX MCP Server?

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

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.

How it works

Subscribe to this server
Provide your APISIX Admin URL and Admin Key (X-API-KEY)
Start managing your microservices infrastructure from Claude, Cursor, or any MCP client

Who is this for?

DevOps Engineers — quickly audit routing rules and upstream health directly from the terminal or chat.
Backend Developers — create and test new API routes and service abstractions without leaving the IDE.
SRE Teams — troubleshoot traffic flow and consumer access issues using natural language queries.

Built-in capabilities (50)

delete_consumer

Delete an APISIX Consumer

delete_consumer_group

Delete an APISIX Consumer Group

delete_global_rule

Delete an APISIX Global Rule

delete_plugin_config

Delete an APISIX Plugin Config

delete_proto

Delete an APISIX Proto

delete_route

Delete an APISIX Route

delete_service

Delete an APISIX Service

delete_ssl

Delete an APISIX SSL certificate

delete_stream_route

Delete an APISIX Stream Route

delete_upstream

Delete an APISIX Upstream

dump_control_discovery

Memory dump of discovered service endpoints

dump_control_plugin_metadatas

Dump all plugin metadata from the Control API

dump_control_routes

Dump all configured Routes from the Control API

dump_control_services

Dump all configured Services from the Control API

dump_control_upstreams

Dump all configured Upstreams from the Control API

get_consumer

Get a specific APISIX Consumer by username

get_consumer_group

Get a specific APISIX Consumer Group by ID

get_control_healthcheck

Get health status of all upstream nodes

get_control_resource_healthcheck

Get health status for a specific resource

get_control_schema

Get JSON schemas for all resources and enabled plugins

get_global_rule

Get a specific APISIX Global Rule by ID

get_plugin_config

Get a specific APISIX Plugin Config by ID

get_proto

Get a specific APISIX Proto by ID

get_route

Get a specific APISIX Route by ID

get_service

Get a specific APISIX Service by ID

get_ssl

Get a specific APISIX SSL certificate by ID

get_stream_route

Get a specific APISIX Stream Route by ID

get_upstream

Get a specific APISIX Upstream by ID

list_consumer_groups

List APISIX Consumer Groups

list_consumers

List APISIX Consumers

list_global_rules

List APISIX Global Rules

list_plugin_configs

List APISIX Plugin Configs

list_protos

List APISIX Protos (Protocol Buffers)

list_routes

List APISIX Routes

list_services

List APISIX Services

list_ssls

List APISIX SSL certificates

list_stream_routes

List APISIX Stream Routes (L4 routing)

list_upstreams

List APISIX Upstreams

put_consumer

Create or update an APISIX Consumer

put_consumer_group

Create or update an APISIX Consumer Group

put_global_rule

Create or update an APISIX Global Rule

put_plugin_config

Create or update an APISIX Plugin Config

put_proto

Create or update an APISIX Proto

put_route

Create or update an APISIX Route

put_service

Create or update an APISIX Service

put_ssl

Create or update an APISIX SSL certificate

put_stream_route

Create or update an APISIX Stream Route

put_upstream

Create or update an APISIX Upstream

reload_control_plugins

Trigger a hot reload of plugins

trigger_control_gc

Trigger full garbage collection in the HTTP Lua VM

Why CrewAI?

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.

—
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
—
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
—
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
—
Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

See it in action

Apache APISIX in CrewAI

AI Agent→Vinkius

High Security·Kill Switch·Plug and Play

Why Vinkius

Apache APISIX and 4,000+ other MCP servers. One platform. One governance layer.

Teams that connect Apache APISIX to CrewAI through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.

4,000+MCP Servers ready

<40msCold start

60%Token savings

	Raw MCP	Vinkius
Server catalog	Find and host yourself	4,000+ managed
Infrastructure	Self-hosted	Sandboxed V8 isolates
Credential handling	Plaintext in config	Vault + runtime injection
Data loss prevention	None	Configurable DLP policies
Kill switch	None	Global instant shutdown
Financial circuit breakers	None	Per-server limits + alerts
Audit trail	None	Ed25519 signed logs
SIEM log streaming	None	Splunk, Datadog, Webhook
Honeytokens	None	Canary alerts on leak
Custom domains	Not applicable	DNS challenge verified
GDPR compliance	Manual effort	Automated purge + export

Unlock for AI Agents View step-by-step setup guide for CrewAI →

Enterprise Security

Why teams choose Vinkius for Apache APISIX in CrewAI

The Apache APISIX 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. All 50 tools execute in hardened sandboxes optimized for native MCP execution.

Your AI agents in CrewAI only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

Unlock for AI Agents View full Apache APISIX details →

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

The Vinkius Advantage

How Vinkius secures
Apache APISIX for CrewAI

Every tool call from CrewAI to the Apache APISIX MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.

< 40msCold start

Ed25519Signed audit chain

60%Token savings

FAQ

Frequently asked questions

Can I update a route's configuration directly through the AI?

Yes. Use the put_route tool by providing the Route ID and the new configuration JSON. The agent will interface with the APISIX Admin API to apply the changes immediately.

How do I list all the backend upstreams configured in my gateway?

Simply ask the agent to 'list upstreams'. It will trigger the list_upstreams tool and return a detailed list of all virtual hosts and load balancer nodes.

Is it possible to delete a service that is no longer needed?

Yes, you can use the delete_service tool. Provide the specific Service ID, and the agent will remove the resource from your APISIX configuration.

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.

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.

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.

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.

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.