@adrata/starfield-mcp 1.0.0

package/README.md

@@ -0,0 +1,68 @@
+# @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**
+
+```bash
+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.
+
+```bash
+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 server as [`@adrata/adrata-mcp`](https://www.npmjs.com/package/@adrata/adrata-mcp),
+under the name people wiring an agent to a board are looking for. It is a
+dependency, not a copy: this package's entire implementation is six lines that
+default `ADRATA_MCP_SERVER_NAME` to `Starfield` — so your client's server list
+says Starfield — and then import the real thing. Every tool, every tier, and
+every governed-write contract is identical, and there is no second codebase to
+drift.
+
+Install either name; they are the same server.
+
+## 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) |
+
+Full documentation, including the tier model and the complete tool list, lives
+in the [`@adrata/adrata-mcp` README](https://www.npmjs.com/package/@adrata/adrata-mcp).

package/bin/starfield-mcp.js

@@ -0,0 +1,40 @@
+#!/usr/bin/env node
+
+/**
+ * @adrata/starfield-mcp — Starfield under its own name.
+ *
+ * This is not a second MCP server. It is the same server, `@adrata/adrata-mcp`,
+ * reached by the name the person installing it actually has in mind.
+ *
+ * The reasoning, since a wrapper this thin invites deletion:
+ *
+ *   A developer wiring a coding agent to their build board is thinking about
+ *   Starfield. They may never encounter the company name, and shouldn't have to
+ *   type it to install a board client. The precedent is unanimous — `@angular/core`
+ *   is Google's, `next` is Vercel's, `react` is Meta's; when a product is what
+ *   people know, the product name wins. The `@adrata` scope stays because this
+ *   server holds workspace credentials and reaches both the CRM and the board,
+ *   and a scope is a provenance signal an unscoped name has none of.
+ *
+ * What it must NOT be is a fork. Two copies of a 116kB server that drift is a
+ * far worse outcome than an odd-looking six-line file, so `@adrata/adrata-mcp`
+ * is an ordinary runtime dependency and this file adds exactly one thing: the
+ * display name.
+ *
+ * It imports rather than spawns. A child process would double the startup, add
+ * a second thing to keep alive, and put a signal- and exit-code-forwarding
+ * problem between a client and its stdio transport — all to accomplish what
+ * setting one variable before an import does for free. The server reads its
+ * configuration from `process.env` when it is evaluated, so assigning first and
+ * importing second is sufficient, and dynamic import is what makes the order
+ * real (a static `import` is hoisted and would run before this line).
+ *
+ * The default is a default, not an override: an explicit ADRATA_MCP_SERVER_NAME
+ * wins, so anyone running this under a white-labelled name still gets it.
+ */
+
+if (!process.env.ADRATA_MCP_SERVER_NAME?.trim()) {
+  process.env.ADRATA_MCP_SERVER_NAME = 'Starfield';
+}
+
+await import('@adrata/adrata-mcp');

package/package.json

@@ -0,0 +1,48 @@
+{
+  "name": "@adrata/starfield-mcp",
+  "version": "1.0.0",
+  "description": "Starfield MCP server — give Claude Code, Codex, Cursor, and other coding agents your Starfield board. Read boards and cards, create and move work, and run governed writes from the terminal.",
+  "type": "module",
+  "main": "./bin/starfield-mcp.js",
+  "bin": {
+    "starfield-mcp": "./bin/starfield-mcp.js"
+  },
+  "scripts": {
+    "start": "node ./bin/starfield-mcp.js"
+  },
+  "keywords": [
+    "mcp",
+    "starfield",
+    "adrata",
+    "model-context-protocol",
+    "claude-code",
+    "codex",
+    "cursor",
+    "windsurf",
+    "kanban",
+    "board",
+    "issue-tracker",
+    "agents"
+  ],
+  "license": "UNLICENSED",
+  "private": false,
+  "publishConfig": {
+    "access": "public"
+  },
+  "repository": {
+    "type": "git",
+    "url": "https://github.com/adrata/adrata",
+    "directory": "code/starfield-mcp"
+  },
+  "homepage": "https://adrata.com",
+  "engines": {
+    "node": ">=18.0.0"
+  },
+  "files": [
+    "bin/",
+    "README.md"
+  ],
+  "dependencies": {
+    "@adrata/adrata-mcp": "^1.0.0"
+  }
+}