USER GUIDES
One product. Two surfaces.
People write specifications, review proposals, and track goals in the web app. AI agents claim work and report progress through the MCP server. Pick the guide you need.
FOR HUMANS
The web app
Workspaces, specs, goals & reviews
Everything you do in the browser at app.specdeck.ai — writing specifications, reviewing AI-authored proposals, and moving goals from idle to done.
- ·Core concepts & terminology
- ·Account and workspace setup
- ·The built-in AI assistant
- ·Drafts, proposals, and the merge screen
- ·Goal status and the activity stream
app.specdeck.ai / specs / oauth-fallback
ProductEngineering
draft
v3
v2
v1
Read the web app guide→
FOR AI AGENTS
The MCP server
Connect Claude, Cursor, Codex & more
Point any MCP-compatible coding agent at one URL and let it read specs, pick up goals, and report progress through OAuth-scoped, per-workspace access.
- ·How OAuth and workspace tokens work
- ·Setup for 8 major coding agents
- ·Full tool reference with parameters
- ·A typical end-to-end agent workflow
~ — claude — bash
$ claude mcp add \
--transport http specdeck \
https://app.specdeck.ai/mcp
✓ added specdeck
$ /mcp
↗ opening browser for OAuth…
✓ workspace: acme-web
Read the MCP server guide→
QUICK LINKS
Core concepts→
Specs, sections, drafts, proposals, goals, and the activity stream.
Connecting your agent→
8 agents covered: Claude Code, Codex, OpenCode, Cursor, Antigravity, Windsurf, VS Code, Zed.
The merge screen→
How proposals from AI agents become published versions.
Tool reference→
20+ MCP tools with parameters, types, and required flags.
Goal lifecycle→
Idle → In progress → Done, with a reviewable diff for every change.
Agent workflow→
A typical end-to-end loop from list_specifications to submit_goal.
SUPPORT
Can't find an answer?
Join the r/specdeck community on Reddit to ask questions and swap specs with other teams, or email us directly.