Get Started

# MCP server

Connect Claude, Cursor, or another AI coding assistant to your account so it can read the docs and run real checks while it builds your integration.

The MCP server connects an AI coding assistant (Claude, Cursor, VS Code, and other MCP clients) to your MexCheck account. While it writes your integration, the assistant can read these docs, run real checks to see the exact responses, and look at your plan and balance.

It is a tool for building the integration, not a part of it. In production your server calls the REST API with an API key, as the rest of these docs describe.

## Connecting

Add this URL to your assistant as a remote MCP server:

URL

```text
https://mexcheck.com/mcp
```

Claude Code

```bash
claude mcp add --transport http mexcheck https://mexcheck.com/mcp
```

Cursor (.cursor/mcp.json)

```json
{
  "mcpServers": {
    "mexcheck": { "url": "https://mexcheck.com/mcp" }
  }
}
```

There is no API key to paste. The first time the assistant uses the server it opens your browser, you log in, and you choose which account it acts as: your personal account or an organization you belong to. Each connection acts as one account. To use another one, connect again and choose it.

Listing the tools and reading the docs works before you log in. The login starts the first time the assistant uses a tool that touches your account.

## Tools


| Tool | What it does |
| --- | --- |
| `rfc_validate`, `rfc_verify`, `rfc_profile`, `rfc_find_zip`, `rfc_sat_lists`, `cfdi_verify`, `csf_verify` | The RFC, CFDI, and Constancia de Situación Fiscal endpoints, answered by SAT. |
| `curp_lookup`, `curp_search` | The CURP endpoints, answered by RENAPO. |
| `ine_verify` | The voter ID endpoint, answered by INE. |
| `cfe_verify` | The electricity receipt endpoint, answered by CFE. |
| `geo_zip`, `geo_zip_search` | The zip code endpoints, answered from Correos de México's catalogue. |
| `list_docs`, `read_doc`, `get_openapi_operation` | These docs as Markdown, grouped by product, and each endpoint's OpenAPI definition. |
| `get_account`, `list_plans` | The connected account's plan, credits used, balance, and what each check costs it. |
| `create_api_key` | A new API key for your server, shown once. Keys are listed and revoked in your dashboard. |
| `charge_saved_card` | Adds balance by charging the saved card. Only if you allowed it when connecting, up to your daily limit. |
| `create_plan_checkout`, `create_balance_checkout`, `get_billing_portal_link` | Links to Stripe pages where you subscribe, add balance, or manage billing. |


Each check tool takes the same fields as its REST endpoint and returns the same JSON. Webhook delivery and /rfc/verify-batch are only in the REST API, because a tool has to answer inside the conversation.

## Billing

A check run through MCP is a real lookup and costs the same credits as the REST call, from the connected account's plan and balance. The docs and account tools are free.

Beyond that, the billing tools only return a link: nothing is charged, and no plan changes, until you open the link and confirm on Stripe's page.

The one exception is yours to grant. When you connect, you can let the assistant add balance by charging the account's saved card, up to a daily limit you set ($100 USD unless you change it). It is off unless you tick the box, the limit resets at midnight UTC, and you can see it and end it under Connected apps.

## Organizations

A connection to an organization follows your role there, as the dashboard does. Admins and developers can run checks. Admins and billing members can use the billing tools. A role change applies to the next request, and leaving the organization ends the connection.

## Privacy

What a check returns (names, CURPs, tax data) goes to the assistant you connected and to the company that runs it. Connect assistants you would trust with that data.

## Disconnecting

Open [API Keys](/dashboard/api-keys) in your dashboard. Connected apps are listed there, each with a Disconnect button that ends its access at once.