DataCore A2A — MCP server

Lets an MCP client (Claude Code, Claude Desktop, VS Code, Cursor…) use DataCore's data skills as native tools: Vietnamese address normalization, address validation, company lookup, embedding generation.

MCP client (stdio) ──► datacore-mcp ──HTTPS──► DataCore API

Zero dependency, Python 3.9+.

Installation

pip install datacore-a2a-mcp

Related MCP server: database-remote-mcp

Prerequisites

This server is a client, not a service. It needs a DataCore endpoint and a mandate token to call — contact 3TIT to be issued one. Without those two, the server starts up and exits immediately with a message saying which variable is missing.

Configuration

Use the exact URL DataCore issued along with the mandate. A different endpoint will not accept your mandate and will return 401.

Claude Code / Claude Desktop

Add to .mcp.json (project) or the Claude Desktop config:

{
  "mcpServers": {
    "datacore-a2a": {
      "command": "datacore-mcp",
      "env": {
        "DATACORE_A2A_URL": "https://api.example.com",
        "DATACORE_MANDATE": "<mandate-token>"
      }
    }
  }
}

Tools

The tool list is generated from the endpoint, not hardcoded here — so when DataCore adds a skill, restart the server and the new tool appears.

By default, 4 skills wired to the real backend are exposed:

Every tool is read-only (readOnlyHint: true): nothing is written, deleted, or created. Calling again with the same input yields the same result.

Three other DataCore skills (company.graph, company.financial-sankey, company.news) are deliberately not exposed: they are currently returning mock/deterministic data. If you want to see them for testing, set DATACORE_SKILLS="*", and don't trust the results.

Examples

The three prompts below run through three different tools:

1. Address normalization — "Normalize this address into province/district/commune: So 1 Ly Thai To, Hoan Kiem, Ha Noi"

2. Company lookup — "Find company information for tax ID 0100109106 and tell me its operating status"

3. Embedding — "Generate an embedding for this industry description and tell me how many dimensions the vector has: bán buôn thiết bị điện tử"

Security model

This server carries the mandate token as-is in the X-AP2-Mandate header for DataCore to verify, and never sets any other authorization header on its own. A client is not a place to grant itself permissions — it only forwards what it was issued, and all allow/deny decisions live on the DataCore side.

The mandate is a bearer credential: whoever holds it can call exactly the skills in it, up to the spend cap, until it expires. Treat it like a password — don't commit a .mcp.json with the token filled in, and if your client supports it, read it from a secret manager instead of leaving it inline.

This package never writes the token to logs, not even partially; the text content you send is not logged either. That is a commitment for the process running on your machine — the service side is a different matter, and PRIVACY.md states plainly what it stores.

Troubleshooting

Logs go to stderr, prefixed with [datacore-mcp]. stdout is the JSON-RPC channel.

Reporting security issues

mcp-security@datacore.vn. Don't open a public issue for security bugs.

If you suspect your mandate has leaked, report it immediately — don't wait until it expires. We need to know so we can handle it on the service side.

Privacy

See PRIVACY.md. In short: this package runs on your machine, stores nothing, sends nothing anywhere except the DataCore endpoint you configure yourself, and never writes the mandate token to logs.

License

MIT — see LICENSE.