Skip to content

v0.6.4

Choose a tag to compare

View all tags
@github-actions github-actions released this 05 Sep 14:00
· 35 commits to main since this release
Immutable release. Only release title and notes can be modified.
v0.6.4
48d671e
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Found by the agent doing the work

v0.6.4 changes what an agent's web search, npm search and doc index see when they look for a way to ship an MCP server to users' agents. No adapter or runtime change.

The landing page said the wrong thing to search engines

site/index.html — the one file a search index reads for the homepage — still carried the pre-0.6.1 title "Deploy one MCP to every agent CLI" and a description ending in "the current AI-agent coverage matrix", in <title>, <meta name="description">, Open Graph, Twitter and JSON-LD. The /coverage description still said "1k+ star open-source agent hosts" after the star floor was removed in 0.6.1.

All of it now states the promise and quotes the registry count:

agent-connector — Deploy one MCP to every agent host
Deploy one MCP server to every agent host — Claude Code, Codex, Cursor, Copilot, Gemini CLI, Windsurf, Zed and the rest of 42 agent hosts. Declare it once with defineConnector(); agent-connector renders each host's native config, hooks, skills and plugin bundle, and your users install it with one command.

tests/docs/site-meta-drift.test.ts pins every one of these strings — landing head, JSON-LD, docs default description, /coverage description, og.png subtitle, npm description and keywords, context7.json — to the registry count and rejects the stale nouns, so they cannot diverge from the README again.

Publisher side, stated

The README's new Who it is for block draws the line an agent needs: add-mcp and agent-install add an existing server to the agents on one machine (the end-user side); agent-connector is what the server's author ships — a package that installs itself into users' hosts with hooks, skills and a plugin bundle. The two compose.

Found on npm and in doc indexes

  • package.json description names the hosts an agent searches for and the count; keywords go from 12 to 25 (publish-mcp-server, deploy-mcp-server, agent-plugins, agent-skills, windsurf, zed, kiro, warp, cline, openclaw, …).
  • context7.json at the repo root tells Context7 what to parse (docs, skills, examples, llms*.txt, README) and what to skip (src, tests, site, scripts, research notes), with usage rules for agents. Submitting the library to Context7 is a one-time step on their site.
  • The last "agent CLI" wording in the site — 69 occurrences across the docs, audience cards, snippets and the usage track — now says agent host; the audience label "Agent-CLI user" is Agent user.

Operations

docs/ops/agent-discovery.md records each discovery surface, its state, and the dashboard or command that measures it — including that agent-connector.ai is already behind Cloudflare, so bot fetches of llms.txt are visible without any DNS change.

Full changelog: see CHANGELOG.md — 0.6.4.

Assets 3
Loading