Live · Model Context Protocol

One line gives your agent 45 APIs and scrapers.

Point Claude, Cursor, VS Code or any MCP client at mcp.apicodex.io and sign in. From then on you ask, and your agent pulls LinkedIn, Instagram, TikTok and Amazon data, scrapes any site, parses documents and checks emails, on your credits and under your limits.

Get started free Set up your client

Existing API keys work on day one: send one as the X-Api-Key header instead.

$ claude mcp add --transport http apicodex https://mcp.apicodex.io

01sign in at apicodex.io when your client asks
02approve the client on the consent screen
03your agent gets 7 tools

Why it matters

An agent is only as useful as what it can reach

Reading LinkedIn, Instagram or Amazon takes logins, proxies, JavaScript rendering and a fight with blocks. Every other data source is one more vendor, key, docs site and invoice. API Codex puts all of it behind one server your agent already knows how to use.

A separate vendor, account and key for each scraper and data API
Proxies, retries and headless browsers to keep scrapers alive
A tool wrapper and prompt for every API, rewritten when it changes
A different bill, quota and dashboard for each one

One URL in your client and one sign-in: 45 APIs and scrapers
Scraping, rendering and blocks are handled for you, live on every call
Three tools cover the whole catalog, and new APIs appear on their own
One credit balance, one quota, one usage log for REST and agents alike

Watch one ask become five calls

You ask for this week’s app reviews. Your agent looks up the right API, reads how to call it, pulls both stores, waits out a slow scrape and hands you the answer. You never see a request, a key or a proxy.

Finding and reading docs is free; only api_request spends credits.
Slow scrapes answer with a snapshot to poll, and polling your own is free.
Every call shows up in your usage with its cost.

youSummarize this week's App Store and Google Play reviews of our app. Anything about crashes?

list_apis search "app store reviews" free

App Store Data API
get_api_docs app-store /v1/apple/reviews free

takes the app's store url
api_request GET /app-store/v1/apple/reviews?url=…/id1452 25 cr

200 · 184 reviews
api_request GET /app-store/v1/google-play/reviews?url=… 25 cr

202 · still scraping, snapshot s_7f2c
api_request GET /app-store/v1/result?snapshot_id=s_7f2c free

200 · 243 reviews

	reviews	avg	crash mentions
App Store	184	4.4	6, all on iOS 19.1
Google Play	243	4.1	11, after v3.2 update

5 tool calls 50 credits billed to your team's MCP key

What you can hand over

Jobs your agent can take from here

Real tasks, the APIs your agent would reach for, and what one call to each costs. Every API page has more.

Setup

One line in your client

Give your client the server URL and it finds the sign-in by itself: you log in at apicodex.io, approve the client, and the tools show up. One server covers every API, so there is nothing to install per API.

Run this once, then type /mcp in Claude Code to sign in.

bash

claude mcp add --transport http apicodex https://mcp.apicodex.io

In claude.ai or Claude Desktop: Settings → Connectors → Add custom connector, then paste the server URL. Claude takes you to apicodex.io to sign in and approve it.

url

https://mcp.apicodex.io

Add the server to ~/.cursor/mcp.json (or .cursor/mcp.json in a project). Cursor asks you to sign in at apicodex.io the first time it connects.

mcp.json

{
  "mcpServers": {
    "apicodex": {
      "url": "https://mcp.apicodex.io"
    }
  }
}

Add the server to .vscode/mcp.json (or run "MCP: Add Server" and choose HTTP). VS Code asks you to sign in at apicodex.io the first time it starts the server.

.vscode/mcp.json

{
  "servers": {
    "apicodex": {
      "type": "http",
      "url": "https://mcp.apicodex.io"
    }
  }
}

Add the server to ~/.codeium/windsurf/mcp_config.json. Windsurf asks you to sign in at apicodex.io the first time it connects.

mcp_config.json

{
  "mcpServers": {
    "apicodex": {
      "serverUrl": "https://mcp.apicodex.io"
    }
  }
}

For clients without OAuth support, and for headless or CI agents: send an existing API key as the X-Api-Key header instead. Calls bill to that key.

mcp.json

{
  "mcpServers": {
    "apicodex": {
      "url": "https://mcp.apicodex.io",
      "headers": { "X-Api-Key": "YOUR_API_KEY" }
    }
  }
}

claude code

claude mcp add --transport http apicodex https://mcp.apicodex.io --header "X-Api-Key: YOUR_API_KEY"

Tools

7 tools, every API in the catalog

There is no tool per API to install or pick. Ask for what you need: your agent finds the API with list_apis, reads its endpoints with get_api_docs and calls it with api_request, new APIs included.

list_apis Browse the catalog: each API's slug, category, credits per call and docs.
get_api_docs Endpoints, parameters and examples for one API, from its OpenAPI spec.
api_request Call any endpoint (e.g. GET /countries/v1/all) through the gateway, metered and rate-limited exactly like a REST call. metered like REST
get_usage Credits used and left this billing period, a per-API breakdown and recent errors.
get_account Your plan, limits and billing period, and which key MCP calls bill to.
list_recent_requests The last 7 days of calls, with status, latency and credits.
list_api_keys Your team's keys, masked, and their status.

Authentication

OAuth by default. Your API key still works.

Billing

Same credits as REST

An API call through MCP costs what the same REST call costs, from the same team balance. The free plan’s 1,000 credits a month cover MCP too, no credit card.

See every API’s credit cost

OAuth session: Your team's MCP key, created automatically. It doesn't count toward your key limit.
API-key session: The key the client sends, like any REST call.
/v1/result polls: Free for scrapes you started, as on REST.
Other tools: Free. Only api_request spends credits.

Get started

Hand it over.

Add mcp.apicodex.io to your client and sign in. 1,000 free credits every month, every API included, no credit card.

Get started free Browse the APIs