Corpole keeps each project's objectives, requirements and constraints in one governed place and hands the binding ones to Claude and other coding agents through MCP, before they write a line of code.
A guided setup walks you from project brief to objectives, stakeholder needs, requirements and constraints — typed by hand, imported from a document or suggested by AI. Every record has an explicit state: Draft, Approved, Authority or Retired.
Claude Code, claude.ai, Claude Desktop, Cursor and any MCP client read the project's Authority records through one remote MCP server. Sign in with OAuth, pick a project, done.
A repository kit tells Claude Code that Corpole outranks the Word documents in your repo, and a GitHub check makes every pull request cite existing, non-retired requirements.
Objectives, business, stakeholder, functional, non-functional, technical and project requirements, plus product, business and project constraints.
Only Authority records are binding for agents. Retired ones never drive new work; Draft and Approved are informational.
get_authority_context, search_requirements, get_record, propose_record and get_repo_kit, with read-only and write annotations.
Agents can propose a missing requirement as a Draft. It is not binding until a person approves it.
See which agent read or proposed what, when, through which connection.
Scan every record type side by side for the active project.
Add https://corpole.com/api/mcp as a custom connector in claude.ai or Claude Desktop, or install the Claude Code plugin. At the start of every Claude Code session the project's Authority records are already in context.
# example > /corpole:context payments Authority FR-3A9C1E Customer pays by card in one step NFR-81D2F0 Checkout completes in < 2 s (p95) PC-0B77A1 No card data stored by us Approved (not binding yet) FR-C19E44 Save card for next order
Connections are scoped to one project and read-only unless someone grants the propose permission.
PKCE, single-use codes, rotating refresh tokens and one-click disconnect. No passwords or tokens pasted into chats.
Agents never change a binding requirement. Proposals land as Drafts for human review, and every agent access is logged.