AgentTCDH MCP server
Commit Nov 8, 2026Provides a centralized registry for discovering and connecting to MCP servers and A2A agents via a single metadata hub.
Also known as jiind/agent-tcdh
- Stars
- 0
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- —
- Last commit
- Nov 8, 2026
- License
- Apache-2.0
What is AgentTCDH MCP?
AgentTCDH provides a centralized registry for discovering and connecting to MCP servers and A2A agents via a single metadata hub.
Summary generated from the project's README
About AgentTCDH MCP server
Managing a growing collection of MCP servers and A2A agents is what AgentTCDH simplifies by providing a centralized metadata registry. Developers and teams can register remote MCP servers, local stdio commands, and agent endpoints in one place to ensure all consumers access the same updated connection details. The service acts as a discovery hub rather than an execution layer, meaning the consuming agent maintains control over protocol clients, credentials, and actual tool execution.
Users interact with the registry through three distinct interfaces: MCP tools, A2A messages, or a standard HTTP API. The system uses SQLite for persistent storage and offers a CLI for administration, including tasks like metadata imports, batch refreshes, and JSON backups. It is designed to run locally using Node.js 24 or newer, and it does not require external accounts or API keys to function as a registry. By using tools like search_targets and get_target, clients can find specific capabilities and then connect directly to the intended target in their own environment.
What you can do with it
- 1Discovering specific documentation toolsAn AI client can search the registry for official documentation servers to retrieve their connection details and search tools.
- 2Centralizing agent and tool registrationsTeams can maintain a single catalog of remote MCP servers and A2A agent endpoints so updates are visible to all consumers.
- 3Migrating existing client configurationsDevelopers can import existing MCP settings from tools like Claude Code, Cursor, or VS Code into the centralized hub.
Written from the project's README. Every use case is checked against a quote from it.
Automated checks
Ran Nov 16, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachablejiind/agent-tcdh is public and reachablegithub.com/jiind/agent-tcdh ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)Apache-2.0spdx.org/licenses/Apache-2.0.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-08github.com/jiind/agent-tcdh ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubAgentTCDH
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.
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 the current npm release:
npm install --global agent-tcdh
agent-tcdh init
agent-tcdh serve
For a hub without global installation:
npx --yes agent-tcdh serve
To run the isolated demo from source:
git clone https://github.com/jiind/agent-tcdh.git
cd agent-tcdh
npm ci
npm run demo
Published GitHub releases provide built tarballs, source manifests, and checksums. See the v0.1.5 release notes for current source features, verification scope, and separate publication checks. Source commands below use the repository checkout; an installed CLI uses agent-tcdh in place of npm run cli -- or node dist/index.js.
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.
Environment management in v0.1.6
Save named hubs, edit source profiles, inspect registry/source/environment status, and track metadata freshness. Guarded history undo helps recover accidental registration changes. The guided setup command brings existing connections into a hub and prepares a selected consuming client.
agent-tcdh hub-profile save work --hub https://hub.example.com --token-env WORK_ADMIN --read-token-env WORK_READER --apply
agent-tcdh hub-profile use work --apply
agent-tcdh status
agent-tcdh setup --hub-profile work
agent-tcdh target observe --all --stale-only --apply
agent-tcdh registry history
See environment management for preview/apply behavior and v0.1.6 release notes for verification and compatibility. This version migrates SQLite to schema 3; back up the database before upgrading. Snapshot format 1 and MCP/A2A discovery remain compatible. Metadata observations describe consumer inspections, not verified execution.
Guided setup in v0.1.2
Version 0.1.2 adds guided setup, file-free registration, seven connection profiles, configuration import, presets, diagnostics, target editing, and registry comparison. Use the current npm package or this source checkout; earlier 0.1.1 installations do not include these commands.
npm run build
node dist/index.js init
node dist/index.js serve
In another terminal in the checkout, replace the example URL with your target:
node dist/index.js target add https://mcp.example.com/mcp
node dist/index.js connect codex --print
node dist/index.js connect claude-code --print
node dist/index.js connect gemini-cli --print
node dist/index.js doctor
init saves reusable settings. Quick add inspects remote metadata or records a local stdio command. connect generates Codex, version-specific OpenCode, Claude Code, Gemini CLI, Cursor, or VS Code settings; explicit file writes merge and back up existing configuration. doctor separates hub access, metadata checks, and unverified execution. See guided setup and diagnostics for credential references, non-interactive setup, and merging options. The additional client guide explains stdio bridge profiles and their verification scope.
Bring existing MCP settings into the shared registry or select bundled documentation targets:
node dist/index.js registry import-config /path/to/config.toml --select docs
node dist/index.js registry import-config /path/to/config.toml --select docs --compare --on-conflict skip
node dist/index.js registry import-config /path/to/config.toml --select docs --apply
node dist/index.js preset list
node dist/index.js preset import public-docs --select openai-docs --apply
node dist/index.js doctor --all --tag imported-config
node dist/index.js target edit openai-docs --add-tag team-docs --dry-run
node dist/index.js target disable openai-docs --dry-run
Configuration imports and presets default to offline previews; --apply registers the selected connections atomically. Import preserves the source file, replaces known inline environment/Bearer values with variable references, and reports unsupported settings. Review literal command arguments before applying. doctor --all explicitly inspects matching registrations with bounded concurrency and per-target results; it fetches remote metadata without executing tools/tasks. See configuration import and presets for formats, conflicts, and consumer-side credentials.
Edit labels/tags or enable/disable registrations without rewriting JSON files. Use --dry-run to review changes; new edit/state commands save against the observed registration version. See target management for conflict handling and deletion previews.
Use registry diff snapshot.json or an import preview with --compare to review added, changed, unchanged, and retained definitions against the hub. Comparison is read-only; see registry comparison for conflict policies and consistency limits.
Connection management in v0.1.3
Version 0.1.3 adds the following commands. Version 0.1.2 does not include them. Use this source checkout or a verified 0.1.3 artifact; see the v0.1.3 release notes for installation and publication checks.
connect --check FILEcompares a saved profile with the expected hub address, credential references, and bridge paths. See connection checks.disconnect CLIENT --file FILEpreviews named-entry removal;--applywrites it with an exact backup. See client disconnection.config backups --file FILElists matching backup metadata by modification time and provides restore preview commands. See backup discovery.config restore BACKUP_FILE --file FILEpreviews whole-file recovery;--applyrestores it and backs up the current file. See configuration restoration.
Batch operations and runtime identity in v0.1.4
Version 0.1.4 adds --version (-v) for the package version, --version --json for local runtime identity, and the same information in doctor reports. Version 0.1.3 does not include these additions. See runtime and version diagnostics.
Version 0.1.4 also supports target refresh --all to preview remote metadata updates across selected registrations; --apply saves changed definitions with per-target version checks. Filters, selection limits, bounded concurrency, skipped targets, and independent failures are reported. See batch metadata refresh. Use repeated --select ID options with doctor or target refresh to process an explicit group without enumerating the catalog; see explicit target selection. Version 0.1.3 does not include these additions.
Import management in v0.1.5
Bring existing MCP connections from Codex, Claude Code, OpenCode, Gemini CLI, Cursor, and VS Code configuration files, plus Gemini remote A2A definitions. Preview source-qualified choices and duplicates, use terminal checkboxes, and save a private profile for later synchronization. Optional metadata refresh/diagnosis and explicit stdio inspection complete the import flow; registry-wide duplicate cleanup is separately previewed.
agent-tcdh registry import-local --interactive --save-profile work --apply
agent-tcdh registry sync-local --profile work
agent-tcdh registry sync-local --profile work --apply --refresh --diagnose
agent-tcdh registry duplicates
These commands require 0.1.5 or later. See local client import, the complete management workflow, and release notes for locations, source conflicts, credential references, optional pruning, and explicit process authorization. Existing client source files are not edited. Stdio startup requires dedicated authorization in the consumer CLI.
MCP discovery
Connect your MCP client to http://127.0.0.1:3000/mcp.
| Tool | Purpose |
|---|---|
search_targets |
Search capabilities; filter by keyword, protocol, or tag; paginate results |
get_target |
Retrieve current capabilities, transport, address/command, and credential references |
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.
| Setting | Purpose |
|---|---|
HOST, PORT |
Listener address; defaults to 127.0.0.1:3000 |
AGENT_TCDH_DB_PATH |
Registry database location |
AGENT_TCDH_TOKEN |
Administrator Bearer token |
AGENT_TCDH_READ_TOKEN |
Separate read-only discovery token; requires an administrator token |
AGENT_TCDH_PUBLIC_URL |
Consumer-facing URL advertised in the A2A card |
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:
| Scope | Observed result | Evidence |
|---|---|---|
| Native platforms | Linux x64, macOS Apple Silicon/Intel, and Windows x64 passed regression and isolated package checks | Platform report |
| Public MCP services | Actual documentation calls succeeded for all six supplied providers through both hub discovery interfaces | Public MCP report |
| Agent selection | Codex selected and executed 3 and 5 relevant MCP/A2A targets from 10 local candidates, with no unrelated execution attempts | Selection report |
| Model-backed targets | Gemini CLI through an A2A test adapter and official TypeSafe Jev through an MCP test adapter each returned a real response | Model-target report |
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
- Guided setup, agent configuration, and diagnostics
- Local demo
- MCP/A2A agent registration compatibility
- Actual-agent verification
- v0.1.5 release notes, v0.1.4 release notes, v0.1.3 release notes, v0.1.2 release notes, 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
AgentTCDH MCP questions
What can I register in AgentTCDH?
You can register remote MCP servers, local stdio MCP commands, and A2A agent endpoints.
Does the registry execute the tools itself?
No, the hub only returns metadata; the consumer is responsible for target selection, protocol clients, credentials, and execution.
Does using the demo require an API key or external service?
No, the demo runs an isolated hub and requires no account, API key, external service, or model.