Your IDE reads your specs via MCP
Connect Specsource to Cursor, Claude Code or any MCP-compatible tool. Your agent fetches features, decisions and test cases before writing code.
MCP tools your agents can call
get_project_context
Everything an agent needs in one call: instructions, business context, features, decisions, systems and tests. The starting point for any task.
get_feature_context
Full implementation context for a feature: requirements, linked solution designs, architecture decisions, test cases and project background.
list_features / get_feature
Fetch all features or drill into a specific one with requirements, status and priority. Accepts short refs or full IDs.
list_decisions / get_decision
Query architecture decisions. Understand the context, alternatives considered and consequences of every technical choice.
list_tests / get_test
Retrieve test cases with step-by-step actions and expected results. Know exactly what behaviour needs to be verified.
list_solution_designs / get_solution_design
Read solution design documents with full markdown content. Understand the architecture before writing implementation code.
list_instructions / get_instruction
Coding conventions, architecture rules and project guidelines. Agents follow these automatically when building.
list_business_contexts / get_business_context
Company background, market context, compliance requirements and domain knowledge that informs every decision.
search_entities
Search across all entity types by keyword. Find any spec, decision, feature or test related to what you're building.
create + update tools
Create features, tests, decisions, instructions and business context directly from your IDE. Agents can write specs back to Specsource.
How it works
Install the MCP server
Add @specsource/mcp-server to your IDE configuration. Works with Cursor, Claude Code, Windsurf and any MCP-compatible tool.
Connect to your project
Authenticate with your Specsource API key. The server maps to your organisation and projects automatically.
Agents read your specs
Before writing code, your agent fetches features, decisions and designs. It builds from your actual specifications.
Specs stay in sync
As you update specs in Specsource, agents always get the latest version. No stale documentation, no outdated context.