Connectors & MCP reference
// plug the station into your tools — and into your other harnesses
Built-in tools
Agents ship with a broad real-tool belt. Everything an agent can reach outside its own reasoning belongs to one of eight capability families, and every family is gated by the station's capability model (object = capability) — you grant it by placing the gear, and you can revoke it the same way.
| Family | What it grants |
|---|---|
| Web & browser | Search the web, fetch pages, and drive a real browser — navigate, read, click, type. |
| File cabinet | Read, search, and write files in the agent's workspace. |
| Workbench | Run shell commands and verify code — the code-execution bench. |
| Task delegation | Delegate subtasks to summoned crew, summon new agents, and schedule routines. |
| Comms relay | Send a message out to a connected chat — only chats someone already opened with this station. |
| Media studio | Generate images from text and analyse images, on the key the agent already uses. |
| Memory notebook | The agent's private memory, task plans, and saved skills. |
| Jukebox | Search and control your Spotify — play, pause, queue, "what's playing". |
Browsing that actually browses
The web family is not just a search box. An agent can run a search, fetch a page, and then drive a real browser against it — navigating, reading the rendered page, clicking, and typing. When a page is unreachable or throws up a challenge, the agent reports that as the result rather than inventing a plausible summary of a page it never loaded; a 403 or a 404 is an answer, not a hidden failure.
When a site genuinely requires a login, the agent can't and won't ask you for the password. It asks the station to open a visible browser window and you sign in yourself — your password is typed into real Chrome and never passes through the agent or the model. The resulting cookies live in the station's browser profile, so later runs stay signed in without ever having handled your credentials.
MCP connectors
StarNet speaks Model Context Protocol. A curated connector catalog covers popular services with one-click setup; connectors that need auth use OAuth 2.1 dynamic client registration or a pasted key. Any third-party remote http(s) MCP server can be added by URL — your agents' reach grows with the ecosystem, not with our release schedule.
Local stdio servers (npx …, uvx …) are supported only through
an agent-owned SAFE CELL. StarNet probes Docker before connecting, runs the server inside that
isolated cell, keeps connector secrets out of process arguments, and never falls back to spawning the
server directly on your host. If no real Safe Cell agent exists, the local-server route is unavailable
rather than pretending the process is isolated.
Messaging channels
Connect Telegram, Discord, Slack, Matrix, or Signal and your agents can report to you — and take tasking from you — where you already are. Scheduled and Night Shift runs can deliver their results straight to a channel. Matrix talks to whatever homeserver you point it at, and Signal talks to a signal-cli bridge you run yourself; StarNet never picks the server for you.
Outbound messages are a capability like any other: an agent can only write to a chat someone has already opened with this station, never to an arbitrary address it decides on.
Telegram as a remote control
Telegram goes further than notifications. From your phone you can hold a real threaded conversation with a specific agent, start and steer runs, answer an approval an agent is waiting on, and orchestrate the crew — the same command surface as COMMS, reachable when you're nowhere near the machine. The station is still doing the work locally; Telegram is just the window you're looking through.
Harness interop
Already run Claude Code, or another agent harness? StarNet exposes an MCP stdio bridge and an OpenAI-style ingress endpoint, so other tools can drive StarNet capabilities — and StarNet agents can sit alongside the harnesses you already use instead of replacing them. Your station becomes shared infrastructure, not another silo.
Local by default
Every connector and channel is opt-in. The default station touches the network only for the model provider you configured; anything wider is a grant you made on purpose and can revoke in Settings.