AgentTCDH

One registry for MCP servers and A2A agents.

Agent & Tool Capability Discovery Hub is an open-source TypeScript service for managing agent and tool connection metadata in one place. Register a target once, let consumers discover its capabilities and connection details, and execute directly against the selected target.

Quickstart · Connect an agent · Reference · Verification · Contributing

Why AgentTCDH

Keep shared target registrations in one place as agents and tools change. Consumers query the same registry, so additions, updates, and removals become visible on their next lookup.

• One catalog: remote MCP servers, local stdio MCP commands, and A2A agent endpoints.

• Three discovery interfaces: MCP tools, A2A messages, and an HTTP API over the same registry.

• Direct execution: consumers use returned connection details to call their selected tools or agent peers.

• Persistent management: SQLite storage, CLI administration, metadata import/refresh, conditional updates, and JSON backups.

Related MCP server: Lab Registry Server

How it works

flowchart LR
    Admin["Administrator"] -->|"Register / update"| Hub["AgentTCDH registry"]
    Agent["Consuming agent"] -->|"Discover capabilities"| Hub
    Hub -->|"Capabilities + connection details"| Agent
    Agent -->|"Direct MCP call"| Tool["MCP server"]
    Agent -->|"Direct A2A message"| Peer["A2A agent"]

The consumer owns target selection, protocol clients, credentials, and execution permissions. The hub returns metadata; target connections and calls happen in the consumer's environment. Native tool mounting depends on the client. The registry searches keywords and filters; planning happens in the consuming agent.

Quickstart

Use Node.js 24 or newer and npm. Install from source:

git clone https://github.com/east-true/agent-tcdh.git
cd agent-tcdh
npm ci
npm run demo

For a published release, run the CLI without a source checkout:

npx --yes agent-tcdh@0.1.0 --help
npx --yes agent-tcdh@0.1.0 serve

The v0.1.0 release also provides a built tarball, checksums, and installation instructions. Source commands below use the repository checkout; an installed CLI uses agent-tcdh in place of npm run cli --.

The demo starts an isolated hub, registers three local targets, discovers them, and calls HTTP MCP, stdio MCP, and A2A targets directly. It checks execution receipts and cleans up. No account, API key, external service, or model is needed.

npm run demo -- --discovery a2a
npm run demo -- --serve

--discovery a2a queries the hub over A2A. --serve keeps the demo available for manual connections. See the local demo guide.

Start a persistent registry

npm run build
npm start

The hub listens at http://127.0.0.1:3000. In another terminal, import the supplied public documentation registrations:

npm run cli -- registry import examples/public-docs-registry.json
npm run cli -- target list --tag public-docs
npm run cli -- target list --q OpenAI --protocol mcp
npm run cli -- target get openai-docs

The snapshot includes OpenAI Docs, Toss Payments Docs, Microsoft Learn, Cloudflare Docs, Context7, and DeepWiki. Import stores their observed metadata. Consumers establish connections when using a target; Toss's pinned npm command runs in the consumer environment.

These are working examples, not a provider allowlist. Register other MCP servers and A2A agents using the generic definition schema, or import their remote metadata.

MCP discovery

Connect your MCP client to http://127.0.0.1:3000/mcp.

Configure the hub once in your consumer, then ask it to discover suitable targets and connect directly. For example:

Find the official OpenAI documentation server in AgentTCDH. Retrieve its connection details and use its documentation search tool directly to answer my question.

The consumer needs permission and a way to call the discovered target. Recorded Codex runs used native MCP discovery and agent-written HTTP clients for execution. See Codex/OpenCode configuration and stdio setup and actual-agent verification.

A2A discovery

Agent peers can discover the hub through /.well-known/agent-card.json and query it through /a2a. The hub supports A2A 1.0 and 0.3 JSONRPC discovery with structured search_targets and get_target operations.

The selected target's protocol determines how the consumer executes it. A consumer can discover an MCP server through the hub's A2A interface, then call that server with MCP. See message formats and protocol versions.

Manage registrations

npm run cli -- target import https://mcp.example.com/mcp --id docs --protocol mcp --dry-run
npm run cli -- target import https://agent.example.com --id researcher --protocol a2a --dry-run
npm run cli -- target refresh openai-docs --dry-run
npm run cli -- target check openai-docs
npm run cli -- registry export backups/registry.json

Replace example addresses with your own endpoints. Import/refresh inspect metadata. target check compares the registration with current remote metadata and reports drift; it does not verify execution. Stdio commands can be registered as JSON without launching them during registration.

The reference covers CRUD, disabling targets, search, authentication references, ETag concurrency protection, snapshots, and all CLI commands. The running hub exposes its OpenAPI specification at /openapi.json.

Storage, authentication, and deployment

The default SQLite registry lives at ~/.agent-tcdh/registry.sqlite, using the current user's home directory on each OS.

Use administrator credentials for registration changes and read credentials for discovery. Store provider credential references in registrations and resolve them in the consuming environment. With no hub tokens configured, the hub accepts anonymous requests.

For Docker, copy .env.example to .env, then run:

docker compose up --build -d

Compose uses a non-root Linux container and a persistent registry volume. Local npm execution reads shell environment variables; Compose reads .env. See deployment, token roles, origins, and reverse proxies.

Verified behavior

Recorded verification on 2026-10-27:

Local fixtures, SDK-driven provider calls, actual model selection, and model-backed adapters are separate checks. The reports preserve their execution paths, failures, fixes, and limits. They do not establish automatic dynamic tool mounting or compatibility with every commercial agent.

Run checks

npm run check
npm run test:package

CI runs typecheck, regression, and package checks on all four native OS/architecture combinations, plus independent Linux container verification. See platform and shell-specific setup.

Public MCP verification is opt-in:

npm run test:public-mcp

Real-agent/model checks are also opt-in and can consume model usage. See verification commands. The default suite and CI use local fixtures.

Documentation

• CLI, API, protocols, and configuration reference

• Local demo

• MCP/A2A agent registration compatibility

• Actual-agent verification

• Changelog and release process

• Contributing and security policy

Project documentation, comments, and application messages use English. Original provider metadata and intentional Unicode fixtures retain their original text.

License

Apache-2.0