Identities your agents can act as, with the secret kept out of the chat.
The accounts your agents use on other systems — a mailbox, an API, an app registration — each with its one credential kept encrypted and never pasted into a conversation.
What your AI can do with it
- Give an agent an identity on another system without handing it the password
- Keep every credential encrypted, with a record of every reveal
- Lock an identity in one move when something looks wrong
- Know before a credential expires
For example
- You say
- “Which of our service accounts expire this month?”
- Your AI
- Lists the personas and reads each one's expiry warning.
- You get
- A short list, before anything stops working.
Its tools
- Create
- Lock
- Reveal
- Replace secret
- Create
- A new identity and its secret
- Lock
- Stop its use at once
- Reveal
- Read the secret, audited
- Replace secret
- Rotate it
Good to know
- Free trial, no card.
- Every price is visible before your AI enables anything.
- Money moves only when you approve a payment link.
- Disabling a service stops its tools and deletes nothing.
Experimental means the tools work and are billed as shown, and their names and shapes may still change before the service is generally available.
Connect your AI
Give your AI this address. It does the rest, and asks you when it needs you.
https://staging.stationzero.services/mcpRun this once in a terminal:
claude mcp add --transport http station-zero https://staging.stationzero.services/mcpInstall with one click, or paste this into .cursor/mcp.json:
{ "mcpServers": { "station-zero": { "url": "https://staging.stationzero.services/mcp" } } }Install with one click, or paste this into .vscode/mcp.json:
{ "servers": { "station-zero": { "type": "http", "url": "https://staging.stationzero.services/mcp" } } }Paste this into your project's AGENTS.md or CLAUDE.md, or give it to your AI as an instruction:
## AI services at https://staging.stationzero.services
This project's AI services are reached over MCP at https://staging.stationzero.services/mcp.
- Your MCP client connects there. The first time, it asks your human to authorize it: they sign in, or create an account, and approve it in their browser. You then act for their organisation. If the server is not in your client's configuration, ask your human to add it.
- Start with `help_explore` and no arguments: it says what the services are, which are on for your account, and lists the help pages. `services_describe` says what a service costs; where it offers a free trial, `services_enable` with `"trial": true` starts one at no cost.
- Anything that costs money is your human's decision: `wallet_top_up` returns a payment link to hand to them.
- The REST API takes an API key, not the MCP token. No key yet? POST https://staging.stationzero.services/api/v1/signup with your human's email address as `operatorEmail` (the Authentication help page explains why): the 201 answer carries `apiKey`, shown once — keep it where you keep secrets and never commit it. Every call creates a new organisation of its own, not your human's, and the key is not accepted at https://staging.stationzero.services/mcp.For any client that reads an mcpServers file:
{ "mcpServers": { "station-zero": { "url": "https://staging.stationzero.services/mcp" } } }No MCP client? One POST creates an organisation and returns its API key:
curl -X POST https://staging.stationzero.services/api/v1/signup \
-H 'Content-Type: application/json' \
-d '{"operatorEmail":"you@example.com"}'This page is written for your AI as well: hand it the address and it can read the full instructions itself.
The first time it connects you sign in, or create an account, and approve it.