MCP setup

Connect your AI tool to Outcomet

Bring the customer's words into your AI workflow. Connect your tool to Outcomet, sign in, then ask it to read the feedback behind the work.

https://mcp.outcomet.app/mcp
Choose your AI toolTry Outcomet

Before you connect, you need an Outcomet account with access to your workspace and permission to connect an external AI tool. Your client must support remote MCP with OAuth, or use a compatible local proxy.

Setup steps

  1. 1

    Open your MCP-capable client.

  2. 2

    Add https://mcp.outcomet.app/mcp as the MCP server URL.

  3. 3

    Sign in with your Outcomet account when the browser opens.

  4. 4

    Approve access to the workspace you want the AI tool to use.

  5. 5

    Retry tool discovery or reconnect if the client does not refresh.

See what you can do once connected. Watch the MCP demo →

Use browser sign-in

A compatible MCP client opens Outcomet in your browser. Outcomet resolves your user, workspace, role, and scopes after you approve the connection. Review the requested permissions: available actions depend on your role and approved access. Current tools read product context, including initiatives, create feedback and, with contact write access, create or update contacts and companies.

MCP does not expose every in-app workflow. The currently advertised tools do not update or close initiatives, or change links between capabilities and initiatives. Check the tools your connection exposes before asking for a change.

Do not paste these into an MCP client
Supabase service-role keysSupabase anon keysdatabase credentialstenant IDsworkspace IDsshared workspace tokensAPI keys

Connect your agent

Configure your favorite AI client or coding assistant to connect to Outcomet.

Claude

Connect Claude Code (CLI) or Claude apps (claude.ai / Claude Desktop) to use Outcomet tools.

Path A — Claude Code (CLI)

  1. 1
    Add the server (native HTTP transport):
    claude mcp add --transport http outcomet https://mcp.outcomet.app/mcp
  2. 2
    Authenticate. Important: /mcp is not a shell command — it is a slash command inside the interactive Claude Code TUI. Launch interactive Claude Code by running claude on its own, then type /mcp, select outcomet → Authenticate. A browser opens.
  3. 3
    Sign in with your Outcomet account in the browser and approve the workspace connection.
  4. 4
    Back in Claude Code, tools appear under outcomet. If they don't, reconnect or retry tool discovery.

Path B — Claude apps (claude.ai / Claude Desktop)

  1. 1
    Open connector settings (claude.ai → Settings → Connectors → add custom connector; or Claude Desktop's connector settings).
  2. 2
    Name it Outcomet, and paste the MCP URL:
    https://mcp.outcomet.app/mcp
  3. 3
    Claude opens the browser sign-in; approve the workspace connection.
  4. 4
    Note: This page cannot add a connector or approve access. An explicitly authorized assistant may help where your client permits it; review the requested permissions and follow the client's consent requirements.

Codex

Use a current Codex version to connect directly over HTTP with browser sign-in. A local proxy is available for clients that need stdio.

Native HTTP (recommended)

  1. 1
    Add this to your Codex ~/.codex/config.toml file (%USERPROFILE%\.codex\config.toml on Windows):
    [mcp_servers.outcomet]
url = "https://mcp.outcomet.app/mcp"
  2. 2
    After adding the configuration, you may need to reconnect or restart Codex to load it. Authenticate from MCP settings or run codex mcp login <configured-server-name>. The name must match your configuration: outcomet is the example above, so its command is codex mcp login outcomet. If you named it outcomet_mcp, use codex mcp login outcomet_mcp.
  3. 3
    Complete the browser sign-in and approve the requested workspace access. Check that Outcomet tools appear; retry tool discovery or reconnect if they do not refresh. When renewing an existing connection, a successful login does not always require restarting Codex.

Fallback — local stdio proxy

  1. 1
    If native HTTP/OAuth is unavailable in your client, install Node.js with npx and replace the entire [mcp_servers.outcomet] section above with this configuration. Do not retain the url field:
    [mcp_servers.outcomet]
command = "npx.cmd"
args = ["-y", "mcp-remote@latest", "https://mcp.outcomet.app/mcp"]
  2. 2
    This example is for Windows. On macOS or Linux, use npx instead of npx.cmd.
  3. 3
    Restart or reconnect Codex and complete the browser sign-in opened by the proxy. Check that Outcomet tools appear; the native codex mcp login command is not used for this stdio path.

Antigravity

For Antigravity's stdio setup, use the mcp-remote proxy. The example below is for Windows and requires Node.js with npx; on macOS or Linux, use npx and your local file path.

Setup instructions

  1. 1
    Create a local JSON file for static OAuth client info (e.g., at %USERPROFILE%\.gemini\antigravity\scratch\outcomet_client_info.json):
    {"client_id":"antigravity"}
    Warning: Avoid inline JSON on Windows as it is easy to quote incorrectly and get shell-mangled.
  2. 2
    Add the following configuration to your client's MCP settings:
    {
  "mcpServers": {
    "outcomet": {
      "command": "npx.cmd",
      "args": [
        "-y",
        "mcp-remote@latest",
        "https://mcp.outcomet.app/mcp",
        "--static-oauth-client-info",
        "@C:\\Users\\YOUR_USER\\.gemini\\antigravity\\scratch\\outcomet_client_info.json"
      ]
    }
  }
}
    Replace YOUR_USER with your local Windows profile folder name.
  3. 3
    Reconnect the client and complete the browser sign-in when prompted.

Try your first question

Once your client shows Outcomet tools, start with a small read-only request.

Read the latest 10 feedback items in this workspace. Show the original customer wording and available source references. Highlight any onboarding issues in those items, separate observations from interpretation, and say when evidence is missing. Do not create or update anything.

Check the customer wording and source references before acting. This prompt reviews a recent sample, not all feedback. No onboarding feedback in those ten items does not mean there are no onboarding problems. If no records are returned, check your workspace access and whether it contains feedback.

Troubleshooting

Can an assistant help me connect?

This page cannot configure your client or approve access. In a compatible client, an explicitly authorized assistant may help with setup or reauthentication, including an authorized renewal approval where client rules allow it. Consent is not automatic, and renewing existing access does not authorize new permissions.

401 after login

Confirm your Outcomet account has workspace access, then reauthenticate the configured server if needed. Retry tool discovery or reconnect if tools do not refresh; successful reauthentication does not always require restarting the whole client.

Client asks for API keys

The client is using the wrong auth mode. Use OAuth and the hosted MCP endpoint.

npx.ps1 cannot be loaded

Use npx.cmd for Windows stdio proxy clients.