Sign InGet Started

MCP Server

Give AI coding tools direct access to your Briefs, Tasks, and project context through the Model Context Protocol — no plugins, no API keys, just a URL.

Overview

The Hamster MCP Server lets AI coding assistants — Claude Code, Cursor, Windsurf, Codex, and others that support the Model Context Protocol — read and manage your Hamster project directly. Instead of pasting Task descriptions into your AI tool, you connect it to Hamster once and the tool can browse your Briefs, check Task details, create subtasks, and update status on its own.

The server exposes 20 tools covering accounts, Briefs, Tasks, subtasks, documents, and plans. All access goes through your authenticated session and respects the same permissions you have in the browser. There are no admin keys involved — every call runs as you, scoped to your team's data.

Connecting is a single URL. Your AI tool follows a standard OAuth sign-in the first time you use it; subsequent calls are automatic.

What's in this section

How Authentication Works

Hamster's MCP Server uses OAuth 2.1 — the same standard your IDE already speaks. The first time your AI tool calls a Hamster tool:

  1. The tool sees that it needs to authenticate and looks up Hamster's OAuth configuration via a Discovery endpoint at /.well-known/oauth-protected-resource. This is a public, machine-readable record that tells the tool where to send you for sign-in.
  2. The tool opens your browser to Hamster's consent page.
  3. You sign in (or confirm if you are already signed in) and approve the connection.
  4. The browser hands a session token back to your AI tool.
  5. Every subsequent call runs as you, with your team-account permissions enforced server-side.

Most AI tools handle this flow automatically — you just see the browser pop open the first time. If your tool does not support automatic OAuth Discovery, you can still paste a Bearer token manually.

The MCP Server never holds an admin key or service-role credential. Every tool call carries your token, which means a Reviewer cannot accidentally edit a Brief from inside their AI assistant just because the assistant tried to.

Related