Integrate

MCP Server

The ImportExportAPI MCP server connects any Model Context Protocol client (Claude, Cursor, VS Code, Windsurf, and more) to the API. One tool per endpoint, generated from the same OpenAPI spec as this reference, so an agent can call the API mid-task in natural language.

Get started in 30 seconds

It is a hosted server, one URL. Authenticate with the same API key you use for REST, sent as a Bearer header; calls are metered and rate-limited identically.

Hosted endpoint

https://mcp.importexportapi.com/mcp

Install in your client

Copy-paste setup for Claude Code, Cursor, VS Code, Claude Desktop, Windsurf.

Authentication

Bearer API key, created in the dashboard, same as REST.

Tools

12 tools, one per endpoint.

API reference

Every tool maps 1:1 to an endpoint documented here.

Install in your client

Replace sk_live_… with your key.

claude mcp add --transport http importexportapi https://mcp.importexportapi.com/mcp \
  --header "Authorization: Bearer sk_live_xxxxxxxxxxxxxxxxxxxx"

Cursor: ~/.cursor/mcp.json (or .cursor/mcp.json in the project)
VS Code: .vscode/mcp.json
Claude Desktop: claude_desktop_config.json. Desktop needs the mcp-remote bridge for HTTP servers
Windsurf: ~/.codeium/windsurf/mcp_config.json

Authentication

The server forwards your Authorization: Bearer sk_live_… header to the API gateway on every tool call. Listing tools is free; a call without a valid key returns the gateway's 401. Keys are created in the dashboard.

Review tool calls

Tools execute real, metered API calls. Keep your client's “approve before running” setting on.