Skip to Content
🚀 Orga AI is in open beta.

MCP

This page specifies the mcp_server configuration field used to connect an Orga AI session to a Model Context Protocol (MCP) server.

For a guided walkthrough, see MCP: Connect your first server. For background and security boundaries, see What is MCP?.


mcp_server

Optional MCP server connection details included in your session initialization config.

mcp_server?: { id: string; alias: string; url: string; headers?: Record<string, string>; } | null;

Field reference

FieldTypeRequiredDescription
idstringYesUnique identifier (for example: "github-tools", "local-files").
aliasstringYesHuman-readable name shown in the UI (for example: "GitHub Assistant").
urlstringYesMCP SSE endpoint URL. Must end with /sse (for example: "http://localhost:3000/sse").
headersRecord<string, string>NoAdditional headers sent when connecting (commonly used for authentication).

Semantics

ValueMeaning
undefinedUse the default behavior for your integration (no explicit MCP server configured).
nullExplicitly disable MCP for this session (no external tools).
objectConnect to the given MCP server.

Examples

Local filesystem (no auth)

mcp_server: { id: "filesystem", alias: "Local Files", url: "http://localhost:3000/sse", }

GitHub (token required)

mcp_server: { id: "github", alias: "GitHub Tools", url: "http://localhost:3000/sse", headers: { Authorization: "Bearer ghp_your_token_here", "X-GitHub-Api-Version": "2022-11-28", }, }

PostgreSQL (connection string header)

mcp_server: { id: "postgres", alias: "Company Database", url: "http://localhost:3000/sse", headers: { "X-Connection-String": "postgresql://user:pass@localhost:5432/mydb", }, }

Transport notes

SSE (current)

url points at the server’s SSE endpoint (typically /sse). The MCP server must remain running for the duration of your WebRTC session.

STDIO (planned)

When STDIO transport is supported, configuration is expected to include a local command and args so Orga AI can launch the MCP server automatically.

Last updated on