Skip to content

The ultimate harness for coding agents and beyond. All your agents. All your machines. One command center. Start with code, then follow your curiosity and build across disciplines: CAD, circuits, robots, games and music.

Switch MCP server to the ai.autonomous.harness domain namespace (#1414)

lingrdc9a82f16fb4b
diff --git a/cli/packages/harness-mcp/package.json b/cli/packages/harness-mcp/package.json
index fe9981f0c..aefd5f3eb 100644
--- a/cli/packages/harness-mcp/package.json
+++ b/cli/packages/harness-mcp/package.json
@@ -1,8 +1,8 @@
{
"name": "@autonomous-ai/harness-mcp",
- "version": "0.1.0",
+ "version": "0.2.0",
"description": "Harness as an MCP server: start, wait for, read and close Claude Code and Codex agents the person can watch.",
- "mcpName": "io.github.autonomous-ai/harness",
+ "mcpName": "ai.autonomous.harness/harness",
"type": "module",
"bin": {
"harness-mcp": "bin.mjs"
diff --git a/docs/research/2026-10-19-mcp-domain-auth-deploy.md b/docs/research/2026-10-19-mcp-domain-auth-deploy.md
new file mode 100644
index 000000000..b18123195
--- /dev/null
+++ b/docs/research/2026-10-19-mcp-domain-auth-deploy.md
@@ -0,0 +1,94 @@
+# MCP Registry — domain auth deploy runbook
+
+October 19, 2026. We publish the Harness MCP server to the Official MCP Registry under the domain
+namespace `ai.autonomous.harness/*` (so no GitHub org Owner is needed). This runs a public-key
+auth check against the website. This file lists what DevOps must deploy and the publish steps.
+
+## What changed for the domain namespace
+
+- `server.json` name -> `ai.autonomous.harness/harness`
+- `cli/packages/harness-mcp/package.json` `mcpName` -> `ai.autonomous.harness/harness` (npm `0.2.0`)
+- `website/scripts/listings.spec.ts` expected name -> `ai.autonomous.harness/harness`
+
+## Step 1 — web team: serve the auth file (MUST be live before login)
+
+Deploy `website/public/.well-known/mcp-registry-auth`, served exactly at:
+
+```
+https://harness.autonomous.ai/.well-known/mcp-registry-auth
+```
+
+Content (PUBLIC key — safe to commit; the private key is never in this repo):
+
+```
+v=MCPv1; k=ed25519; p=PK1G8xTW2TMjhLrYzDNFYv/5+TRosm8SPNip06Fvfug=
+```
+
+It lives at `website/public/.well-known/mcp-registry-auth`, which is already under
+`public/` (Next.js serves `public/*` at the root), so no `next.config.js` change is needed.
+Place it beside the existing `public/llms.txt` and `public/agents/`.
+
+Verify after deploy:
+
+```
+curl -s -o /dev/null -w "%{http_code}\n" https://harness.autonomous.ai/.well-known/mcp-registry-auth
+# expect 200 (was 404 before)
+```
+
+Note: keep it a plain-text file, no trailing whitespace, exactly one line.
+
+## Step 2 — npm: republish with the new mcpName (needs npm org 2FA)
+
+```bash
+cd cli/packages/harness-mcp
+npm publish --access public # version 0.2.0, mcpName ai.autonomous.harness/harness
+npm view @autonomous-ai/harness-mcp version # confirm 0.2.0
+```
+
+This is additive: `@autonomous-ai/[email protected]` (old mcpName) stays on npm;
+`0.2.0` is what new `npx` installs get. The registry's ownership check reads the latest
+published version's `mcpName`, so `0.2.0` must be the version `server.json` names.
+
+## Step 3 — build the release server.json (from the release commit)
+
+Only the repo's `server.json` template lives in `main`; `make mcpb` fills in the real
+version + sha256. Run from a checkout of the release tag (e.g. `v0.4.19_cli`):
+
+```bash
+make mcpb ARGS="0.4.19" # writes mcpb/dist/server.json + harness-mcp.mcpb, prints sha256
+```
+
+This writes `cli/packages/harness-mcp/mcpb/dist/server.json` with:
+- `name: ai.autonomous.harness/harness`
+- `version: 0.4.19` (the CLI release the bundle is attached to)
+- npm package version `0.2.0`
+- the `.mcpb` asset sha256
+
+## Step 4 — login + publish to the Official MCP Registry
+
+Install the CLI and log in with the domain auth (uses the Ed25519 private key, which is
+NOT committed — keep it out of the repo, e.g. in a secrets manager or a gitignored file):
+
+```bash
+brew install mcp-publisher
+
+# the private key (hex of the `priv:` block) is held separately; feed it via env/file:
+mcp-publisher login http --domain harness.autonomous.ai \
+ --private-key "<priv hex from the key generated for this deploy>"
+
+mcp-publisher validate cli/packages/harness-mcp/mcpb/dist/server.json
+mcp-publisher publish cli/packages/harness-mcp/mcpb/dist/server.json
+
+# confirm
+curl -s "https://registry.modelcontextprotocol.io/v0.1/servers?search=ai.autonomous.harness"
+```
+
+Order: **web file (1) -> npm (2) -> build server.json (3) -> login+publish (4).**
+The registry fetches the npm package (checks `mcpName`) and HEADs the `.mcpb` URL, so
+steps 1–3 must be live before `publish`.
+
+## Security
+
+- Public key: committed in `website/public/.well-known/mcp-registry-auth`.
+- Private key: **never** commit. Keep it in a secrets manager / gitignored file. Only the
+ `mcp-publisher login http --private-key` call needs it.
diff --git a/server.json b/server.json
index 05c9a5a6e..ec4e471be 100644
--- a/server.json
+++ b/server.json
@@ -1,6 +1,6 @@
{
"$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
- "name": "io.github.autonomous-ai/harness",
+ "name": "ai.autonomous.harness/harness",
"title": "Harness",
"description": "Start Claude Code and Codex agents the person can watch, wait for them and read their answers.",
"websiteUrl": "https://harness.autonomous.ai/agents",
@@ -13,7 +13,7 @@
{
"registryType": "npm",
"identifier": "@autonomous-ai/harness-mcp",
- "version": "0.1.0",
+ "version": "0.2.0",
"transport": {
"type": "stdio"
}
diff --git a/website/next.config.js b/website/next.config.js
index 431508bc9..1f255753b 100644
--- a/website/next.config.js
+++ b/website/next.config.js
@@ -110,6 +110,14 @@ module.exports = {
{ key: 'X-Content-Type-Options', value: 'nosniff' },
],
})),
+ {
+ // The MCP registry domain-auth file: served exactly as written, never cached or rewritten.
+ source: '/.well-known/mcp-registry-auth',
+ headers: [
+ { key: 'Cache-Control', value: 'no-store, no-transform' },
+ { key: 'X-Content-Type-Options', value: 'nosniff' },
+ ],
+ },
{
source: '/os/latest',
// Cache the GitHub lookup on the server, never the release redirect in a browser or CDN.
diff --git a/website/public/.well-known/mcp-registry-auth b/website/public/.well-known/mcp-registry-auth
new file mode 100644
index 000000000..a8b58a604
--- /dev/null
+++ b/website/public/.well-known/mcp-registry-auth
@@ -0,0 +1 @@
+v=MCPv1; k=ed25519; p=PK1G8xTW2TMjhLrYzDNFYv/5+TRosm8SPNip06Fvfug=
diff --git a/website/scripts/check-agents-site.mjs b/website/scripts/check-agents-site.mjs
index 83b1041bb..dae7b1ef3 100644
--- a/website/scripts/check-agents-site.mjs
+++ b/website/scripts/check-agents-site.mjs
@@ -8,18 +8,22 @@ const base = new URL(process.argv[2] || 'http://127.0.0.1:3000');
const requests = { signal: AbortSignal.timeout(20_000) };
const page = await readFile(new URL('../public/agents/index.html', import.meta.url), 'utf8');
const llms = await readFile(new URL('../public/llms.txt', import.meta.url), 'utf8');
+const mcpAuth = await readFile(new URL('../public/.well-known/mcp-registry-auth', import.meta.url), 'utf8');
for (const [route, expected, type] of [
['/agents', page, /text\/html/],
['/agents/', page, /text\/html/],
['/agents/index.html', page, /text\/html/],
['/llms.txt', llms, /text\/plain/],
+ // Next serves the dotfile as octet-stream, not text/plain; the MCP registry reads its body, so
+ // only require the route to serve the bytes unchanged and keep the no-cache/nosniff headers.
+ ['/.well-known/mcp-registry-auth', mcpAuth, null],
]) {
const response = await fetch(new URL(route, base), requests);
assert.equal(response.status, 200, route);
- assert.match(response.headers.get('content-type'), type, route);
+ if (type) assert.match(response.headers.get('content-type'), type, route);
assert.match(response.headers.get('cache-control'), /no-transform/, route);
assert.equal(response.headers.get('x-content-type-options'), 'nosniff', route);
assert.equal(await response.text(), expected, `${route} must serve the file unchanged`);
}
-console.log('Harness /agents and /llms.txt: every entry path serves the static source unchanged.');
+console.log('Harness /agents, /llms.txt and /.well-known/mcp-registry-auth: every entry path serves the static source unchanged.');
diff --git a/website/scripts/listings.spec.ts b/website/scripts/listings.spec.ts
index bc1ecc7d4..eb531b887 100644
--- a/website/scripts/listings.spec.ts
+++ b/website/scripts/listings.spec.ts
@@ -29,7 +29,7 @@ const manifest = json("cli", "packages", "harness-mcp", "mcpb", "manifest.json")
/** What the registry checks beyond the schema when it publishes (its internal/validators, read on 2026-10-11). */
function registryRules(entry: Server) {
- expect(entry.name).toBe("io.github.autonomous-ai/harness");
+ expect(entry.name).toBe("ai.autonomous.harness/harness");
expect(entry.packages.map((pkg) => pkg.registryType).sort()).toEqual(["mcpb", "npm"]);
for (const pkg of entry.packages) expect(pkg.transport).toEqual({ type: "stdio" });
const npm = entry.packages.find((pkg) => pkg.registryType === "npm")!;