Grafizum Command Center

Your projects, tasks, calendar and project memory as MCP tools — so an agent can read the board and update it, with a receipt for every write.

Live endpoint: https://mcp.grafizum.com/mcp

There is no API key to paste. The client registers itself, opens a one-card approval page on the dashboard, and works inside the access you grant: chosen projects, read-only or read-and-write, revocable at any time.

Documentation: https://grafizum.com/docs

How to install in Cursor

Add the server to your MCP configuration (mcp.json):

{
  "mcpServers": {
    "grafizum": {
      "url": "https://mcp.grafizum.com/mcp"
    }
  }
}

Then restart Cursor (or reload the MCP servers from its settings) and finish the sign-in in the browser window that opens. Approve the connection, pick the projects it may reach, and the Grafizum tools appear in the client.

How to install in Cline

Cline keeps MCP servers in cline_mcp_settings.json. Open it from the Cline panel — MCP Servers icon → Configure → Configure MCP Servers — and merge this entry into the existing mcpServers object:

{
  "mcpServers": {
    "grafizum": {
      "type": "streamableHttp",
      "url": "https://mcp.grafizum.com/mcp",
      "disabled": false,
      "autoApprove": []
    }
  }
}

The "type": "streamableHttp" line is not optional: without it Cline falls back to the legacy SSE transport and the connection fails. Leave headers out — there is no token to paste.

From the CLI instead:

cline mcp add grafizum https://mcp.grafizum.com/mcp --transport http --yes
cline mcp   # then choose "Authorize OAuth"

After saving, the entry shows that authentication is required: click Authenticate, sign in to Grafizum in the browser, approve the connection and pick the projects it may reach. Cline registers itself with the server, so there is no client ID to enter.

If you are having an agent set this up for you, llms-install.md writes the same steps as instructions for the agent.

How to install in other MCP clients

Any client that speaks Streamable HTTP with OAuth 2.1 works the same way: give it this URL as the server URL.

https://mcp.grafizum.com/mcp

Nothing else is required — no token, no headers, no proxy. The client runs the OAuth flow itself.

Claude Code — claude mcp add --transport http grafizum https://mcp.grafizum.com/mcp
VS Code / Copilot — the same two fields under a servers object in .vscode/mcp.json
Codex, Gemini CLI, Aider or a plain terminal agent — use the URL as the server address

What it can do

30 tools across reading and writing:

Read — projects, project status and progress, tasks, the activity log, calendar entries, project knowledge and memory, and a change check since the last look.
Write — create, update and move tasks; create and update projects; report project status; write project knowledge and memory; record events; add calendar entries.

Every write answers with a receipt naming what changed and where to see it, and lands in the workspace's activity log. Consequential changes ask for a yes first — in the client's own prompt where it can draw one, otherwise in the conversation.

Permissions

Connections are scoped per app, not per account: the projects it may reach, whether it is read-only or read-and-write, which of thirteen fine-grained rules apply, and an optional expiry (24 hours, 7 days, 30 days, or until revoked). Nothing outside the workspace is reachable: no filesystem, no credentials, no network access on your behalf.

Revoke or edit a connection any time at https://dashboard.grafizum.com/mcp

License

MIT — see LICENSE.

Grafizum Command Center