4,000+ servers built on vurb.ts
Vinkius

Kong Gateway MCP Server for CrewAIGive CrewAI instant access to 40 tools to Create Certificate, Create Consumer, Create Plugin, and more

MCP Inspector GDPR Free for Subscribers

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

Ask AI about this MCP Server for CrewAI

The Kong Gateway MCP Server for CrewAI is a standout in the Friends Mcp category — giving your AI agent 40 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="Kong Gateway Specialist",
    goal="Help users interact with Kong Gateway effectively",
    backstory=(
        "You are an expert at leveraging Kong Gateway 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 Kong Gateway "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 40 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)
Kong Gateway
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 Kong Gateway MCP Server

Connect your Kong Gateway Admin API to any AI agent and take full control of your API management lifecycle through natural conversation.

When paired with CrewAI, Kong Gateway becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Kong Gateway 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

  • Services & Routes — List, create, and update upstream services and their associated routing rules to manage traffic flow.
  • Consumer Management — Query and manage API consumers, allowing you to track users and applications interacting with your gateway.
  • Plugin Configuration — Inspect and manage plugins for authentication, rate limiting, and logging across your services and routes.
  • Upstreams & Targets — Configure load balancing by managing upstreams and their health-checked targets.
  • SSL/TLS Management — List and update certificates and SNIs to ensure secure communication across your endpoints.
  • System Health — Retrieve real-time status and information about your Kong instance to monitor performance.

The Kong Gateway MCP Server exposes 40 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 40 Kong Gateway tools available for CrewAI

When CrewAI connects to Kong Gateway through Vinkius, your AI agent gets direct access to every tool listed below — spanning api-gateway, microservices, traffic-management, 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.

create

Create certificate on Kong Gateway

Create a new Kong Certificate

create

Create consumer on Kong Gateway

Create a new Kong Consumer

create

Create plugin on Kong Gateway

Create a new Kong Plugin

create

Create route on Kong Gateway

Create a new Kong Route

create

Create service on Kong Gateway

Create a new Kong Service

create

Create sni on Kong Gateway

Create a new Kong SNI

create

Create target on Kong Gateway

Create a new Target for an Upstream

create

Create upstream on Kong Gateway

Create a new Kong Upstream

delete

Delete certificate on Kong Gateway

Delete a Kong Certificate

delete

Delete consumer on Kong Gateway

Delete a Kong Consumer

delete

Delete plugin on Kong Gateway

Delete a Kong Plugin

delete

Delete route on Kong Gateway

Delete a Kong Route

delete

Delete service on Kong Gateway

Delete a Kong Service

delete

Delete sni on Kong Gateway

Delete a Kong SNI

delete

Delete target on Kong Gateway

Delete a Target from an Upstream

delete

Delete upstream on Kong Gateway

Delete a Kong Upstream

get

Get certificate on Kong Gateway

Get details for a specific Kong Certificate

get

Get consumer on Kong Gateway

Get details for a specific Kong Consumer

get

Get info on Kong Gateway

Retrieve general information about the Kong node

get

Get plugin on Kong Gateway

Get details for a specific Kong Plugin

get

Get route on Kong Gateway

Get details for a specific Kong Route

get

Get service on Kong Gateway

Get details for a specific Kong Service

get

Get sni on Kong Gateway

Get details for a specific Kong SNI

get

Get status on Kong Gateway

Retrieve the status of the Kong node

get

Get upstream on Kong Gateway

Get details for a specific Kong Upstream

list

List certificates on Kong Gateway

List all Kong Certificates

list

List consumers on Kong Gateway

List all Kong Consumers

list

List plugins on Kong Gateway

List all Kong Plugins

list

List routes on Kong Gateway

List all Kong Routes

list

List services on Kong Gateway

List all Kong Services

list

List snis on Kong Gateway

List all Kong SNIs

list

List targets on Kong Gateway

List all Targets for an Upstream

list

List upstreams on Kong Gateway

List all Kong Upstreams

update

Update certificate on Kong Gateway

Update an existing Kong Certificate

update

Update consumer on Kong Gateway

Update an existing Kong Consumer

update

Update plugin on Kong Gateway

Update an existing Kong Plugin

update

Update route on Kong Gateway

Update an existing Kong Route

update

Update service on Kong Gateway

Update an existing Kong Service

update

Update sni on Kong Gateway

Update an existing Kong SNI

update

Update upstream on Kong Gateway

Update an existing Kong Upstream

Connect Kong Gateway to CrewAI via MCP

Follow these steps to wire Kong Gateway 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 40 tools from Kong Gateway

Why Use CrewAI with the Kong Gateway MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Kong Gateway 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

Kong Gateway + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Kong Gateway MCP Server delivers measurable value.

01

Automated multi-step research: a reconnaissance agent queries Kong Gateway 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 Kong Gateway, analyzes trends over time, and generates executive briefings in markdown or PDF format

03

Multi-source enrichment pipelines: chain Kong Gateway 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 Kong Gateway against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Example Prompts for Kong Gateway in CrewAI

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

01

"List all services currently configured in Kong."

02

"Create a new service named 'auth-api' pointing to 'http://auth.internal'."

03

"What is the current status of my Kong Gateway node?"

Troubleshooting Kong Gateway MCP Server with CrewAI

Common issues when connecting Kong Gateway 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.

Kong Gateway + CrewAI FAQ

Common questions about integrating Kong Gateway 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 →