CONNECTORS & INTEROP

// plug the station into your tools — and into your other harnesses

Built-in tools

Agents ship with a broad real-tool belt: web search and fetching, browser automation, files and shell in granted workspaces, notebooks, memory recall, skills, and more — fourteen tool families, every one gated by the station's capability model (object = capability).

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 MCP server you run can be added — your agents' reach grows with the ecosystem, not with our release schedule.

Messaging channels

Connect Telegram or Discord 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.

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.