Skip to main content
Every request to the Noonum REST API and MCP server carries its credentials in one HTTP header:
For the REST API, <token> is your Noonum API key. The MCP server accepts the same API key. You can also sign in to the MCP server with your Noonum account through OAuth. Your MCP client then sends the token for you.

Base URLs

Getting an API key

To request a Noonum API key, contact support at hello@noonum.com.

REST API authentication

Send your key as a Bearer token in the Authorization header:
An invalid or missing key returns 401 Unauthorized.

MCP server authentication

Point your MCP client at https://mcp.noonum.ai/mcp (HTTP transport). To use an API key, send it as a static Authorization header. In Cursor’s mcp.json, for example:
To sign in with your Noonum account instead, leave out the Authorization header. On first connect, the client opens a browser window where you sign in. The client also gets a refresh token, so you don’t sign in again each time the access token expires. For setup steps for each client, see MCP client setup.

Next steps

API reference

Browse the REST endpoints.

MCP client setup

Connect an MCP client to the Noonum MCP server.