DataCore A2A
vn.datacoreClaim this server
接入你的智能体
新增此伺服器
The publisher's own command. Not a PlugMCP endpoint.
用我們的金鑰與日誌託管一份副本。
Local command
uvx datacore-a2a-mcp==0.2.5Credentials from the publisher
- DATACORE_A2A_URL — Base URL of the DataCore gateway, for example https://gateway.datacore.vn. It must be the gateway — pointing straight at the orchestrator is always rejected with 401.
- DATACORE_API_KEY — Long-lived credential shaped dck_..., created with POST /mcp/credentials — see the README. The server exchanges it for short-lived mandates and refreshes them itself, so it never has to be replaced on expiry. Either this or DATACORE_MANDATE is required.
- DATACORE_MANDATE — A hand-issued AP2 mandate, the older way. Not refreshed: when it expires you replace it and restart. Use it only if you were set up this way; otherwise use DATACORE_API_KEY.
- DATACORE_SKILLS — Comma-separated skill ids to narrow the tools that get exposed, or * for every skill the endpoint returns. Empty uses the default four.
- DATACORE_TIMEOUT — Per-request timeout in seconds. Defaults to 30.
Claude Code has no install link for a local command. Copy the command below and run it in a terminal.
shClaude Code
DATACORE_A2A_URL=<value> DATACORE_API_KEY=<secret> DATACORE_MANDATE=<secret> DATACORE_SKILLS=<value> DATACORE_TIMEOUT=<value> claude mcp add vn.datacore-datacore-a2a -- uvx datacore-a2a-mcp==0.2.5Run in a terminal.
jsonClaude Desktop
{ "mcpServers": { "vn.datacore-datacore-a2a": { "command": "uvx", "args": [ "datacore-a2a-mcp==0.2.5" ], "env": { "DATACORE_A2A_URL": "<value>", "DATACORE_API_KEY": "<secret>", "DATACORE_MANDATE": "<secret>", "DATACORE_SKILLS": "<value>", "DATACORE_TIMEOUT": "<value>" } } }}claude_desktop_config.json
Local · pypiPublisher installStep-by-step: add this in Claude
Remote URL or a command on your machine? How the two installs differ
Server facts
Local- Transport
- stdio
Tools
Tools
No tool list yet. Remote servers get one after the first health check.
FAQ
