Touchque MCP: add it to Claude and Cursor
Add one URL to Claude, Cursor or any MCP client and sign in once with Touchque. The AI then knows who you are, your organization, your role and which Touchque features are on for you. It reads your app's code, picks the right SDK, writes the integration and checks it against your live workspace.
The address is
https://api.touchque.com/mcp. There is no API key to paste: you sign in with Touchque in the browser, and the token is for this server only.Add it
- Claude Code: run the command under Claude Code, then
/mcp, pick touchque and Authenticate. The browser opens Touchque's sign-in; after it, pick the organization and allow. - Claude (claude.ai and the desktop app): Settings → Connectors → Add custom connector, name
Touchque, URLhttps://api.touchque.com/mcp, then Connect and sign in. - Cursor: add it to
~/.cursor/mcp.json(or.cursor/mcp.jsonin a project). Cursor shows Needs login next to it: click it and sign in. - VS Code, Windsurf and others: any client that speaks Streamable HTTP with MCP authorization takes the URL. A client that runs only local (stdio) servers reaches it through
mcp-remote.
Signing in and what it may do
- Your AI tool finds Touchque SSO from the server and registers itself.
- You sign in at sso.touchque.com as usual: password, passkey or phone.
- The consent screen names the AI tool, lets you pick one of your organizations and lists what it may do.
- The token lasts 10 minutes and your AI tool renews it in the background. End the connection any time under your Touchque account's AI access; your organization's AI tool rules apply.
| Permission | What it allows |
|---|---|
touchque:read | Your organization, role, features and workspace setup. Never a secret. |
touchque:write | Changes you ask for, such as an API key or a redirect URI. Each one asks you first and, as in the dashboard, your phone. |
Every call runs as you, in your active organization, and sees only what the dashboard shows you.
Slash commands
| Command | What it does |
|---|---|
/touchque-setup | Who you are, what is on and set up, which SDK fits this project, what to do next |
/add-phone-approval | Phone approval (a push with number matching) on sign-in or a sensitive action |
/add-passkeys | Passkeys: enrollment and phishing-resistant sign-in or step-up |
/add-touchque-login | Touchque Login: hosted sign-up and sign-in (OpenID Connect) for your customers |
/check-integration | Checks your code against the SDK rules and your live workspace |
In Claude Code they appear as /mcp__touchque__touchque-setup and so on. You can also just ask: "add Touchque phone approval to the transfer endpoint".
Tools
| Tool | What it gives the AI |
|---|---|
touchque_whoami | You, the active organization, your role, every feature on or off, your API key, webhook, action types, Touchque Login and your other organizations. The same facts come in the server instructions when you connect, so small account questions need no call |
touchque_use_organization | Moves the connection to another of your organizations |
touchque_workspace_setup | API keys (never a secret), webhook, action types, passkey domain, Touchque Login apps and redirect URIs; one part, or one action type |
touchque_search_docs | Searches these docs in English and Turkish and the SDK READMEs: the best three sections; page reads one page |
touchque_pick_sdk | The SDK for the project, whether it is published, the install command, import line and requirements |
touchque_generate_integration | The SDK's own guide for a feature and language, with this workspace's real values and what is missing first; refuses a feature that is off |
touchque_check_integration | Checks code against the live workspace (feature, key, action types, redirect URIs, webhook) and the checklist |
touchque_explain_case | Explains a "Why?" case code |
touchque_define_action_type, touchque_create_api_key, touchque_add_redirect_uri | Changes, only when you ask (touchque:write). The first call only says what will happen and gives a confirm token; the AI asks you, and only your yes makes the change. A new API key and a redirect URI also ask your phone |
touchque_send_test_approval, touchque_wait | A test approval on your own phone, only when you ask; touchque_wait waits for its answer or for the phone's yes to a change |
get_touchque_docs, get_sdk_types | An SDK's README (the server SDKs, web and react) or one part of it; the type names or one declaration |
touchque_help | What Touchque is and which tool answers what |
The older names touchque_features, touchque_list_organizations, touchque_change_status, touchque_test_approval_status and validate_integration still answer, as other names of the tools above.
Claude Code
claude mcp add --transport http touchque https://api.touchque.com/mcpCursor: ~/.cursor/mcp.json
{
"mcpServers": {
"touchque": { "url": "https://api.touchque.com/mcp" }
}
}Clients that run only local (stdio) servers
{ "command": "npx", "args": ["-y", "mcp-remote", "https://api.touchque.com/mcp"] }