MCPNews

The Model Context Protocol ecosystem, verified

Current spec 2026-07-28

Doc Bridge

Spec Support Unverified First-party Confidence: Good (0.85)

Doc Bridge is an MCP server published by AgentsKit.io; its MCP spec-revision support has not been verified yet. It is the first-party server from AgentsKit.io. Last verified 2026-09-15.

Does Doc Bridge support the current MCP specification (2026-07-28)?

Undetermined. We have not verified which MCP specification revision Doc Bridge supports (as of 2026-09-15).

Is Doc Bridge a first-party (official) MCP server?

Yes. Doc Bridge is the first-party MCP server published by AgentsKit.io (last verified 2026-09-15).

How do I connect to Doc Bridge?

Doc Bridge is available via the package npm:@agentskit/doc-bridge, the official MCP Registry under io.github.AgentsKit-io/doc-bridge, the source repository at https://github.com/AgentsKit-io/doc-bridge. Authentication: none. Transports: stdio.

What tools does Doc Bridge expose?

Doc Bridge exposes 8 tools, including handoff.resolve, doc.search, doc.get, gate.status, retriever.query, memory.classify (last verified 2026-09-15).

When were Doc Bridge's facts last verified?

2026-09-15. Each fact on this page links to the sources used to verify it.

Which tools does Doc Bridge expose?

8 tools verified.

  • handoff.resolve
  • doc.search
  • doc.get
  • gate.status
  • retriever.query
  • memory.classify
  • memory.promoteDraft
  • registry.topology

Doc Bridge is AgentsKit's own documentation and agent-handoff tool: it reads a repository's docs, ownership map and human documentation site, then gives coding agents and humans an evidence-linked starting point before an edit. It runs locally over stdio only, launched via npx ak-docs mcp, and requires no API key; the README states it does not send project data to AgentsKit, collect telemetry, or write files outside the selected project. The AgentsKit-io GitHub organization, the @agentskit npm scope, the doc-bridge.agentskit.io product page and the parent agentskit.io site all point at the same repository, establishing first-party authority: this is not a wrapper around a separate vendor's product.

The dedicated docs/mcp.md page, fetched 2026-09-15, enumerates eight tools: handoff.resolve, doc.search, doc.get, gate.status, retriever.query, memory.classify, memory.promoteDraft and registry.topology. The README separately states that a packaged Claude Desktop bundle advertises fourteen tools and exercises eight of them in its smoke test; the extra six, and the one non-read-only tool named in the README (docbridge.proposals), are not itemized in docs/mcp.md. No file fetched, including the README, CHANGELOG, PRIVACY.md and the docs pages, names an MCP protocol revision, so spec support is recorded as unknown.

The official MCP Registry record is pinned at version 1.2.6, published 2026-08-03, while the npm package @agentskit/doc-bridge had reached version 1.7.45 by 2026-08-29, roughly forty releases ahead. GitHub's own release feed stopped at v1.4.3 on 2026-08-14; the newer npm versions have no corresponding GitHub release or tag.

How widely adopted is Doc Bridge?

Ranked #247 in The MCP 500 with Adoption Index 49.50 (snapshot , methodology v1).

Measurement Value Source
Official MCP Registry yes API ·
Docker MCP Catalog no API ·
npm downloads (weekly) 1,761 API ·
GitHub stars 7 API ·
GitHub forks 1 API ·
Last push 2026-09-15T04:14:57Z API ·
Repository archived no API ·

How was this verified, and what are the sources?

Verified · method: repo-readme · confidence 0.85 (Good).

  1. Official MCP Registry search match for io.github.AgentsKit-io/doc-bridge, fetched 2026-09-15 - confirms the pre-fetched record: version 1.2.6, isLatest true, statusChangedAt 2026-08-03, repository.url https://github.com/AgentsKit-io/doc-bridge, no remotes - accessed
  2. GitHub repository AgentsKit-io/doc-bridge, fetched 2026-09-15 - not archived, MIT license, 7 stars, 1 fork, latest GitHub release v1.4.3 (2026-08-14), no security advisories, owner type Organization - accessed
  3. npm registry metadata for @agentskit/doc-bridge, fetched 2026-09-15 - latest 1.7.45 published 2026-08-29 versus the registry's pinned 1.2.6; no @modelcontextprotocol/sdk dependency present; repository field matches the GitHub org - accessed
  4. Doc Bridge product page, fetched 2026-09-15 - titled "Doc Bridge - one repository, two audiences"; its only GitHub link is https://github.com/AgentsKit-io/doc-bridge - accessed
  5. Parent site agentskit.io, fetched 2026-09-15 - titled "AgentsKit.js", page body names "Doc Bridge" among its own listed products - accessed
  6. docs/mcp.md, fetched 2026-09-15 - tool table lists exactly eight tools (handoff.resolve, doc.search, doc.get, gate.status, retriever.query, memory.classify, memory.promoteDraft, registry.topology) and states the build "exercises all eight tools from the staged runtime" - accessed