Koskamo

Jinn Gateway MCP MCP server

The Jinn Gateway MCP provides a read-only endpoint for AI agents to access a company's Brand DNA, including voice, positioning, messaging, product details, and design systems. It allows agents to retrieve brand kits, design tokens, and answer natural language questions about the brand using canonical facts, ensuring consistent brand representation in generated content.

Endpoint and access

OAuth sign-in: the first time you connect, your client opens the vendor's own authorization prompt in a browser.

OAuth sign-inEndpoint checked 2026-10-05Operated by Jinn
MCP endpoint (Streamable HTTP)
https://app.jinn.works/api/mcp
Vendor documentation

What you can do with it

  • Retrieve brand voice and positioning guidelines
  • Access render-ready brand kits and design tokens
  • Answer natural language questions about brand facts
  • Verify agent access and token context

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http jinn-gateway-mcp https://app.jinn.works/api/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add jinn-gateway-mcp --url https://app.jinn.works/api/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable jinn-gateway-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "jinn-gateway-mcp": {
      "url": "https://app.jinn.works/api/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.
Cline configuration
{
  "mcpServers": {
    "jinn-gateway-mcp": {
      "type": "streamableHttp",
      "url": "https://app.jinn.works/api/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start jinn-gateway-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "jinn-gateway-mcp": {
      "type": "http",
      "url": "https://app.jinn.works/api/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http jinn-gateway-mcp https://app.jinn.works/api/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.
Claude Desktop configuration
{
  "mcpServers": {
    "jinn-gateway-mcp": {
      "url": "https://app.jinn.works/api/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "jinn-gateway-mcp": {
      "serverUrl": "https://app.jinn.works/api/mcp"
    }
  }
}

Do you run Jinn Gateway MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing