CoreStory Playbook: Using the CoreStory MCP Server with Devin

Upgrade Devin's Single-Session Capacity with CoreStory Code Intelligence

CoreStory customers can now wire our code intelligence directly into Cognition’s Devin via MCP to boost accuracy, finish longer tasks, and generate stronger tests—without reinventing your workflow.

What this playbook delivers

• Step-by-step setup to connect Devin to CoreStory through the MCP Marketplace (with copy-paste config).
• Clear benefits you can expect: more accurate code, successful longer (>5 ACU) runs, ticket-level autonomy, spec-driven development, and specification-derived test coverage.
• A ready-to-use prompting pattern that tells Devin to verify the right project, consult CoreStory specs first, cross-check spec vs code, and work test-first.

Why it matters

Agents do their best work when they see the “source of truth.” CoreStory extracts the real business rules, flows, contracts, and patterns from your repo; Devin consumes that context through MCP and uses it to write code, author tests, and resolve tickets with fewer surprises. The playbook packages this into a repeatable path you can adopt in one sprint.

What’s inside

• Quick start: MCP connection, environment variables, and a pre-flight checklist Devin can run before touching code.
• Tooling map: 16 CoreStory MCP tools (projects, conversations, document generation) and when to use each.
• Best-practice prompts: spec/code gap analysis, test-first development, parity testing for migrations, and contract validation.
• Workflow templates: start prompt for Devin, usage log, discrepancy report, security checklist, and cost-control guidance (retrieve vs generate).
• Troubleshooting: connection issues, flaky tests, timeouts, and ingestion readiness—each with diagnostic prompts.

Example outcomes

• Migration & parity: write tests from CoreStory specs, implement against them, and verify behavioral parity across old and new services.
• Gap analysis: produce a file:line discrepancy report, prioritize fixes, and enforce spec compliance with new tests.
• Test hardening: derive positive, negative, idempotency, and RFC-7807 error-contract cases from specs—fast.

Fast start (copy/paste)

1. Add the CoreStory MCP server in Devin’s Marketplace and set CORESTORY_API_KEY / CORESTORY_API_URL.
2. Run the pre-flight checklist (list projects → confirm project → check ingestion → read corestory://guidance).
3. Use the included “Devin Start Prompt” to spin up a conversation, extract requirements from CoreStory, validate spec vs code, and proceed test-first.

Who should read this

Engineering managers, Dev leads, platform/QA owners, and anyone piloting agentic development who needs reliable, spec-driven automation—not one-off prompt magic.

Get Started Today

Read the playbook and connect Devin to your CoreStory project today. Then run your first spec-driven task with the included start prompt and usage log template.