Documentation Index
Fetch the complete documentation index at: https://mintlify.com/kortix-ai/suna/llms.txt
Use this file to discover all available pages before exploring further.
Overview
MCP (Model Context Protocol) tools allow agents to connect to external services through standardized protocols. Kortix supports multiple MCP server types:- Composio: Pre-built integrations (Gmail, Slack, GitHub, etc.)
- Custom HTTP: Custom MCP servers over HTTP
- Custom SSE: Custom MCP servers using Server-Sent Events
- Custom JSON/stdio: Local MCP servers via stdin/stdout
Get Agent Custom MCP Tools
Authentication
Requires JWT authentication via theAuthorization header.
Path Parameters
The unique identifier of the agent
Headers
The URL of the MCP server (for HTTP/SSE) or Composio profile ID
The MCP server type:
http, sse, or composioOptional JSON string of custom headers for the MCP server
Response
Array of discovered tools from the MCP server
Whether this MCP server is already configured for the agent
The type of MCP server (http, sse, composio)
The MCP server URL or identifier
Example Request
Example Response
Update Agent Custom MCP Tools
Authentication
Requires JWT authentication.Path Parameters
The unique identifier of the agent
Request Body
The MCP server URL or Composio profile ID
The MCP server type:
http, sse, or composioArray of tool names to enable
Response
Whether the operation succeeded
Array of tool names that are now enabled
Total number of enabled tools
Example Request
Example Response
Update Agent Custom MCPs
Authentication
Requires JWT authentication.Path Parameters
The unique identifier of the agent
Request Body
Array of MCP configuration objects
Response
Whether the operation succeeded
Example Request
Example Response
MCP Server Types
HTTP MCP Servers
HTTP-based MCP servers use streamable HTTP for communication:SSE MCP Servers
Server-Sent Events based MCP servers:Composio Integrations
Pre-built integrations via Composio:JSON/stdio MCP Servers
Local MCP servers via stdin/stdout:Error Responses
MCP integrations not enabled
Worker not found
Invalid request (missing URL, invalid config, etc.)
Custom worker limit exceeded
Internal server error
MCP Tool Execution
MCP tools are executed using ephemeral connections:- Discovery: Tool schemas are cached in Redis (24-hour TTL)
- Activation: Tools are activated on first use (JIT loading)
- Execution: Each call creates a fresh connection to the MCP server
- Result: Connection is closed immediately after execution
Schema Caching
MCP tool schemas are cached for performance:- Cache Key:
mcp_schema:{toolkit_slug} - TTL: 24 hours
- Storage: Redis
- Invalidation: Automatic on TTL expiry or manual via registry methods
Security Considerations
URL Validation
In production environments, private/local URLs are blocked:- Localhost addresses (127.0.0.1, ::1)
- Private IP ranges (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16)
- Link-local addresses (169.254.0.0/16)
Authentication
- Composio: Authentication handled via profile configuration
- Custom MCPs: Use custom headers for API keys/tokens
- Private MCPs: Deploy behind authentication gateway
Best Practices
- Test MCP servers: Use the discovery endpoint before enabling tools
- Enable selectively: Only enable tools your agent needs
- Monitor usage: Track which tools are being called
- Update regularly: Keep MCP configurations in sync with server changes
- Handle failures: MCP servers may be temporarily unavailable
- Cache schemas: Let the system cache schemas for performance
- Version agents: Use agent versions when changing MCP configurations
Rate Limits
MCP tool endpoints respect the following limits:- Discovery: Max 30 seconds timeout per server
- Execution: Max 30 seconds timeout per tool call
- Custom MCPs: Limited by subscription tier (check plan limits)
- Connection pool: Ephemeral connections prevent pool exhaustion