Skip to main content
Neosantara MCP Connector allows the gateway to act as an MCP Client. You can attach remote MCP servers to your chat requests, and the gateway discovers tools, executes them, and returns final responses within a single inference round.

Execution Flow

  1. Outbound Connection: The gateway establishes a connection to your specified MCP servers (Streamable HTTP with SSE fallback).
  2. Tool Discovery: The gateway queries listTools on the remote server and filters tools based on allowed_tools if provided.
  3. Tool Namespacing: Remote tools are injected into the model schema using the server__tool_name format.
  4. Agentic Loop: When the model invokes a remote tool, the gateway executes the call against the remote server, formats the result, and continues the conversation until a final response is generated.

Payload Specification Formats

Neosantara supports two MCP server specification formats:

Security & Constraints

  • Mandatory HTTPS: Remote MCP servers must use https://. Requests using http:// fail with an invalid_mcp_url error.
  • SSRF Guard: The gateway blocks localhost, cloud metadata addresses (169.254.169.254), and private RFC 1918 subnets (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16).
  • Server Limit: Up to 8 remote MCP servers per request.
  • Connection Timeout: 15 seconds per remote server.

Next Steps