The Noxus MCP server is a remote streamable-HTTP endpoint at https://backend.noxus.ai/mcp, authenticated with your Noxus API key as a bearer token. Below are configs for the common clients. Replace YOUR_NOXUS_API_KEY with a key from Settings → Organization → Workspaces → API Keys.
Your API key grants access to its workspace. Treat it like a password — prefer
an environment variable over hardcoding it, and use a key scoped to only the
permissions the client needs.
Claude Code
Claude Desktop
Cursor
Any MCP client
Add the server with the CLI (HTTP transport + an Authorization header):Then in a session, the Noxus tools are available to the model. Manage it with claude mcp list / claude mcp remove noxus. Claude Desktop can add remote MCP servers as custom connectors: Settings → Connectors → Add custom connector, then enter the URL https://backend.noxus.ai/mcp. When prompted for authentication, supply your API key as the bearer token.If your version needs a config-file entry instead, bridge the remote server with mcp-remote in claude_desktop_config.json:Restart Claude Desktop after editing the file. Add to .cursor/mcp.json (project) or ~/.cursor/mcp.json (global):Enable it under Cursor Settings → MCP. Any client that supports the streamable-HTTP transport can connect. Provide:
- URL:
https://backend.noxus.ai/mcp
- Header:
Authorization: Bearer YOUR_NOXUS_API_KEY
The server advertises its tools on connect (tools/list); no per-tool setup is needed. Self-hosted deployments
On-prem / self-hosted Noxus serves the same MCP server at your backend host:
Use that URL in any of the configs above.
Verify the connection
Once connected, ask the model to list something read-only, e.g. “list my Noxus workflows” or “what knowledge bases do I have?” — it should call workflows_list / knowledge_bases_list and return your workspace’s resources. If calls fail with an auth error, re-check the bearer token; if a specific tool is refused, the key likely lacks that permission (see Available tools). 
