Summary

Read-side access to the backlog, from inside the editor.

The three calls map onto the questions you ask before starting a ticket, which is a better cut than exposing the whole API. It reads rather than writes, so it adds context to a coding session without letting an assistant change the board.

What it is

A bridge between an MCP client and the Agile Luminary project management system. It reads three things an engineer actually needs mid-task: what is assigned to you now, what similar work was completed before, and which specification documents relate to the thing you are building.

What you get

`getCurrentWork` — fetch the tasks and user stories currently assigned to you, no arguments needed
`getPastWork` — retrieve completed user stories matching a `searchString`, so earlier solutions to a similar problem come back as context
`getRelatedDocuments` — search project documentation and specifications by `searchString` and return the relevant pages

Requirements

An Agile Luminary account and its API key, supplied as `LUMINARY_API_KEY` and sent in the Authorization header on every request. Node.js v16 or higher. The documented client entry runs `node server.js` over stdio with the key in the `env` block; `npm install @modelcontextprotocol/sdk zod` covers the dependencies.

Setup effort

Build from source — clone the repository and build it, then point your client at the binary