Connect Claude & ChatGPT
Hosted agents that speak MCP — Claude, ChatGPT, and others — connect to TAP with one URL:
https://mcp.tap.human.tech/mcpAdd it as a custom connector (leave OAuth Client ID and Secret empty) and authorize in your browser with your normal TAP login. That’s the whole setup — no API key to paste, no per-service configuration.
What your agent gets
Two tools, and every credential in your dashboard is reachable through them:
tap_discover— lists the credentials this connection can use and how to call each.tap_call— calls any API by credential name. TAP injects the secret, enforces your policies, and pauses writes for your approval. The agent never sees the secret.
Reads and writes follow the same policies, approvals, and audit log as every other TAP agent. The connection holds an OAuth token — never an API key or a credential value — and you can revoke it from the dashboard anytime.
Which connection to use
| Your agent | Use |
|---|---|
| Claude, ChatGPT, other hosted MCP clients | This page — paste the URL, authorize in the browser |
Claude Code, Cursor, scripts, anything that can curl | Quickstart — an API key and /instructions |
Both use the same credentials, policies, approvals, and audit log.
Note — this isn’t a per-service toolbox. You don’t install a separate Gmail, Stripe, and GitHub MCP server, each holding its own copy of your keys. You connect TAP once and reach every API through those two tools. It’s the same idea as TAP’s Socratic API: the agent works from a couple of generic calls and learns the rest from what TAP tells it, instead of a hand-written catalog per service.