5 Commits

Author SHA1 Message Date
bbc7f593b1 Document hosted OAuth MCP connectors
All checks were successful
build / test (push) Successful in 19s
2026-05-31 19:26:02 -03:00
633ca5dad6 release: 0.1.3 — add a2amcp bin, sync server/cli version from package.json
All checks were successful
build / test (push) Successful in 29s
publish / npm (push) Successful in 31s
Adds an "a2amcp" bin (alongside the existing "a2a-mcp" for back-compat)
so that npx -y a2amcp resolves the binary by package name. Without it
npx fell back unreliably when no bin matched.

Also rips the hardcoded "0.1.0" out of cli.ts and gateway.ts and reads
the version from package.json — that was why serverInfo lagged behind
the published tag. Renames the user-facing command in help / error
strings / README from a2a-mcp to a2amcp; the legacy bin stays for
existing scripts.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-15 20:39:23 -03:00
fd71a528e9 release: rename to unscoped a2amcp, bump 0.1.2
All checks were successful
build / test (push) Successful in 29s
publish / npm (push) Successful in 33s
Drops the @a2amcp/mcp scope so the npx invocation collapses to
`npx -y a2amcp` — one token instead of two, no scope to register or
remember.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-15 20:26:09 -03:00
f0f6fe9672 release: rename package @a2a/mcp → @a2amcp/mcp, bump to 0.1.1
All checks were successful
build / test (push) Successful in 29s
publish / npm (push) Successful in 32s
The @a2a scope on npm is owned by a different account, so PUT against
the registry 404'd. Move to @a2amcp/mcp (scope we control) and bump the
version so the publish workflow has a fresh tag to push.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-15 20:19:54 -03:00
f1ccc3bb91 ci: publish mcp package to npm
Some checks failed
build / test (push) Successful in 27s
publish / npm (push) Failing after 31s
2026-05-15 19:59:43 -03:00