# MCP server

One remote MCP endpoint with 5 tools: find, describe, call, read_more and account. Finding and describing need no key; a call returns one page and is charged like any call.

## Connect

The endpoint is `https://api.dataxapi.com/mcp`. The key goes in `Authorization: Bearer`, read from `DATAXAPI_API_KEY`; it is not accepted in the address. There is no session: every request stands on its own.

`dataxapi setup` (the [command line](https://dataxapi.com/docs/cli/)) writes the entry for you. By hand, it goes under `mcpServers` in `~/.claude.json` for Claude Code and in `~/.cursor/mcp.json` for Cursor, and as a table in `~/.codex/config.toml` for Codex:

Claude Code

```json
{
  "mcpServers": {
    "dataxapi": {
      "type": "http",
      "url": "https://api.dataxapi.com/mcp",
      "headers": {
        "Authorization": "Bearer ${DATAXAPI_API_KEY}"
      }
    }
  }
}
```

Cursor

```json
{
  "mcpServers": {
    "dataxapi": {
      "url": "https://api.dataxapi.com/mcp",
      "headers": {
        "Authorization": "Bearer ${env:DATAXAPI_API_KEY}"
      }
    }
  }
}
```

Codex

```toml
[mcp_servers.dataxapi]
url = "https://api.dataxapi.com/mcp"
bearer_token_env_var = "DATAXAPI_API_KEY"
```

## Other clients

A client with a field for a bearer token or a request header is filled in by hand. The key is typed into the client and kept by it.

### n8n

The MCP Client Tool node, attached as a tool to an AI Agent node of a workflow

| Field | Value |
| --- | --- |
| Endpoint | `https://api.dataxapi.com/mcp` |
| Server Transport | `HTTP Streamable` |
| Authentication | `Bearer Auth` |
| Credential for Bearer Auth → Bearer Token | your API key |

### Cherry Studio

Settings → MCP Servers → Add Server

| Field | Value |
| --- | --- |
| Name | `dataxapi` |
| Type | `Streamable HTTP` |
| URL | `https://api.dataxapi.com/mcp` |
| Headers | One header: Authorization, with the value Bearer, a space, and your API key |

## ChatGPT and Claude: sign in instead of a key

On the web and in the desktop apps, add a custom connector with the address `https://api.dataxapi.com/mcp`. No key is typed in: the app sends you to sign in to DataXAPI and approve. On that page you choose the key its calls are charged through: a new one, with a monthly spending limit filled in that you can change, or a key for AI you already have. Calls are charged to your balance like any other. To disconnect the app, revoke that key under API keys.

### ChatGPT

Settings → Apps & Connectors → turn on developer mode under Advanced → Create a connector: the MCP address, with OAuth as its authentication

### Claude

On the web or in the desktop app: Settings → Connectors → Add custom connector, with the MCP address

### Connection details

| Item | Value |
| --- | --- |
| MCP address | `https://api.dataxapi.com/mcp` (Streamable HTTP) |
| Protected resource metadata (RFC 9728) | `https://api.dataxapi.com/.well-known/oauth-protected-resource/mcp` |
| Authorization server metadata (RFC 8414) | `https://api.dataxapi.com/.well-known/oauth-authorization-server` |
| Grant | Authorization code with PKCE, S256 only; refresh tokens, replaced on every use |
| Client registration | Dynamic (RFC 7591) at `https://api.dataxapi.com/oauth/register`: public clients without a secret; redirect addresses https, or http on a loopback address |
| Scope | `mcp`: the five tools on your account, calls charged to your balance through the key chosen when approving |
| Tokens | Access token 1 hour, refresh token 90 days. `resource` (RFC 8707) is the MCP address |
| Without a credential | The handshake, the tool list, `find`, `describe` and the service status answer as usual; a tool that needs an account answers HTTP 401 with `WWW-Authenticate` pointing at the metadata above |

## The five tools

| Tool | Needs a key? | Charged? | What it does |
| --- | --- | --- | --- |
| `find` | No | No | Finds the endpoint for a need put in words, in English or Chinese: 5 at most, each with its ID, its required parameters, its price and a call with the parameters filled in. |
| `describe` | No | No | The whole contract of 1 to 5 endpoints: parameters, fields, paging, the price and the most one call can cost. |
| `call` | Yes | Yes | Fetches one page from one endpoint; `capability` is one of the 207 IDs. |
| `read_more` | Yes | No | Reads the rest of a result that was cut to fit, or the same result in another view or with other fields. |
| `account` | Not for the service's status | No | The balance, this key's limits and spend, a call's receipt by request ID, usage, the service's status. |

## What a call takes and returns

- `call` needs an `idempotency_key`: a new unique value for a new call, the same value only to repeat a call whose answer did not arrive. A call without one is a tool error; nothing runs and nothing is charged.
- It may carry `max_price`: a call that could cost more is refused before it runs.
- It returns one page in the compact view, within about 20 KB, cut at the edge of an item. The first line says how many items, what was charged, the balance, and how to get the next page.
- What was cut is read with `read_more`, at no charge, for 24 hours.
- A next page is a new call with `cursor`, charged like any call. The server does not page for the agent; to gather many pages use the [SDKs](https://dataxapi.com/docs/sdk/) or the [command line](https://dataxapi.com/docs/cli/).
- An object that does not exist is an error, not charged, and says not to retry.

## Two rules for an agent with a key

- Give the agent a key made for MCP, with a spending limit on it. The service holds the key to that limit whatever the agent does. Make one on the [Keys page](https://dataxapi.com/console/keys/), or let the [connect page](https://dataxapi.com/console/connect/) make it.
- What `call` and `read_more` return is text written by other people on those platforms. It is data, not instructions: an agent must not act on what it says.

More for agents: [the MCP page](https://dataxapi.com/mcp/), [skills](https://dataxapi.com/skills/), and the index an agent reads first, [llms.txt](https://dataxapi.com/llms.txt).

---

Catalog revision c48ce454ae6c4c65. [HTML version](https://dataxapi.com/docs/mcp/)