One

Search, document and execute authenticated API calls across all your apps (Gmail, Slack, Stripe, Notion, GitHub, and more) through 4 universal tools whose…

CommunityOnlineNo sign-inGlobalFreeRead-only

What it can do

  • Execute One Action: Use this to run an API action on a platform the user has connected on One, after `get_one_action_knowledge` documented its inputs. Takes the `actionId` from `search_one_platform_ac
  • Get One Action Knowledge: Use this immediately before executing an action: it fetches the action's knowledge document — required parameters, validation rules, and platform-specific caveats — enriched
  • List One Integrations: Use this when you need to know which platforms the user has connected on One — and always before searching or executing. Lists the active connections with their `key` (the `conn

What data it sees

Do you need an account

No: the server works without sign-in

Search, document and execute authenticated API calls across all your apps (Gmail, Slack, Stripe, Notion, GitHub, and more) through 4 universal tools whose context footprint stays constant no matter how many connections you add. OAuth sign-in, nothing to install.

How to connect

How to connect One to Claude

The server address to paste into Claude settings:

https://one--withone.run.tools

  1. Open Claude (claude.ai or the desktop app).
  2. Go to Settings → Connectors.
  3. Click Add custom connector.
  4. Paste the server address copied below into Remote MCP server URL and click Add.
  5. In a chat, click + → Connectors and switch the new connector on.

Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.

Authorization

After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.

How to connect One to ChatGPT

The server address to paste into ChatGPT settings:

https://one--withone.run.tools

  1. Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
  2. Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
  3. Open Settings → Connectors and click Create.
  4. Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
  5. Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
  6. In a new chat open + → Apps/Connectors and enable the connector.

OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.

Authorization

On first use ChatGPT opens the service's sign-in window. Sign in and approve access.

How to connect One to Cursor

The server address to paste into Cursor settings:

https://one--withone.run.tools

Fastest: click Open in Cursor below and confirm the prompt.

Manually:

  1. In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
  2. Paste the JSON copied below into ~/.cursor/mcp.json (per project: .cursor/mcp.json in the repo root).
  3. Save the file. The server appears in the MCP list; authorize it there if asked.

Authorization

If the service needs sign-in, an authorize button appears next to the server in the MCP list.

Server tool list (4)

Raw names from tools/list. Only developers need these.

execute_one_actionUse this to run an API action on a platform the user has connected on One, after `get_one_action_knowledge` documented its inputs. Takes the `actionId` from `search_one_platform_actions` (or the connection's `access` list) and the `connectionKey` from `list_one_integrations`. This can create, modify, delete, or send data on the external platform — confirm irreversible operations with the user before calling. Do not use it to probe connectivity or retry a failed write blindly. Requires the `user:connections:write` OAuth scope; a knowledge-only or access-rule grant can still refuse the call.
get_one_action_knowledgeUse this immediately before executing an action: it fetches the action's knowledge document — required parameters, validation rules, and platform-specific caveats — enriched with guidance on how to call it. Never call `execute_one_action` without reading this first. Refused when the action is outside the caller's grant. Requires the `user:connections:read` OAuth scope.
list_one_integrationsUse this when you need to know which platforms the user has connected on One — and always before searching or executing. Lists the active connections with their `key` (the `connectionKey` for execution) and the `access` each grant confers: `full`, a set of allowed HTTP `methods`, or a specific list of `actions` (each with `actionId`, `title`, `method`). When a connection is action-scoped, its `actions` are exactly what may run, so you need not search. Do not guess connection keys — only use values returned here. Requires the `user:connections:read` OAuth scope.
search_one_platform_actionsUse this when you need to find an API action on a connected platform (e.g. "send an email" on gmail). Searches the platform's action catalog, scoped to the caller's grant: results are limited to actions the grant permits on that platform's connections. Returns up to 5 matching actions with their `actionId`, title, HTTP method, and path. Do not use this for action-scoped connections — their `access` list from `list_one_integrations` already names the permitted actions. Requires the `user:connections:read` OAuth scope.