MCP server
Let your AI read and edit your plan
Solid Hours has a remote MCP server. Connect the assistant you already use and it can see your day, add and finish tasks, and keep your projects and milestones up to date, while you watch the changes land in the app.
The endpoint
https://app.solidhours.com/api/mcpIt speaks MCP over HTTP and takes a bearer key in the Authorization header. Any MCP client that can send a header can connect.
1. Make a key
- Open Settings → MCP in Solid Hours.
- Name the key after where it will live, for example “Claude Code on my laptop”.
- Choose Read only (expires after 30, 90 or 365 days) orRead & edit (7, 30 or 90 days; edit access is kept shorter on purpose).
- Copy the key. It is shown once; if you lose it, revoke it and make another.
2. Add it to your assistant
Claude Code
claude mcp add --transport http -s user solidhours https://app.solidhours.com/api/mcp --header "Authorization: Bearer <your key>"-s user makes Solid Hours available in every folder, not only the current one.
ChatGPT: Codex CLI
codex mcp add solidhours --url https://app.solidhours.com/api/mcp --bearer-token-env-var SOLIDHOURS_TOKEN
echo 'export SOLIDHOURS_TOKEN=<your key>' >> ~/.zshrcCodex reads the key from an environment variable, so it never sits in a config file.
Gemini CLI
gemini mcp add -t http -s user solidhours https://app.solidhours.com/api/mcp -H "Authorization: Bearer <your key>"Cursor and other MCP clients
Add a remote server with the URL and the header. In Cursor that is mcp.json:
{
"mcpServers": {
"solidhours": {
"url": "https://app.solidhours.com/api/mcp",
"headers": {
"Authorization": "Bearer <your key>"
}
}
}
}Then ask in plain words: “What is on my day?”, “Plan my day”, “Add a task to call the accountant tomorrow”, or “Where am I on the website project?”
What your assistant can do
With a read-only key it can:
- Read “My day”, your ordered list of what to do today.
- List and search tasks by status or project, and read any one task.
- List projects and read one, including its open tasks and a status report: percent done, where you left off, what is next, milestones and hours worked.
With a read & edit key it can also:
- Add, edit and complete tasks (completing can be undone), snooze them to a later day, or mark them blocked with the reason.
- Put tasks on My day, take them off, or reorder the whole day.
- Add and edit projects, set their milestones and dates, put tasks under a milestone, record blockers, log time, and set the project logo.
Safety, plainly
- Each assistant gets its own key, and you can revoke any of them at once from Settings → MCP. You can see when each one was last used.
- Read-only means read-only. A read key has no write tools at all; the server checks the key’s access on every call.
- Keys expire, and edit keys sooner than read keys. Only a hash of each key is stored, never the key itself.
- Nothing is permanently deleted through MCP. A task can be dropped and a project archived; both can be brought back.
- No double writes, no blind overwrites. Every change carries an operation id, so a retry never creates a second copy, and an edit must quote the item’s latest revision, so it cannot silently overwrite a change you made in the meantime.
- Assistants are told to ask first before large changes, such as adding many tasks, reordering your whole day, or dropping things.
What you share with an assistant is then handled by that assistant’s provider under your account with them. See Privacy for the full picture.
Using Claude Code on a codebase?
The desktop app adds a /solidhours command to Claude Code that reads a repo and builds its whole project in Solid Hours through this MCP server.