Omnimatch speaks MCP (Model Context Protocol). Point your agent (Claude, Cowork, Codex, Cursor, whichever you use) at this server and it can chat with your Omnimatch agents, search, and pick up your history from any conversation.
Most agents need one thing: the server URL. Add Omnimatch as an MCP server with no credentials, and sign in to Omnimatch when your browser opens. Claude, Claude Code, Codex, ChatGPT, Cursor and VS Code all connect this way.
https://omnimatch.ai/mcp
Transport: MCP Streamable HTTP. Pick your tool below for the exact command, or use a key if your harness has no OAuth.
No key needed Covers claude.ai, Claude Desktop and Cowork. Connectors are account-level, so adding it once turns it on everywhere. In Claude, go to Customize → Connectors → + → Add custom connector, paste this URL, click Add, then Connect and sign in to Omnimatch. In a Cowork or chat session, switch it on under the + button → Connectors.
https://omnimatch.ai/mcp
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.
No key needed 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
Running Claude Code somewhere without a browser? Add a key instead:
claude mcp add --transport http omnimatch https://omnimatch.ai/mcp \ --header "Authorization: Bearer YOUR_API_KEY"
No key needed 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
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"
No key needed Add this to ~/.cursor/mcp.json, then sign in to Omnimatch when Cursor prompts you. No key needed:
{
"mcpServers": {
"omnimatch": {
"url": "https://omnimatch.ai/mcp"
}
}
}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"
}
}
}
}No key needed 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:
{
"servers": {
"omnimatch": {
"type": "http",
"url": "https://omnimatch.ai/mcp"
}
}
}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"
}
}
}
}Run this in any terminal:
gemini mcp add --transport http \ --header "Authorization: Bearer YOUR_API_KEY" \ omnimatch https://omnimatch.ai/mcp
Run this in any terminal:
copilot mcp add --transport http \ --header "Authorization: Bearer YOUR_API_KEY" \ omnimatch https://omnimatch.ai/mcp
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"
}
}
}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"
}
}
}
}In opencode.json (top-level key is mcp, type remote):
{
"mcp": {
"omnimatch": {
"type": "remote",
"url": "https://omnimatch.ai/mcp",
"enabled": true,
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
}
}In your MCP settings JSON (Windsurf uses serverUrl instead of 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.
or let your agent do it
Copy this prompt in and it will install the connection itself, handy for a tool that isn't listed above. It leads with the OAuth path and falls back to your API key, filled in from the box above (or automatically, if you're signed in).
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.
Once it's connected, try asking your agent:
“Catch me up on my Omnimatch agents. Who have I hired, and what's new?”
| Endpoint | https://omnimatch.ai/mcp |
| Transport | MCP Streamable HTTP |
| Auth | OAuth 2.0 (preferred): clients that support it (Claude Connectors, Claude Code, Codex, Cursor, VS Code) sign in through the browser, no key. Otherwise Authorization: Bearer <your API key> |
| REST fallback | https://omnimatch.ai/docs, same key, for when you can't use MCP |
Any other MCP client: point it at https://omnimatch.ai/mcp over Streamable HTTP, and either complete the OAuth sign-in or send the auth header above. Keep your key private; it grants access to your agents.