one-by.one MCP Server

by one-by Your server? Claim it

answering

one-by.one is answering right now. Last checked 15 min ago.

Your AI plans your day as action cards; your iPhone shows one card at a time.

Uptime history 19 hours of history

19 hours agonow

100.0%

Uptime 24h

69 of 69 checks

—

Tools

hidden behind auth

764 ms

Response time

average over 24h

OAuth sign-in

Access

streamable-http

Nothing serious here today

Today is the operative word: we check one-by.one every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 15 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add planner --transport http https://mcp.one-by.one/mcp

Settings → Connectors → Add custom connector, then paste this address

https://mcp.one-by.one/mcp

~/.codex/config.toml

[mcp_servers.planner]
url = "https://mcp.one-by.one/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "planner": {
      "url": "https://mcp.one-by.one/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "planner": {
      "type": "http",
      "url": "https://mcp.one-by.one/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.one-by.one/mcp	streamable-http	sign-in	958 ms	15 min ago

Alternatives to one-by.one

same job, measured the same way

Postcue

by getpostcue

Plan social posts that Postcue cues on your iPhone at the right time. It never posts for you.

answering

Focus

by bekkevard

Blocks distractions on your Mac, PC, Chrome and iPhone to match what you told your agent.

answering

Call Me

by serdaroztetik

Your AI rings your iPhone, speaks its question, and gets your spoken answer back as text.

9 tools answering

Call Me

by callmemcp

Your AI rings your iPhone, speaks its question, and gets your spoken answer back as text.

9 tools answering

Kitchen Timer

by tnyforge

Plan a meal and run kitchen timers that ring on your phone. No sign-in.

9 tools answering

Parameter

by parameterfit

Your AI writes training plans that arrive as structured workouts on iPhone and Apple Watch.

answering

opolyx

by opolyx

Play opolyx, a Monopoly-style board game, as your own AI player in the AI Arena or at an AI Table.

answering

AimYear

by yahhi

Accountability partner in your agent: one yearly aim, one main step a day, a timer your agent runs.

59 tools answering

one-by.one — questions

Answers built from our own checks of this server.

Why is there no tool list for one-by.one?

The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.

Is one-by.one working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 69 of 69 checks got a reply (100.0%), average response time 764 ms. The bar chart above shows every period we have measured.

How do I connect one-by.one?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.

How do you sign in to one-by.one?

No API key is involved. one-by.one answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.

How fast is one-by.one?

It answers our handshake in 764 ms on average, which is faster than 11% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.