Skip to main content

​
What it is

Noxus runs a hosted Model Context Protocol (MCP) server. It exposes the platform’s capabilities — workflows, agents, conversations, knowledge bases, tables, sandboxes, deployments and more — as MCP tools that any MCP-compatible client can call. Point Claude Desktop, Claude Code, Cursor, or your own agent at it, authenticate with a Noxus API key, and the model can list your workflows, run them, search a knowledge base, query a data table, or create an agent — all as native tool calls, no glue code.

Remote, hosted

A single streamable-HTTP endpoint — nothing to install or run locally.

Your API key = your access

Authenticate with a workspace API key; tools are gated by that key’s permissions.

Same surface as the SDK

Backed by the same platform APIs as the Python SDK, so behavior matches.

Model-native

Tools carry typed schemas, so models call them reliably without prompt glue.

​
Connection details

Self-hosted / on-prem deployments serve the same MCP server at https://<your-backend-host>/mcp. Use that URL in place of backend.noxus.ai/mcp below.

​
Authentication

The server takes your Noxus API key as a bearer token. It’s the same key you use for the SDK and REST API — create one in the Noxus UI under Settings → Organization → Workspaces → (pick a workspace) → API Keys. Every tool call runs as that key, in its workspace, and is subject to the key’s permissions. A read-only key can list and read but not create or delete; a key without the sandboxes:run permission can’t spin up sandboxes. This is the same permission model as the REST API — see Authentication.

​
MCP vs. SDK vs. REST

All three hit the same platform. Pick by how you’re building:

MCP

You want an LLM/agent to operate Noxus as tools (Claude, Cursor, a custom agent). No code — the model calls tools directly.

Python SDK

You’re writing a Python program and want typed resources, pagination helpers, and streaming. See the SDK.

REST API

You’re in another language or wiring a webhook/integration. See the API reference.

​
Next steps

Connect a client

Config for Claude Desktop, Claude Code, Cursor, and generic MCP clients.

Available tools

The full catalog of tools the server exposes, by domain.
Looking to give one of your Noxus agents access to an external MCP server (GitHub, Linear, Notion…)? That’s the reverse direction — configured per-agent as an MCP tool. See the agent tools documentation.