Skip to content
Specor

Introduction

Specor is where your product lives — structured, versioned, and kept consistent by AI.

Most teams scatter product knowledge across Jira tickets, Notion docs, Confluence pages, and Slack threads. Those sources diverge, go stale, and contradict each other. Specor replaces that mess with a single authoritative model: a graph of everything your product is and does, with full version history and AI that continuously checks for gaps and conflicts.

Quick Start

Create an account, build your first domain, and make your first commit. Start here →

Node Types

Learn what Domains, Capabilities, Features, Rules, Metrics, and Flows are. Read guide →

MCP Integration

Connect Claude Desktop or Cursor to your product graph. Set up MCP →

Key ideas

  • One model, one truth. Every domain, feature, rule, and metric lives in the same place. Changes are versioned — nothing gets silently overwritten.
  • Branch-based. Work on changes in isolation, just like Git branches. Merge back when ready, with conflict detection if two branches touched the same thing.
  • AI-aware. Agents run after every change and flag missing coverage, naming issues, contradicting rules, and broken flows — before they become problems.
  • Readable by your tools. Connect Claude Desktop, Cursor, or any MCP-compatible AI assistant so your AI tools work from the same product model your team does.