qoder-mcp

A Model Context Protocol server for Qoder — read and write your projects, todos, issues, versions, notes, milestones, daily logs, and ideas against your Qoder Supabase workspace, from Claude or any MCP-aware client.

Install

Via npx (recommended — always latest)

No install step; your MCP client will fetch it on demand. See the config examples below.

Globally

npm install -g qoder-mcp

Related MCP server: Taskade MCP Server

Configuration

qoder-mcp signs into your Qoder Supabase project with email + password. All four variables are required:

Claude Desktop

Add this to claude_desktop_config.json (on Windows: %APPDATA%\Claude\claude_desktop_config.json; on macOS: ~/Library/Application Support/Claude/claude_desktop_config.json):

{
  "mcpServers": {
    "qoder": {
      "command": "npx",
      "args": ["-y", "qoder-mcp"],
      "env": {
        "QODER_SUPABASE_URL": "https://your-project.supabase.co",
        "QODER_SUPABASE_ANON_KEY": "eyJ...",
        "QODER_EMAIL": "you@example.com",
        "QODER_PASSWORD": "your-password"
      }
    }
  }
}

Restart Claude Desktop. You should see the Qoder tools listed in the tool picker.

Claude Code (CLI)

claude mcp add qoder \
  --env QODER_SUPABASE_URL=https://your-project.supabase.co \
  --env QODER_SUPABASE_ANON_KEY=eyJ... \
  --env QODER_EMAIL=you@example.com \
  --env QODER_PASSWORD=your-password \
  -- npx -y qoder-mcp

Tools

Reads

Writes

Security notes

• All credentials are read from the server's environment block, which the MCP client passes to the child process. Nothing is written to disk by qoder-mcp.

• The server signs in once per process and refreshes its JWT in the background.

• Every read filters by your user id — the server does not expose cross-user queries.

• The connection to Supabase is a direct HTTPS call from this process; nothing is proxied through a third party.

• The anon key is a public identifier (that's what the Electron app ships with). Access control comes from Supabase's row-level security policies on your tables.

Local development

git clone https://github.com/JNoles405/qoder-mcp.git
cd qoder-mcp
npm install
# set the four env vars, then:
node bin/qoder-mcp.js

The server speaks MCP over stdio, so a bare node launch will just sit there waiting on protocol input after signing in — that's success. Ctrl-C to exit.

To wire your local checkout into Claude Desktop for end-to-end testing, point it at the absolute path:

{
  "mcpServers": {
    "qoder": {
      "command": "node",
      "args": ["F:/Qoder/MCP/bin/qoder-mcp.js"],
      "env": { "...": "..." }
    }
  }
}

License

MIT. See LICENSE.