Connect Omnimatch with MCP

Choose your AI assistant, add the MCP connection, then sign in.

Your AI assistant

Claude

Browser sign-in Open Customize → Connectors and add a custom connector with the URL below. Select Connect, then sign in to Omnimatch. The connection also works in claude.ai, Claude Desktop and Cowork.

https://omnimatch.ai/mcp

Alternative setup

On Team or Enterprise an owner has to add it first, under Organization settings → Connectors → Add → Custom → Web, same URL. Everyone else then hits Connect on it in their own Customize → Connectors.

ChatGPT

Browser sign-in Open Settings → Security and login and turn on Developer mode. Go to Plugins, select +, add Omnimatch with the URL below, then create the connection and review its tools. Availability depends on your account and workspace policy.

https://omnimatch.ai/mcp

Claude Code

Browser sign-in Run this in any terminal. No key is needed: Claude Code flags Omnimatch as needing sign-in, and you complete it from /mcp inside a session, or by running claude mcp login omnimatch:

claude mcp add --transport http omnimatch https://omnimatch.ai/mcp

Alternative setup

Running Claude Code somewhere without a browser? Add a key instead:

claude mcp add --transport http \
  --header "Authorization: Bearer YOUR_API_KEY" \
  omnimatch https://omnimatch.ai/mcp

Codex CLI

Browser sign-in Two commands in any terminal. The second opens a browser to sign in to Omnimatch:

codex mcp add omnimatch --url https://omnimatch.ai/mcp
codex mcp login omnimatch

Alternative setup

No mcp login in your build, or running Codex somewhere without a browser? Use a key instead: put this in ~/.codex/config.toml and set OMNIMATCH_API_KEY in your environment. (Codex on the web can't be configured this way; it only sees MCP tools that come bundled with a plugin.)

[mcp_servers.omnimatch]
url = "https://omnimatch.ai/mcp"
bearer_token_env_var = "OMNIMATCH_API_KEY"

Cursor

Browser sign-in Add this to ~/.cursor/mcp.json, then sign in to Omnimatch when Cursor prompts you. No key needed:

Add to Cursor

{
  "mcpServers": {
    "omnimatch": {
      "url": "https://omnimatch.ai/mcp"
    }
  }
}

Alternative setup

Prefer a key? The one-click button above installs it once your key is filled in, or add the header by hand:

{
  "mcpServers": {
    "omnimatch": {
      "url": "https://omnimatch.ai/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

VS Code

Browser sign-in For GitHub Copilot in VS Code: add this to .vscode/mcp.json (top-level key is servers), then sign in to Omnimatch when VS Code prompts you. No key needed:

Install in VS Code

{
  "servers": {
    "omnimatch": {
      "type": "http",
      "url": "https://omnimatch.ai/mcp"
    }
  }
}

Alternative setup

Prefer a key? The one-click button above installs it once your key is filled in, or add the header by hand:

{
  "servers": {
    "omnimatch": {
      "type": "http",
      "url": "https://omnimatch.ai/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Gemini CLI

Run this in any terminal:

gemini mcp add --transport http \
  --header "Authorization: Bearer YOUR_API_KEY" \
  omnimatch https://omnimatch.ai/mcp

Copilot CLI

Run this in any terminal:

copilot mcp add --transport http \
  --header "Authorization: Bearer YOUR_API_KEY" \
  omnimatch https://omnimatch.ai/mcp

JetBrains / Visual Studio

Visual Studio uses the same servers shape as VS Code, in %USERPROFILE%\.mcp.json. No key needed: click Manage Authentication on the CodeLens above the entry and sign in to Omnimatch.

{
  "servers": {
    "omnimatch": {
      "url": "https://omnimatch.ai/mcp"
    }
  }
}

Alternative setup

JetBrains: top-level key is mcpServers, and the key goes in a plain headers block:

{
  "mcpServers": {
    "omnimatch": {
      "url": "https://omnimatch.ai/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

OpenCode

For OpenCode 1 (opencode), put this in opencode.json: server names live directly under mcp, type remote. OpenCode 2 also accepts this format.

{
  "mcp": {
    "omnimatch": {
      "type": "remote",
      "url": "https://omnimatch.ai/mcp",
      "oauth": false,
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Alternative setup

For the OpenCode 2 beta (opencode2), the optional native format nests servers under mcp.servers:

{
  "mcp": {
    "servers": {
      "omnimatch": {
        "type": "remote",
        "url": "https://omnimatch.ai/mcp",
        "oauth": false,
        "headers": {
          "Authorization": "Bearer YOUR_API_KEY"
        }
      }
    }
  }
}

Cline / Windsurf

In your MCP settings JSON (Windsurf accepts either serverUrl or url):

{
  "mcpServers": {
    "omnimatch": {
      "type": "streamableHttp",
      "url": "https://omnimatch.ai/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      },
      "disabled": false
    }
  }
}

Key fallback (no OAuth)

This tool signs in with a key. If you're signed in we'll fetch yours and fill the snippet above in; it stays in your browser and nothing is sent anywhere.

Check the connection

Start a new chat and ask:

“Which Omnimatch agents can I use?”

Let your assistant set it up

Copy this prompt into any AI assistant that can configure MCP. It uses browser sign-in when available and your API key as a fallback.

I want to use my Omnimatch agents from here. Please register Omnimatch as a persistent MCP server (so it stays available in future chats, not just a one-off call): transport MCP Streamable HTTP, URL: https://omnimatch.ai/mcp. If your harness supports MCP OAuth, add the server with no credentials and complete the browser sign-in when it appears; that is the preferred path. If OAuth isn't available, use this Omnimatch API key: YOUR_API_KEY. Register the MCP server with header "Authorization: Bearer YOUR_API_KEY", or call the REST API directly with the same header (docs at https://omnimatch.ai/docs). If you need the exact per-tool setup (Claude Code, Codex, Cursor, VS Code, Gemini, and others), see https://omnimatch.ai/connect. Once connected you can search, read and write memories, view our chat history, manage my custom agents, and step into any agent I've hired (act_as_agent) to serve its side of a conversation yourself, committing each exchange with record_agent_turn so it lands in my chat history. The key is scoped to working with my agents; it can't manage API keys, billing or account settings.

Connection details and API-key fallback

Server	`https://omnimatch.ai/mcp`
Transport	MCP Streamable HTTP
Sign-in	Browser sign-in where supported
API key	`Authorization: Bearer <your API key>`
REST fallback	https://omnimatch.ai/docs

Any other MCP client can use the server above. Keep API keys private; they grant access to your agents.