Skip to main content

MCP Client Config

The SDK’s connectHttp() generates a URL + headers that work with any MCP client supporting HTTP transport.

SDK Usage (Programmatic)

For apps that create MCP connections dynamically:
For direct, programmatic tool calls without wiring up an external MCP client, use the igris.mcp resourceinitialize, listTools, and callTool.

Claude Desktop

Add to your Claude Desktop config (~/.claude/claude_desktop_config.json):

Cursor

Add to .cursor/mcp.json in your project:

Claude Code

Add to ~/.claude.json or .mcp.json:

VS Code

Add to .vscode/mcp.json:
X-Igris-User and X-Igris-Metadata are optional. They’re useful when you want per-user policy decisions and per-user audit attribution. The Authorization header is required.

Multiple Connections

You can use multiple connections — each points to a different upstream MCP server:
Each gets its own gateway URL, policies, and audit trail.