# Devin + CoreStory

Connect Devin to CoreStory so autonomous work begins with governed project context rather than model memory alone.

## Before you connect

- Use the MCP endpoint and authentication method shown in your CoreStory account or onboarding material. Do not copy tokens into source files, prompts, or chat.

- Confirm the target project is ingested and that your identity is authorized to read it.

- Treat tool discovery as authoritative: available tool names and parameters may change as the service evolves.

## Procedure

1. Add CoreStory as a remote HTTP MCP integration using Devin's current integration settings.

2. Use the CoreStory endpoint and secret store available to your account; do not place a bearer token in repository files.

3. Inspect the live tools, select the target project, and retrieve the relevant PRD, technical spec, or semantic evidence before planning.

4. Make evidence use part of the task's acceptance criteria.

## Validation

- The MCP client reports a connected `corestory` server.

- `list_projects` returns only projects your identity should access.

- A project-document or semantic query returns evidence from the expected project.

- The agent cites retrieved context in its plan or answer and distinguishes retrieved facts from inference.

## Failure handling

- For authentication errors, create or rotate credentials through the product workflow; never print a token to diagnose it.

- For missing data, verify project identity and ingestion state before changing the prompt.

- If the advertised tools differ from this guide, use the server's live tool schema and report the documentation drift.