MCP (Model Context Protocol)
An open standard from Anthropic for connecting AI assistants to external data and tools. Specsight ships a read-only MCP server so assistants can query a live spec.
MCP — Model Context Protocol — is the open standard Anthropic published in late 2024 for letting AI assistants talk to external systems. An MCP server exposes a small set of tools and resources; an MCP-aware client (Claude Code, Cursor, Windsurf, Claude Desktop, and others) can then call those tools as part of a conversation. The wire format is JSON-RPC over HTTP or stdio.
Before MCP, every assistant integration was bespoke — a Cursor extension here, a Claude Desktop plugin there, none of them portable. MCP turned that into one protocol. Build an MCP server once and every MCP-aware assistant can use it.
Specsight ships a read-only MCP server. Once you generate an API key in Organisation Settings and add the URL to your assistant's config, the assistant can pull live spec context — features, scenarios, changelogs, connections — into whatever you are working on. Useful for drafting briefs and answering ad-hoc product questions without leaving the editor.
Related terms
- SPEC
Scenario
A single plain-language description of how a product behaves in a specific situation. The atomic unit of a Specsight spec.
- SPEC
Changelog
A chronological record of what changed in a product, feature, or scenario over time. In Specsight, one running changelog covers the whole product, filterable down to a single Feature.
- CONCEPT
Product Observability
Continuous insight into how a product behaves and changes, release by release — the way infrastructure observability (Datadog, Sentry) watches your systems, pointed at the product itself.