MCP: governed context outside the repo

Most of what an engineer needs to do a task well lives outside the repo.

Think of the Jira ticket, the Confluence runbook, the Datadog dashboard showing the error spike, the internal API docs. MCPModel Context Protocol. A standard that lets an AI agent pull in context from outside the repo, like Jira tickets or internal docs. Press Enter for the full definition. (Model Context Protocol) is the standard bridge that lets the agent reach that context and the artifact graph is what it exposes through that bridge.

MCPModel Context Protocol. A standard that lets an AI agent pull in context from outside the repo, like Jira tickets or internal docs. Press Enter for the full definition. is an open protocol. An MCP server wraps a system (Jira, Confluence, GitHub, an observability platform, an internal docs service) and exposes its data and actions as tools the agent can call. Instead of you copy-pasting a ticket into the chat, the agent queries the Jira MCP server directly, reads the acceptance criteria and links the PR back. The repo stops being an island.