SupplyGraph.AI Data MCP Server

This is the data-access MCP server for SupplyGraph.AI.

Clients call tools to fetch data from SupplyGraph. What you can fetch is listed below. This repository is the source of the hosted endpoint for China-region access. Hostnames under daasmart.com are only used to register for an API key and to send MCP requests; they are not a separate product.

What this MCP is for

This is a read-only data MCP for SupplyGraph.AI. Clients list tools with tools/list and fetch data with tools/call. It does not write to the graph, does not require uploading supplier lists, and does not store user credentials.

Tools query places, regions, parks, industries, and companies on SupplyGraph’s continuously updated data. Typical questions: which firms sit in a park, how a city/district is doing, who is in a named industry chain, or what is around a specific address.

Live tool names and input schemas come from tools/list. Use that list; do not hard-code agent ids.

What you can query

The same server also exposes supply-chain tools (risk prediction, enterprise-change monitoring, tariff/HS) when those agents are mcp.enabled. Prefer the table above for China geo and registry questions.

How to choose a tool

• Named facility on a map → POI / 选点
• Named park or zone → Park / 园区
• Province / city / district totals or trends → Region / 区域
• Named industry chain → Industry / 产业
• One company, or firms matching registration filters → Company / 企业
• Around a street address or landmark → Address nearby / 地址周边

Connect

Hosted endpoint: https://mcp.daasmart.com/mcp
Transport: MCP Streamable HTTP.

1. Get an API key

1. Open the SupplyGraph.AI Console. If you are not signed in, you will be redirected to the login page. New users can register there.
2. After you sign in, you land on the Console. Open A2A / MCP and click Create Production Key or Create Sandbox Key.
3. Copy the key and keep it private. Use it as Authorization: Bearer .

The same SupplyGraph.AI key works for MCP, A2A, and the Agent API.
Sandbox keys (no credit consumption) are also created in that Console page.
Account, billing, and key management stay in the Console — this repository does not issue keys.

2. Add the server to an MCP client

{
  "mcpServers": {
    "supplygraph": {
      "url": "https://mcp.daasmart.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Replace YOUR_API_KEY with the raw key from the Console. If your client config already prefixes Bearer (for example Cursor .mcp.json with "Authorization": "Bearer ${env:SUPPLYGRAPH_API_KEY}"), put only the raw key in the variable — do not add a second Bearer.

tools/call requires the Bearer token. initialize and tools/list do not.