@adrata/starfield-mcp
Give a coding agent your Starfield board.
Starfield is the work board in Adrata — boards, cards, tags, roll-ups, and the governed writes that move them. This package lets Claude Code, Codex, Cursor, Windsurf, or any other MCP client read that board and change it through exactly the same endpoints the app uses, so workspace scoping, validation, and the transactional move all hold whether a human dragged the card or an agent did.
Install
You don't. Point your agent's config at it and the client installs it on launch.
Claude Code
claude mcp add starfield --scope user -- npx -y @adrata/starfield-mcp
Codex — codex mcp add writes the global file, ~/.codex/config.toml;
there is no project-scope flag.
codex mcp add starfield -- npx -y @adrata/starfield-mcp
For a project-scoped setup, edit the file yourself — .mcp.json for Claude
Code, .codex/config.toml for Codex. Codex ignores project config in a
directory you have not trusted, and says nothing when it does.
Then, inside the agent
connect_workspace # signs you in through the browser; read-only by default
workspace_status # names the credential in play and the tier it grants
connect_workspace runs a real OAuth 2.1 + PKCE flow against a loopback
callback and stores a refreshable, revocable token on your machine. Ask for
connect_workspace with writeAccess: true when the agent needs to move cards.
Nothing outside your machine can tell you whether the config landed —
workspace_status is the confirmation.
What this actually is
The same implementation as
@adrata/adrata-mcp, under
the product name people are looking for. The wrapper selects the Starfield
profile before importing the shared server. That profile advertises only
workspace/session, board, roadmap, agent, webhook, governed bridge, and future
Forms/Surveys/Automations packs. Foreign CRM schemas are not sent to the model.
The bridge is the namespace-bound search_capabilities →
describe_capability → run_capability path; the broad legacy API/dispatcher
escape hatches are not registered in this profile.
An explicit ADRATA_MCP_ENABLED_DOMAINS remains authoritative for controlled
deployments. The wrapper never widens it.
Environment
| Variable | Meaning |
|---|---|
ADRATA_API_URL | API base URL (default https://api.adrata.com) |
ADRATA_API_KEY | Pro-tier API key |
ADRATA_OAUTH_TOKEN | Enterprise OAuth token (or use connect_workspace) |
ADRATA_MCP_SERVER_NAME | Display name in serverInfo (default Starfield here) |
ADRATA_MCP_ENABLED_DOMAINS | Optional explicit tool packs; overrides the Starfield defaults |
Full documentation, including the tier model and the complete tool list, lives
in the @adrata/adrata-mcp README.