MCP server Early access

# Latam APIs, as MCP tools.

We are preparing remote MCP access to data APIs from Argentina, Mexico and Chile with your ApiNitro account. Client compatibility and API availability are not yet verified.

[Request early access](https://apinitro.com/en/contact/?topic=mcp) [View API Catalog](https://apinitro.com/en/apis/)

**MCP**`https://apinit.ro/mcp`

Early access Early access is in preparation. Client compatibility and API availability are not yet verified. These examples describe the planned integration.

Planned workflow

## Connect. Authorize. Call.

01

### Add the server

The planned endpoint is `https://apinit.ro/mcp`. Confirmed setup instructions will accompany the pilot.

02

### Sign in with ApiNitro

The planned OAuth flow uses your ApiNitro login. You select an account and authorize specific APIs and a credit budget for each integration.

03

### Your agent calls tools

Authorized APIs will appear as tools with typed inputs. Asynchronous tool results will include a request ID and a status in `structuredContent`.

Connect your client

## One URL. Your MCP workflow.

The initial validation targets are Claude Code, Cursor and a reference client. Confirmed versions and setup instructions will accompany early access.

Claude Code Cursor Other assistants Custom client

Copy

    # Terminal
    claude mcp add --transport http apinitro https://apinit.ro/mcp

Proposed setup for the pilot. The OAuth flow and supported client version still need end-to-end validation.

Copy

    // .cursor/mcp.json
    {
      "mcpServers": {
        "apinitro": {
          "url": "https://apinit.ro/mcp"
        }
      }
    }

Proposed configuration for the pilot. Connection and authorization behavior still need end-to-end validation.

Copy

    # Add a custom connector / app
    Name:       ApiNitro
    Server URL: https://apinit.ro/mcp
    Auth:       OAuth

Compatibility with ChatGPT and other assistants has not been established. Ask us about your client before relying on this proposed configuration.

Copy

    Server URL: https://apinit.ro/mcp
    Transport:  Streamable HTTP
    Auth:       OAuth 2.1 (Protected Resource Metadata)
    Scope:      APIs explicitly authorized for this integration

A custom client must pass the published transport and OAuth tests before it is listed as supported.

Tools

## Your catalog, as tools.

The planned tool catalog is limited to the APIs you authorize for an integration, within your account permissions. Tool names follow the API route.

Tool

What it does

`list_apis`

Lists the APIs authorized for this integration, with country, category and input schema.

`{country}_{category}_{api}`

One tool per authorized API, mirroring `POST apinit.ro/{country}/{category}/{api}`. Validates input and returns a result or a request ID.

`get_result`

Retrieves the structured JSON result of an asynchronous request when it completes.

`get_credits`

Returns your organization's available credit balance.

Planned security & control

## Enterprise controls, agent speed.

### OAuth sign-in

The design uses ApiNitro sign-in without API keys in prompts. Users will be able to revoke each integration authorization.

### Scoped to your APIs

Each authorization will bind the user, account and client, with explicit APIs and permissions. An enabled account API is not automatically available to every integration.

### Same credits and controls

Tool calls will use the same admission controls as REST: credits, rate limits and idempotency.

### Spending caps

Each durable authorization will have a credit budget. Reconnecting or renewing a token must not reset it.

### Structured output only

The design returns typed fields instead of raw third-party pages to reduce prompt-injection exposure.

### Private by design

The design keeps results isolated to the account and records an audit trail for each call.

MCP or REST

## Same APIs. Two front doors.

### Use MCP when…

-   An AI assistant or agent decides which API to call.
-   You want tools discovered automatically from your catalog.
-   Users authorize access with their own ApiNitro login.

### Use REST when…

-   Your backend calls a known API on a fixed flow.
-   You need webhooks, signed requests and the SDK.
-   You integrate API calls into production workflows.

FAQ

## Questions

What is an MCP server?

The Model Context Protocol (MCP) is an open standard that lets AI applications discover and use external tools. The planned ApiNitro MCP server will expose explicitly authorized APIs as tools. Compatibility must be verified for each client and version.

Do I need an ApiNitro account?

Yes. The planned flow requires an ApiNitro account and a separate authorization for each integration. Early access is still in preparation. [Request early access](https://apinitro.com/en/contact/?topic=mcp).

How are MCP calls billed?

The planned model uses account credits under the same billing policy as REST for the same API. Terms and availability will be confirmed before activation.

Which countries and APIs are available?

MCP availability is not yet verified. Planned products and coverage are described in the [API Catalog](https://apinitro.com/en/apis/).

Is my data shared with other customers?

The design isolates requests and results by account, without sharing them between customers. Isolation must pass validation before the pilot opens.

Can I still use the REST API?

MCP is planned as an additional way to use the same APIs and credits as REST. You will be able to choose an interface for each integration once its availability is confirmed.

## Give your agents Latam.

[Request early access](https://apinitro.com/en/contact/?topic=mcp) [Explore APIs](https://apinitro.com/en/apis/)