MCP setup

Know before your customers do

Connect Outmano to the AI you already use. Then ask about your competitors' prices, reviews and roadmaps, and get answers from the competitors you track.

Create an account, then generate a key under Integrations → MCP. Paste it in place of YOUR_KEY in the steps below.

Keys are read-only. They only read data for the competitors your workspace tracks, and you can revoke them at any time under Integrations → MCP. Only the workspace owner can create keys, and MCP needs an active trial or plan.

Claude

claude_desktop_config.json

Claude Desktop connects to Outmano through a small bridge called mcp-remote, which runs with Node.js.

  1. Install Node.js 18 or newer from nodejs.org if you don't have it yet.
  2. In Claude Desktop, open Settings, go to Developer and click Edit Config. This opens claude_desktop_config.json.
  3. Add Outmano under mcpServers, then replace YOUR_KEY with your key: 
    {
  "mcpServers": {
    "outmano": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://outmano.com/mcp",
        "--header",
        "Authorization:${AUTH_HEADER}"
      ],
      "env": {
        "AUTH_HEADER": "Bearer YOUR_KEY"
      }
    }
  }
}
  4. Save the file, then quit Claude Desktop completely and open it again.
  5. In a new chat, open the connectors menu next to the message box and check that "outmano" is listed.

If you already have other servers in this file, add only the "outmano" block inside your existing "mcpServers".

Try it: What pricing changes did my competitors make this month?

Claude Code

Claude Code adds Outmano with one terminal command.

  1. Run this in your terminal, with your key in place of YOUR_KEY: 
    claude mcp add --transport http --scope user outmano \
  https://outmano.com/mcp \
  --header "Authorization: Bearer YOUR_KEY"
  2. Start Claude Code with claude and type /mcp. Outmano should show as connected.

--scope user makes Outmano available in all your projects. Leave it out to add Outmano to the current project only.

Try it: Get the Outmano battlecard for my top competitor and turn it into a one-page sales sheet in battlecard.md.

Codex

~/.codex/config.toml

Codex connects to Outmano directly over HTTP, with one block in its config file.

  1. Open ~/.codex/config.toml. Create the file if it doesn't exist.
  2. Add this block, with your key in place of YOUR_KEY: 
    [mcp_servers.outmano]
url = "https://outmano.com/mcp"
http_headers = { "Authorization" = "Bearer YOUR_KEY" }
  3. Save the file and start Codex. Type /mcp to check that Outmano is listed.

The Codex CLI and the Codex IDE extension read the same config file, so you only set this up once. If you'd rather not keep the key in the file, use bearer_token_env_var = "OUTMANO_API_KEY" in place of http_headers, and set OUTMANO_API_KEY in your shell.

Try it: Which features do my competitors have that we don't? Show them as a table.

Cursor

~/.cursor/mcp.json

Cursor connects to Outmano directly, with one entry in mcp.json.

  1. Open ~/.cursor/mcp.json in your home folder. Create the file if it doesn't exist.
  2. Add Outmano under mcpServers, then replace YOUR_KEY with your key: 
    {
  "mcpServers": {
    "outmano": {
      "url": "https://outmano.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_KEY"
      }
    }
  }
}
  3. Save the file. Open Customize in Cursor's sidebar and check that Outmano is turned on and lists its tools.

Use the global file in your home folder instead of a project's .cursor/mcp.json. That way your key stays out of your repo.

Try it: What did my competitors change on their roadmaps recently? Flag anything that overlaps with what we're building.