one-by.one × MCP
ChatGPT, Claude, a terminal or an editor. Any MCP agent that supports remote HTTP and OAuth can connect to one-by.one. Your AI plans; your iPhone shows one card at a time.
The fastest way to connect. Your agent adds the server, starts the sign-in and waits while you approve.
Add the one-by.one MCP server to yourself and connect it.
- Server URL: https://mcp.one-by.one/mcp
- Transport: remote streamable HTTP. Name the server "onebyone".
- Auth: OAuth sign-in with dynamic client registration. There is no API key or token, so do not ask me for one.
Steps:
1. Add the server to your MCP configuration and keep my existing servers. If you cannot change your own configuration, give me the exact command or setting for this client.
2. Start the OAuth sign-in. If you cannot open a browser, show me the sign-in link.
3. I will sign in to my one-by.one account and approve the permissions: context:read, activity:read and activity:write. The approval screen may label you "Unverified app"; that is normal for unverified clients.
4. When I am back, confirm that the onebyone tools are listed. Do not create or change any plans until I ask. If the connection is refused because the limit of 3 AI connections is reached, tell me.
Instructions for each client: https://one-by.one/connect/index.mdAn agent that cannot change its own settings will tell you what to enter. You can also follow the steps for your tool below, or give your agent the Markdown version of this page.
https://mcp.one-by.one/mcpcontext:read, activity:read, activity:writeNo API key or separate developer registration is needed. one-by.one supports dynamic client registration for web connectors and local clients, including local loopback redirects.
An app we have not verified appears as Unverified app on the approval screen. Check that it is the tool you meant to connect.
context:read — read the context you share for planning.activity:read — read your plans and recorded activity.activity:write — create or update plans and save activity.Review what your AI receives in our Privacy Policy.
Keep your existing settings and merge only the onebyone entry. These examples use OAuth discovery; no pasted tokens or client secrets. Menus can vary by version.
Turn on Developer mode if your account allows it. The current setup guide uses Settings → Security and login → Developer mode.
Open Plugins, select +, name the connection one-by.one and enter the public server URL. Older interfaces may call this Apps or Connectors.
https://mcp.one-by.one/mcpCreate the connection and finish the one-by.one OAuth sign-in.
Select it from the tools menu in a new chat. Availability depends on your plan and workspace policy.
Open Customize → Connectors and add a custom web connector.
Name it one-by.one and paste the server URL.
https://mcp.one-by.one/mcpChoose sign-in authentication and automatic client registration when that option is shown.
Complete the OAuth flow, then enable the connector in your conversation.
Use the same remote custom connector in Claude Desktop. Team and Enterprise workspaces may need an owner to add it first.
Run this in your terminal.
claude mcp add --transport http onebyone https://mcp.one-by.one/mcpIn a Claude Code session, enter /mcp, select onebyone and authenticate in the browser.
/mcpAdd the server and start OAuth login from your terminal.
codex mcp add onebyone --url https://mcp.one-by.one/mcp
codex mcp login onebyonePrefer a config file? Merge this TOML entry into ~/.codex/config.toml and run codex mcp login onebyone.
[mcp_servers.onebyone]
url = "https://mcp.one-by.one/mcp"Use /mcp in Codex to inspect the connection.
Merge this entry into .cursor/mcp.json in your project, or ~/.cursor/mcp.json for all projects.
{
"mcpServers": {
"onebyone": {
"url": "https://mcp.one-by.one/mcp"
}
}
}Save and restart Cursor, then complete the OAuth prompt and use the tools in Agent.
Merge this into .vscode/mcp.json. You can also open user-level settings with MCP: Open User Configuration.
{
"servers": {
"onebyone": {
"type": "http",
"url": "https://mcp.one-by.one/mcp"
}
}
}Use the editor’s Start action for onebyone and complete the browser sign-in.
Enable its tools in Copilot Agent.
Merge this into ~/.gemini/settings.json (or your project’s .gemini/settings.json). OAuth is discovered automatically.
{
"mcpServers": {
"onebyone": {
"httpUrl": "https://mcp.one-by.one/mcp"
}
}
}In a Gemini CLI session, run the authentication command.
/mcp auth onebyoneIn Cascade, open the … Actions menu → MCPs → Open MCP config file.
Merge this entry into mcp_config.json.
{
"mcpServers": {
"onebyone": {
"serverUrl": "https://mcp.one-by.one/mcp"
}
}
}Save and complete OAuth sign-in when prompted.
The official Windsurf guide now redirects to Devin Desktop and applies to the legacy Cascade agent. Follow the configuration-file control in your installed version; newer Devin Local tabs use a different setup.
You can have up to three AI connections per account. To make room, open Settings › AI apps in the iPhone app and tap Disconnect next to a connection. You can also use Disconnect on its one-by.one authorization page, or remove its configuration in the AI tool.
Disconnecting stops future tool access. It does not delete your one-by.one records or information the AI already received. AI connections require your account’s applicable subscription entitlement.
Use the same server URL with remote Streamable HTTP and OAuth. Your client must support OAuth discovery and dynamic registration. Local tools can return to a loopback redirect after sign-in. Check your tool’s official documentation for its configuration format. Agents can read this page as Markdown.