list_stakeholdersLABSCO SUMMARY
The review you would have got in a room, before the room is available.
Each persona brings a different objection — the security engineer's is not the UX designer's — so a requirement gets pushed on from several sides in one pass, and the group mode runs them together when what you want is the disagreement rather than one opinion.
What it is
A set of stakeholder personas exposed as tools. Seven ship with it — Tech Lead, Product Manager, UX Designer, Security Engineer, DevOps Engineer and two end-user personas — each with its own expertise and concerns, and each consultation goes to a model of your choosing through OpenRouter.
What you get
- Seven pre-configured personas, listed with optional filtering, and the detail behind any one of them
- One stakeholder consulted on a proposal, or several at once — in parallel or in sequence
- New personas created at runtime, updated and deleted
- Any of OpenRouter's models behind the consultation
- Stdio and HTTP/SSE transports
Requirements
Bun, and an OpenRouter API key — every consultation is a model call billed to it. The default token limit is set high so the personas can reason at length, and can be capped in the environment when you want shorter answers.
Setup effort
Follow the published steps — bun install
USE CASES
01
Pressure-testing a feature idea
Put the proposal to several personas at once and read where they disagree, with the security objection and the UX objection arriving together.
02
Getting one specific kind of objection
Ask the security engineer, or the DevOps engineer, when you already know which angle you are weakest on.
03
Refining requirements before writing them up
Consult, revise, consult again — so the spec that reaches the team has already survived the obvious questions.
04
Modelling the users you actually have
Create a persona that matches your real customer and update it as you learn more about them.
05
Keeping the roster honest
Remove personas that no longer represent anyone, so a consultation is not answered by a fiction.
7 tools
Listed in project docs. Your client may show a different list.
get_stakeholderconsult_stakeholderconsult_groupcreate_stakeholderupdate_stakeholderdelete_stakeholderBEFORE YOU INSTALL
What to know first
Tools you get
7 tools named in the project's documentation.
Requires
OPENROUTER_API_KEY in your environment
Where it runs
All 3 documented setups run the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
git clone https://github.com/okkimus/stakeholder-mcp
cd stakeholder-mcp
bun install
cp .env.example .envMCP Clients
Claude Desktop, Cursor
JSON
{
"mcpServers": {
"stakeholder-mcp": {
"command": "bun",
"args": [
"run",
"<YOUR_PATH_TO_STAKEHOLDER_MCP>/src/index.ts"
],
"env": {
"OPENROUTER_API_KEY": "<YOUR_OPENROUTER_API_KEY>"
}
}
}
}Cursor — project level
CURSOR — PROJECT LEVEL · JSON
{
"mcpServers": {
"stakeholder-mcp": {
"command": "bun",
"args": [
"run",
"<YOUR_PATH_TO_STAKEHOLDER_MCP>/src/index.ts"
],
"env": {
"OPENROUTER_API_KEY": "<YOUR_OPENROUTER_API_KEY>",
"STAKEHOLDER_MCP_CONFIG_PATH": ".cursor/stakeholders.yaml",
"STAKEHOLDER_MCP_DB_PATH": ".cursor/data/consultations.db",
"STAKEHOLDER_MCP_RUNTIME_STORE_PATH": ".cursor/data/runtime-stakeholders.json"
}
}
}
}
