Labsco
MCP SERVER

Stakeholder MCP

by okkimus

Run a requirement past a tech lead, a security engineer and two end users before you build it — each answering in its own voice.

Reasoning Scaffolds & Agent Workflow Engines
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.