getRelatedDocumentsLABSCO 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 neededgetPastWork— retrieve completed user stories matching asearchString, so earlier solutions to a similar problem come back as contextgetRelatedDocuments— search project documentation and specifications bysearchStringand 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 — git clone https://github.com/AgileLuminary/mcp-agile-luminary.git
USE CASES
01
Starting the day without opening the tracker
Ask what is assigned to you right now and get the tasks and stories back in the editor you are already in.
02
Finding how this was solved last time
Search completed stories for the same feature area and read what the earlier implementation actually did.
03
Getting the spec into context before coding
Search project documentation for the subject you are working on so the assistant writes against the specification rather than a guess.
3 tools
Listed in project docs. Your client may show a different list.
getCurrentWorkgetPastWorkBEFORE YOU INSTALL
What to know first
Tools you get
3 tools named in the project's documentation.
Requires
- node on PATH
- Node.js
- LUMINARY_API_KEY in your environment
Where it runs
Both documented clients run the server on your machine.
INSTALLATION
Connect your client
You clone this one yourself.
Server setup
TERMINAL
git clone https://github.com/AgileLuminary/mcp-agile-luminary.git
cd mcp-agile-luminary
npm install @modelcontextprotocol/sdk zodMCP Clients
Cursor, Claude Desktop
JSON
{
"mcpServers": {
"agile-luminary": {
"command": "node",
"args": [
"<YOUR_PATH_TO_SERVER>"
],
"env": {
"LUMINARY_API_KEY": "<YOUR_LUMINARY_API_KEY>"
}
}
}
}<YOUR_PATH_TO_SERVER> is the full path to server.js in your mcp-agile-luminary clone, and <YOUR_LUMINARY_API_KEY> is your Agile Luminary API key.
