Connect your AI agent to How About Today.

Start by telling your agent

If you already chat with an MCP-capable assistant, just ask it to connect and point it at this page. It reads the guide, opens a pairing request for your email, and asks you to approve.

Connection details

Point your agent at the MCP endpoint and the agent-readable guide. The guide is plain Markdown, meant for machines as much as people.

https://app.howabout.today/mcp

https://howabout.today/SKILL.md

Configuration snippets

If your runtime supports remote MCP servers, add How About Today as a streamable HTTP server. Reload the runtime afterward so it can discover the tools.

{
  "mcpServers": {
    "how_about_today": {
      "url": "https://app.howabout.today/mcp"
    }
  }
}

mcp_servers:
  how_about_today:
    url: "https://app.howabout.today/mcp"

Connecting Claude Desktop

Desktop apps like Claude Desktop don't take a chat prompt — they add How About Today as a custom connector and sign in over OAuth. A quick one-time setup; after that it behaves like any other agent here.

1. In Claude, open Customize → Connectors → + Add custom connector.
2. Give it a name (How About Today) and paste https://app.howabout.today/mcp into the Remote MCP server URL field, then click Add.
3. Click Connect. Claude opens How About Today in your browser — the standard OAuth handshake.
4. Sign in the usual passwordless way (your email + the one-time code we send), then choose the scope — read-only or read & write — and approve.
5. Back in Claude, grant permission for the tools whenever it asks — exactly like any other connector.

Other connector-style desktop clients follow the same shape: add the endpoint URL above, click Connect, sign in to How About Today in the browser, and approve a scope. Claude receives its own scoped token and never sees your password — disconnect anytime from Connectors, or open Connected agents in your account and hit Revoke.

Connecting Codex

Codex adds How About Today as a remote MCP server — the same endpoint, reached through Codex's own server settings. It signs in over OAuth; no token or key to paste.

1. In Codex, open Settings → MCP Servers → + Add server, then choose Streamable HTTP.
2. Set Name to How About Today and URL to https://app.howabout.today/mcp. Leave the bearer-token and header fields empty, then Save.
3. Click Authenticate — or, in the Codex CLI, run codex mcp login. Codex opens How About Today in your browser for the OAuth sign-in.
4. Sign in passwordlessly and approve the scope you want — read-only or read & write — and Codex is connected.

No bearer token, header, or API key is needed — Codex completes a standard OAuth sign-in, then stores its own scoped token. Revoke it with codex mcp logout or from your account anytime.

What you're approving

You choose the scope when you approve, and you can revoke it anytime from your account — the token stops working immediately.

No passwords. No API keys.

How About Today uses passwordless sign-in throughout: command-line agents go through user-approved pairing, and desktop apps like Claude Desktop and Codex sign in over OAuth. Every path is designed so an agent never needs a secret from you.

• Your agent starts a pairing request for your registered email and the scope it needs, then shows you the approval link.
• You approve once. It should never ask for your password, one-time login code, API key, bearer token, or session token.
• The agent keeps its token in its own secure storage. You can revoke access later, anytime.

How a good agent behaves here

How About Today is intentionally calm. A well-behaved agent keeps that spirit — it doesn't bolt on structure the app deliberately avoids.

• No projects, tags, priorities, overdue warnings, alarms, streaks, or productivity-pressure language. Tasks are just tasks.
• "Open today," not "overdue." "Set aside," not "deprioritize." "Quietly moved forward," not "late."
• Make the smallest change that satisfies your request, identify the exact task before editing, and read it back to confirm.
• Verify a fresh connection with a harmless read — today's open tasks — not a test task.

If a connection won't take

Most snags come down to one small thing. In order of likelihood:

• The pairing request is still pending approval — approve the link your agent showed you.
• The link expired — ask the agent to start a fresh request.
• The email doesn't match the one you registered with — confirm it.
• The runtime needs a restart after adding the MCP server, or you need read & write for the action.