Use with Cursor & Claude

The prompt CTX builds for a ticket is assembled from the same verified quotes as the Jira description, not rewritten by a model — what your assistant reads is what the room said. MCP is how it gets there without anyone copy-pasting it.

Create an API key

Settings → API keys → Create key. The exact command for Claude Code, and the JSON to drop into Cursor's config, are both shown right there with your key already filled in — copy them once.

Claude Code

claude mcp add --transport http ctx https://<your-ctx-backend>/v1/mcp \
  --header "Authorization: Bearer ctx_..."

Cursor

Add to .cursor/mcp.json (or your global Cursor MCP config):

{
  "mcpServers": {
    "ctx": {
      "url": "https://<your-ctx-backend>/v1/mcp",
      "headers": { "Authorization": "Bearer ctx_..." }
    }
  }
}

What your assistant can ask for

• ctx_get_ticket_context — everything behind a Jira key: the prompt, the quotes, acceptance criteria, the epic, and sibling tickets from the same meeting.
• ctx_search_context — search verified decisions, requirements, constraints and open questions across meetings, each result with the quote it rests on.
• ctx_get_bundle — a whole meeting's context as markdown, cited line by line.