Skip to main content
Up2Data ships a Model Context Protocol server that exposes the entire Gateway API as tools: enrich, search, engagement, batch, Signals, and account. Give your agent an API key and it can pull live B2B data mid-conversation. The hosted endpoint is embedded in the Gateway — same API keys, credits, rate limits, and pay-on-success semantics as REST.
This is the API MCP (https://api.up2data.ai/mcp) — billable enrich/search/Signals tools. It is not Mintlify’s docs-search MCP (read-only help for this documentation site).
Prefer the terminal over an agent? The same package is a full shell CLI.
Tool calls are billable. Enrich and search charge on success; Signal checks charge per run. Prefer up2data_account_get to confirm balance before large searches.

Get an API key

Create a key in the dashboard. New accounts start with free trial credits.

Install

Cursor (remote)

Add to ~/.cursor/mcp.json (or project .cursor/mcp.json):

Cursor (stdio / npx)

Credentials live in ~/.config/up2data/credentials.json. You can still pass UP2DATA_API_KEY in env to override. The same credentials power the shell CLI.

Claude Code

Or stdio (after npx -y up2data login):

Claude Desktop

In Claude Desktop → Settings → Developer → Edit Config (after up2data login):

VS Code

Add to .vscode/mcp.json:

Quick try

Once connected, ask your agent:
Use Up2Data to enrich https://linkedin.com/in/satyanadella and summarize the current role.
The agent should call up2data_profile_enrich (1 credit on success) and return structured profile data plus meta.creditsUsed / meta.creditsRemaining.

Tools & credits

All tool names are prefixed with up2data_. Failed scrapes are free (pay-on-success) unless noted.

Enrich

Search accepts either structured filters or a LinkedIn / Sales Nav URL — not both.

Batch

Signals & account

Full pricing context: Credits & billing. Signal check billing: Signals.

Auth notes

  • Prefer Authorization: Bearer <key> (primary). X-API-Key is also accepted.
  • Remote clients must send the key as an HTTP header on every request to /mcp.
  • The stdio package reads a key from up2data login (~/.config/up2data/credentials.json) or UP2DATA_API_KEY, then forwards it as a Bearer token to the Gateway.
  • Optional overrides: UP2DATA_BASE_URL (default https://api.up2data.ai), UP2DATA_APP_URL (default https://up2data.ai).

Troubleshooting

REST parity

Every MCP tool maps 1:1 onto a /v1/* route. Prefer MCP for agents, the CLI for shell scripts, and REST for production pipelines. OpenAPI: https://docs.up2data.ai/openapi.yaml.