Connect an AI assistant to nullplatform
The nullplatform MCP server is how an AI assistant gets access to your organization. Once it's connected, the agent can query, troubleshoot, and operate nullplatform for you, as you: with only the access you approve, and never more than you have. You add one URL, sign in, and choose what the agent can do. There's nothing to install and no API key to copy.
It works with any assistant that supports remote MCP servers: Claude Code, Claude on the web and desktop, Cowork, Kiro, Cursor, Codex, and others. That includes people who never open a terminal: they can ask about their deployments from a chat window.
The AI plugins teach your assistant how nullplatform works. The MCP server gives it access to your organization. They work well together, and each works on its own.
How it works
- You add your organization's MCP URL to your AI assistant.
- The first time the agent connects, your browser opens. You sign in to nullplatform and approve the connection, choosing what the agent can do.
- Nullplatform creates a personal access token for that connection. The agent acts as you, and it can never do more than you.
The connection lasts until that token expires or you delete it from your user settings. In between, it renews its session on its own, so you don't sign in again every hour.
Your server URL
It's the URL you use to sign in to nullplatform, with /mcp at the end:
https://<your-org>.app.nullplatform.io/mcp
For example, if you sign in at https://acme.app.nullplatform.io, your MCP server is https://acme.app.nullplatform.io/mcp.
Connect your AI assistant
Claude Code
Add the server:
claude mcp add --transport http nullplatform https://<your-org>.app.nullplatform.io/mcp
Then start a session, run /mcp, select nullplatform, and choose Authenticate. Your browser opens so you can sign in and approve access. Back in Claude Code, you'll see Authentication successful. Connected to nullplatform.
💡 Tip:
claude mcp addregisters the server for the current project. Add--scope userto make it available in every project.
Claude on the web, desktop, and Cowork
Add nullplatform as a custom connector: open Settings > Connectors, click Add custom connector, and paste your server URL. Claude opens the sign-in page the first time you connect.
Other assistants
Kiro, Cursor, Codex, VS Code, and other assistants that support remote MCP servers take the same URL. Add it as a remote (HTTP) MCP server in the assistant's settings. The assistant opens your browser to sign in the first time it connects.
Sign in and approve access
After you sign in, nullplatform asks you to approve the connection. Walk through the screen below:
Choose Choose grants, pick a resource, and give it only the Member role. The agent can read everything at that resource and change nothing.
What your agent can do
The server exposes nullplatform as a small set of tools instead of one tool per API operation, so the agent's context stays usable:
| Tool | What it does |
|---|---|
np_list | List entities of one type, with filters |
np_read | Read one entity by ID |
np_describe | Describe an API operation: its parameters and request body |
np_lake_query | Run read-only SQL against the data lake, for counts, aggregates, and questions that cross entities |
np_logs | Fetch the application logs of a scope |
np_metrics | Fetch a scope's metrics: requests per minute, response time, error rate, CPU, and memory |
np_docs_search | Search the nullplatform documentation |
np_skills, np_skill_read | Browse and read nullplatform's AI skills, the same catalog as the AI plugins |
np_auth_status | Report whether the connection works, and for which organization |
np_create, np_update, np_patch, np_delete | Create, change, and delete entities |
The agent can change something only if the access you approved allows it, and anything outside it is refused. The server also tells the agent to confirm with you before it creates, changes, or deletes anything.
Manage and revoke access
Every connection is a personal access token under User settings > Personal access tokens, tagged source | mcp. Search for mcp to list them all. From there you can see what each one can do, extend it, or delete it.
Deleting the token cuts the agent's access right away. To use the server again, connect and approve a new token.
Removing the server from your assistant doesn't delete its token. Delete it from your user settings too, or it stays listed until it expires.
Use an API key instead
Agents that can't open a browser, like one running in CI, can authenticate with an API key sent in the X-API-Key header. A personal access token works too, if the agent should act as you:
claude mcp add --transport http nullplatform https://<your-org>.app.nullplatform.io/mcp \
--header "X-API-Key: AAAA.1234567890abcdef1234567890abcdefPTs="
The key's grants decide what the agent can do.
Project-scoped MCP configuration files, such as .mcp.json, are often committed to git. Don't put a key in one: read it from an environment variable or keep the entry in your user configuration.
The hosted server or the CLI
The CLI can also run as an MCP server, locally, with the session np already has. Use the hosted server when you want sign-in from the browser, an access you choose per connection, and support for assistants that don't run on your machine. Use the CLI when you already work with np profiles and want the server to start read-only.
Next steps
- Personal access tokens: see, extend, and delete the tokens your connections use
- Set up the AI plugins: teach your coding assistant how nullplatform works
- Using the CLI as an MCP server: run the server locally with your
npsession - Roles: what each role lets the agent do