Skip to main content
Neosantara implements the Model Context Protocol (MCP) in two distinct roles: as an MCP Gateway (Server) providing tools to local IDEs and agents, and as an MCP Connector (Client) connecting AI models to your remote MCP servers.

Comparing the Two MCP Roles

When to Use Each Mode

Use MCP Gateway When:

  • You want to connect coding IDEs (Cursor, Windsurf) or Claude Desktop to Neosantara AI capabilities.
  • You need tools such as image generation or model catalog discovery directly from an IDE chat window.
  • You configure CLI agents such as Claude Code to call Neosantara tools.

Use MCP Connector When:

  • You build applications where LLMs need access to private databases, internal APIs, or third-party services through your own MCP servers.
  • You want to avoid writing client-side tool-calling orchestration loops. Simply provide your MCP server URLs, and Neosantara handles tool discovery, execution, and response synthesis automatically.

MCP Connector

Connect chat models to your remote MCP servers automatically.

MCP API Keys

nsk_mcp_ key format, tier rate limits, and creation instructions.

Coding Agents & IDEs

Setup guides for Claude Code, OpenCode, Cursor, and Cline.

Claude Desktop

Configure Claude Desktop application with Neosantara SSE transport.