MCP Servers & Transports
AVAILABLEConnect external Model Context Protocol (MCP) servers to seamlessly expose remote filesystems, databases, APIs, and tools to your AI applications.
- Portal Location:
Projects > [Your Project] > AI & Capabilities > MCP Servers(/projects/[slug]/mcp-servers) - API Endpoint:
/v1/mcp/servers
What is MCP (Model Context Protocol)? #
MCP is an open standard developed to connect AI models with external data sources and tools.
Naagmani provides a built-in MCP Gateway that manages:
- Connection Lifecycle: Maintains long-lived transports (
stdiosubprocesses orSSEHTTP streams) to external MCP servers. - Dynamic Tool Discovery: Automatically discovers tools, resources, and prompts exposed by the remote MCP server.
- Governance & Approval Policies: Applies fine-grained MCP Tool Policies before executing sensitive actions.
Rendering diagram...
graph LR
Agent["AI Agent in Naagmani"] --> Gateway["Naagmani MCP Gateway"]
Gateway -->|stdio Transport| LocalMCP["Local Server (Filesystem / SQLite)"]
Gateway -->|SSE Transport| RemoteMCP["Remote Server (GitHub / Postgres / Jira)"]
Supported Transport Protocols #
| Transport | Connection Target | Configuration Fields |
|---|---|---|
stdio | Local binary or command on gateway host. | Command (npx -y @modelcontextprotocol/server-postgres), args, environment variables. |
sse | Remote HTTP/HTTPS Server-Sent Events stream. | Remote URL (https://mcp.internal.company.com/sse), Bearer authorization headers. |
Connecting an MCP Server in Developer Portal #
- In your project workspace, click AI & Capabilities > MCP Servers.
- Click Add MCP Server.
- Configure:
- Server Name: e.g.,
GitHub MCP Connector. - Transport Type: Select
stdioorsse. - Command / URL: Endpoint or executable command.
- Environment Variables: e.g.
GITHUB_PERSONAL_ACCESS_TOKEN.
- Server Name: e.g.,
- Click Connect & Probe. Naagmani executes the MCP handshake and lists all available remote tools.