MCP setup

feega’s MCP server lets an agent read and write your canvases with the same sign-in as the CLI. There are no static API tokens.

• Remote: https://mcp.feega.app/mcp, Streamable HTTP. The host must send Authorization: Bearer <access token>; discovery is at /.well-known/oauth-protected-resource. A missing Bearer is a 401, not a broken server. Health: https://mcp.feega.app/health.
• Local stdio: feega-mcp (cli/mcp/stdio.ts), sharing the session file ~/.config/feega/session.json.

Claude Code

claude mcp add --transport http feega https://mcp.feega.app/mcp

Unverified: the OAuth round in Claude Code against feega’s authorization server was not run for these docs. If it fails, use the local option below.

Local stdio (Cursor, Claude Desktop, any client)

Sign in once with feega login, then add:

{
  "mcpServers": {
    "feega": {
      "command": "bun",
      "args": ["run", "/ABS/PATH/to/feega/cli/mcp/stdio.ts"]
    }
  }
}

Needs Bun and a clone of the repo (or the CLI binary). Then call query on projects to confirm you are signed in.

Cursor with the remote URL

{ "mcpServers": { "feega": { "url": "https://mcp.feega.app/mcp" } } }

Some Cursor builds register a cursor:// OAuth callback that feega’s registration endpoint refuses (it accepts only https or loopback http). Prefer local stdio, update Cursor, or bridge with mcp-remote.

First calls

1. query on projects.
2. describe with {} to see every tool and op; find_tools to search them.
3. load_tools to list the ones you need, or run any through edit {op, input}.

A session lists 10 core tools (query, view, edit, describe, render_video, get_render, list_orgs, find_tools, load_tools, unload_tools; about 900 tokens); the rest load on demand. Claude Code refreshes on tools/list_changed; Cursor does not, so call loaded tools by name.

The whole surface: MCP tools and Edit ops. Never guess an org or project id: read it with query first.