MCP server that exposes stakeholder personas for iterative product feedback
If you already use Stakeholder MCP, the stakeholder mcp mcp server is the piece that lets your assistant work with it directly. MCP server that exposes stakeholder personas for iterative product feedback.
An MCP (Model Context Protocol) server that exposes stakeholder personas as tools for iterative product feedback. Each stakeholder represents a distinct role with a unique personality, expertise, and concerns.
Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
list_stakeholders — List all available personas with optional filteringget_stakeholder — Get detailed info about a specific stakeholderconsult_stakeholder — Query a stakeholder for feedbackconsult_group — Query multiple stakeholders (parallel or sequential)create_stakeholder — Create a new runtime stakeholderupdate_stakeholder — Update an existing stakeholderdelete_stakeholder — Delete a runtime stakeholderCursor — Add the server to your MCP config. User-level: Cursor Settings → MCP → Edit config (or ~/.cursor/mcp.json). Project-level: .cursor/mcp.json inConfiguration is passed through the environment: OPENROUTER_API_KEY, STAKEHOLDER_MCP_CONFIG_PATH, STAKEHOLDER_MCP_DB_PATH, STAKEHOLDER_MCP_RUNTIME_STORE_PATH, STAKEHOLDER_MCP_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Plenty of AI and media services servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Stakeholder MCP's toolset — list_stakeholders, get_stakeholder, consult_stakeholder and 5 more — is a fair guide to whether it matches your workflow. It is maintained by okkimus; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| list_stakeholders | List all available personas with optional filtering |
| get_stakeholder | Get detailed info about a specific stakeholder |
| consult_stakeholder | Query a stakeholder for feedback |
| consult_group | Query multiple stakeholders (parallel or sequential) |
| create_stakeholder | Create a new runtime stakeholder |
| update_stakeholder | Update an existing stakeholder |
| delete_stakeholder | Delete a runtime stakeholder |
| Cursor | Add the server to your MCP config. User-level: **Cursor Settings → MCP → Edit config** (or ~/.cursor/mcp.json). Project-level: .cursor/mcp.json in the repo root. |
{
"mcpServers": {
"stakeholder-mcp": {
"command": "bun",
"args": ["run", "/path/to/stakeholder-mcp/src/index.ts"],
"env": {
"OPENROUTER_API_KEY": "your-key-here",
"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"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| OPENROUTER_API_KEY | Credential the server authenticates with. | Yes |
| STAKEHOLDER_MCP_CONFIG_PATH | Filesystem location the server is allowed to use. | Optional |
| STAKEHOLDER_MCP_DB_PATH | Filesystem location the server is allowed to use. | Optional |
| STAKEHOLDER_MCP_RUNTIME_STORE_PATH | Filesystem location the server is allowed to use. | Optional |
| STAKEHOLDER_MCP_API_KEY | Credential the server authenticates with. | Yes |
Build a programmable telecommunications stack for connecting telephony services with the Internet via a cloud-based utility.
Search built for AI, not humans — semantic web search that returns model-ready content, plus code context.
Answers, not links — delegate questions to Perplexity's search-grounded models and get cited responses back.
Give your assistant a voice — text-to-speech, voice cloning and audio tools from the ElevenLabs API.
Give your assistant a real code sandbox — isolated cloud VMs for actually running the code it writes.
The ML hub in your context window — search models, datasets, papers and run Spaces from the official server.