ETL: Connect a Client to MCP

Pick your client below and follow its setup page. Every client connects to the same endpoint: https://api.xplenty.com/YOUR_ACCOUNT_ID/api/mcp Replace YOUR_ACCOUNT_ID with your account subdomain or numeric id (the value in your dashboard URL). New to this? The Quickstart walks through Claude Code in about five minutes. For token and OAuth detail, see Authentication.

Compatibility

Client	How to add	Auth	Notes
Claude Desktop	OAuth custom connector, one-click `.mcpb` extension, or `mcp-remote` bridge	OAuth or token	OAuth connector recommended; extension or token bridge for token-based setups.
Claude.ai web	Native custom connector	OAuth	Connects from Anthropic’s cloud; endpoint must be reachable.
Claude Code	Native remote (Streamable HTTP)	OAuth or token	No bridge needed.
ChatGPT	Developer-mode custom connector	OAuth	Plans that expose connectors / developer mode.
Cursor	Native remote `mcp.json`	Token (or OAuth)	`mcp-remote` bridge for older builds.
Perplexity	Custom connector (Remote)	OAuth	Availability depends on your Perplexity plan.
OpenAI Codex	`mcp-remote` bridge	Token	stdio client, needs the bridge.
MCP Inspector	Native remote (Streamable HTTP)	Token	Debugging tool, not an AI agent.
Any other client	Native remote, or `mcp-remote` bridge	OAuth or token	Generic instructions for any MCP client.

MCP Inspector is not an AI agent. It is a debugging tool from the MCP project team (npx @modelcontextprotocol/inspector) that opens a local UI for listing and calling tools directly. Use it to confirm the endpoint works before wiring up a real agent.

Last modified on October 27, 2026

Get started

Connect a client

Authentication

Tool reference

Troubleshooting

ETL: Connect a Client to MCP

Compatibility

​Compatibility

Compatibility