Skip to main content
New to MCP? Start with Agentic access with MCP. Connect an MCP client to the Noonum MCP server at https://mcp.noonum.ai/mcp. This page covers the Claude Code CLI, Claude Desktop and claude.ai, Cursor, and generic MCP clients, with both authentication methods:
  • API key (static Authorization header), for automation and server-side use.
  • OAuth, for interactive apps that sign you in to your Noonum account through a browser.
For the full tool catalog and how runs work, see the Noonum MCP Server reference. For API keys and the shared REST auth model, see Authentication. OAuth (browser sign-in) is documented on this page.

Before you start

You need one of the following, depending on the method you choose:
  • For the API-key flow: a Noonum API key. See Authentication to request one.
  • For the OAuth flow: a Noonum user account you can sign in to. The client handles the OAuth handshake, so no key is required.
Which method should I use? For a script, server, or headless integration, use the API key. For a desktop app you use interactively, use OAuth so the client signs you in through the browser.

Option A: Claude Code CLI

If you use Claude Code, a single command registers the server:
Make sure the URL ends in /mcp. To use OAuth instead, omit --header. Then run /mcp in Claude Code, pick noonum, and sign in with your Noonum account.

Option B: Claude Desktop and claude.ai

Claude Desktop and claude.ai add remote MCP servers as custom connectors. claude_desktop_config.json is for local servers only, so do not add Noonum there.
1

Add a custom connector

Open Customize → Connectors and choose Add custom connector. Enter Noonum as the name and https://mcp.noonum.ai/mcp as the server URL.On a Team or Enterprise plan, an owner adds the connector for the organization under Organization settings → Connectors. Each member then connects to it from Customize → Connectors.
2

Choose how to authenticate

Keep the default authentication settings and click Add. Then click Connect next to Noonum. Your browser opens the Noonum sign-in page. After you approve, Claude keeps you signed in and renews access on its own.
A connector you add on claude.ai is also available in Claude Desktop.

Option C: Cursor

Cursor connects to MCP servers over HTTP. Add Noonum through Settings → MCP → Add new MCP server, or by editing Cursor’s MCP config (~/.cursor/mcp.json, or .cursor/mcp.json for a single project). The config looks like this:
Reload Cursor (or toggle the server off and on) so it picks up the change. With OAuth, expect a browser prompt on first connect.

Option D: A generic MCP client

Any MCP client that supports the MCP Streamable HTTP transport can connect to Noonum. Configuration field names vary by client; the values stay the same.
1

Point the client at the MCP URL

Set the server URL to:
Select the HTTP transport (MCP Streamable HTTP). No SSE or custom-protocol options are required.
2

Configure authentication

Add a static request header:
If your client uses a JSON config, the shape generally mirrors Cursor’s:
3

Reload and connect

Reload the client so it picks up the new server. With OAuth, expect a browser prompt on first connect; with an API key, the connection is established immediately.

Named examples

The steps above cover any HTTP-transport client. Two specifics:
  • Codex CLI: register Noonum as an MCP server in your Codex config, pointed at https://mcp.noonum.ai/mcp over HTTP, with the Authorization: Bearer header for the API-key flow.
  • ChatGPT and other connectors: point the connector at https://mcp.noonum.ai/mcp, select the HTTP transport, and set the Authorization: Bearer header, or leave it unset to use OAuth.

Verify it works

Once the client has reloaded:
  1. Check the server is connected. In Claude Desktop or claude.ai, open Customize → Connectors and confirm Noonum shows as connected. In Claude Code, run /mcp. In other clients, check the MCP server or tools panel.
  2. Confirm the tools loaded. You should see the Noonum tools available, for example list_strategies, search_companies, and get_usage. The tool list means the client handshook with the server.
  3. Make a real call. Ask the client to run a low-risk, read-only tool. Good first calls:
    • “List my Noonum strategies” → runs list_strategies.
    • “Show Noonum’s public strategies” → runs list_strategies with scope set to public.
    • “How many Noonum credits do I have left?” → runs get_usage.
A successful tool call returns data (or an empty list if you have no strategies yet) rather than an authentication error. That confirms both the connection and your credentials are good.
Read analytics, not trades. Noonum tools return research analytics. They don’t place trades and aren’t investment advice. An LLM client can also misread output, so review results before acting on them. Most tools are read-only and safe to explore first; a few change your strategies or consume credits (see What your agent can access). Lead with read-only calls and use the state-changing ones deliberately.

Troubleshooting

401 Unauthorized (API key)

An API-key authentication failure returns a standard 401 Unauthorized. Check that:
  • The header is exactly Authorization: Bearer YOUR_API_KEY, with a single space after Bearer and no extra quotes or whitespace around the key.
  • You pasted the full key and it has not been revoked. If in doubt, request a fresh key from hello@noonum.com.
  • The URL is https://mcp.noonum.ai/mcp (note the mcp. host and the /mcp path, with no version).

OAuth re-authentication

OAuth failures do not surface as a 401 you handle yourself. Instead, the client restarts the authorization flow and opens the browser so you can sign in again. An expired access token alone does not cause this, because the client renews it with its refresh token. You sign in again only when your sign-in has expired or been revoked, or when the client has lost its saved tokens. If the browser prompt does not appear or the loop repeats:
  • Complete the browser sign-in fully, including any consent screen.
  • Make sure your client is configured without an Authorization header. A stray header forces the API-key path.
  • Remove any issuer, audience, or client ID you set by hand. The client discovers what it needs from the MCP server, and the MCP server rejects a token you get from Auth0 directly.

409: email already belongs to another account

If you connected with OAuth, submit_strategy and get_usage can fail with 409 and the message “This email already belongs to another Noonum account”. This usually means you signed in with a different method than the one you first signed up with. Disconnect the server, connect again, and sign in the way you first signed up. If that does not work, contact hello@noonum.com.

Tools do not appear

  • Re-check the JSON is valid (no trailing commas, balanced braces) and fully restart the client.
  • Verify the url and transport are HTTP and point at https://mcp.noonum.ai/mcp.

A run seems stuck

submit_strategy does not wait for the run to finish. It returns right away with the version and its run state. A live run usually takes a few minutes. A historical run with priority below 5 can take hours. Poll get_strategy_version until completed is true. A status of -1 is a temporary error that is retried automatically. A status of -2 means the run failed, and a failed run is not charged. See Runs.

Still stuck

If the problem persists, or the server returns a 5xx or other server-side error, contact hello@noonum.com.

Next steps