Guide: Connect datapoint.market in Claude (or any MCP client)

This connects the management MCP so an agent can create and manage your endpoints, authenticated as your provider account via OAuth. (This is the control plane — not a paid relay.)

One-time setup

1. In Claude: Settings → Connectors → Add custom connector.
2. Paste the MCP server URL:

   https://api.datapoint.market/mcp
   

3. Connect. Claude discovers the OAuth metadata, opens the authorize page, and you log in with your datapoint.market account (magic-link email — a new account is created automatically if you don’t have one) and approve.
4. Done. The tools below are now available in chat.

The dashboard also has a “Use in Claude” panel with the URL and a copy button.

How the auth works (for the curious / for other clients)

Standard OAuth 2.0 authorization-code + PKCE, discoverable per the MCP spec:

• GET /.well-known/oauth-protected-resource and GET /.well-known/oauth-authorization-server — discovery metadata
• POST /oauth/register — dynamic client registration (RFC 7591)
• GET /oauth/authorize → consent → POST /oauth/token — code → access token
• The token is an opaque, revocable bearer (emoauth_…); send it as Authorization: Bearer <token> to POST /mcp.

If you call POST /mcp without valid auth you get 401 with a WWW-Authenticate header pointing at the metadata — that’s the cue for an MCP client to start the OAuth flow.

Auth is per-capability, not all-or-nothing. You can connect, browse (search_marketplace, get_endpoint_sample, quote_endpoint) and buy (call_endpoint, call_mcp_tool) with no account — the payment credential in the args (a signed X-PAYMENT or a buy-job spk_) is the authorization, mirroring the accountless raw-x402 flow. Selling and custodial wallet/budget tools (create_*, publish, create_wallet, create_buy_job, …) require a verified email account: calling one without it returns the 401 OAuth challenge, which funnels you into email login. (A wallet-only account is verified for payouts but can’t mint keys or run those Tier-2 tools.)

What you can do once connected

The management tools (full details in MCP tools reference):

• list_endpoints
• create_api_relay, create_mcp_wrapper
• publish_endpoint
• update_endpoint, pause_endpoint, resume_endpoint, delete_endpoint
• list_automation_keys, revoke_automation_key

When you publish through Claude, Claude also helps set up the buyer-facing sample (see Publishing): it composes the sample_request, can run the publish-time probe to preview the synthetic sample before it goes live, and summarizes what buyers will see — then asks you to confirm before publishing. Claude never invents the data shape; the structure always comes from your origin (or an example you provide), shown honestly as synthetic by default.

Example things to say in chat:

• “List my endpoints.”
• “Create a paid relay over https://api.me.com/v1/quote at $0.02 on Base mainnet, payout to 0x…. It’s read-only, so enable sampling and show buyers a synthetic example.”
• “This endpoint is sensitive — keep the sample synthetic, but offer 3 free trial calls.”
• “Show me what the sample will look like before you publish.”
• “Drop the price on my weather endpoint to $0.01.”
• “Pause the test relay, then delete the old one.”

Alternative: no browser, just a key

For headless agents, skip OAuth and use an automation key:

• Bootstrap with a wallet signature: POST /auth/wallet/challenge → sign → POST /auth/wallet/verify returns an automation key, or mint one in the dashboard.
• Send it as Authorization: Bearer empk_… to POST /mcp.

See Publish an endpoint next.