MCP & AI Agents
Let Claude, Cursor, OpenClaw, or Hermes run your Fokus workspace — 44 tools over the Model Context Protocol.
Captain Fokus lives inside Fokus. This section is about the opposite direction: giving the AI agents you already use — Claude, Cursor, OpenClaw, Hermes — the keys to your workspace, so they can create tasks, read your agenda, take notes, and even run the auto-scheduler while you're deep in some other tool.
(If you want the reverse — Fokus's own crew reading from your other apps — that's Connectors.)
Either way you get the same 44 tools — over the Model Context Protocol — across tasks, events, notes, buckets, objectives, tags, reminders, calendars, unified search, day/week agendas, and auto-scheduling. Connect the hosted server with nothing to install, or run the fokus-mcp CLI on your own machine.
Hosted MCP (no install)
Connect Claude.ai, ChatGPT, or Claude Code over HTTP — nothing to download.
Claude, Cursor & MCP clients
The local MCP server: Claude Desktop, Cursor, and anything that speaks MCP over stdio.
OpenClaw
Install the Fokus skill — the agent learns the data model and the workflows, not just the tools.
Hermes Agent
Nous Research's agent, with the Fokus tools loaded natively.
Two ways in
The same CLI serves both routes. Pick one per framework — installing both just duplicates the same capabilities in the agent's context.
- MCP server — run
fokus-mcpwith no subcommand and it serves the 44 tools over stdio, plus two ready-made prompts (daily_planning,weekly_review). Raw, schema-driven tool access. - Skill — the
fokusskill (agentskills.io format) wraps the same CLI and teaches the agent Fokus's data model, conventions, and workflows. Better answers, fewer wrong turns.
| Framework | Recommended route |
|---|---|
| Claude Desktop / Claude Code / Cursor | MCP server |
| OpenClaw | Skill (MCP also works) |
| Hermes Agent | MCP server (skill also works) |
What an agent can actually do
- Read your day. "What's on my plate tomorrow?" — agendas, events, deadlines, rollovers.
- Capture properly. Tasks with priority, energy, due dates, buckets, and objectives; notes in real markdown that render as headings, checklists, and tables in the editor.
- Change things. Update, complete, reschedule, tag, remind.
- Plan. Trigger the auto-scheduler and apply the proposed plan to your calendar.
Authentication, once
On the hosted server, skip this
The hosted MCP uses a one-click browser approval (or a token you mint) instead of a terminal login. The steps below are for the local CLI.
Sign in one time from a terminal; the CLI stores rotating tokens in ~/.config/fokus-mcp/credentials.json (mode 0600) and refreshes them as it works:
fokus-mcp login # email/password
fokus-mcp login --oauth google # or microsoft / apple
fokus-mcp whoami # verify: user, API URL, active workspace
fokus-mcp workspace # choose the default workspaceA human has to log in
Login is interactive by design — never share your password with an agent in chat. If tools report "not logged in", run fokus-mcp login yourself. Credentials expire after about 7 days without use.
Self-hosting
Point the CLI at your own backend with fokus-mcp login --api-url http://your-host:3000, or set FOKUS_API_URL. The credential store is keyed per API URL, so cloud and self-hosted logins coexist.
How is this guide?