Product design with Claude: phases, requirements, user stories, RICE, flows, dashboard, Jira.
Connect Runs on your machine
claude mcp add yeti -e PRODUCT_DESIGN_DB=<PRODUCT_DESIGN_DB> -e JIRA_SITE=<JIRA_SITE> -e JIRA_EMAIL=<JIRA_EMAIL> -e JIRA_API_TOKEN=<JIRA_API_TOKEN> -- npx -y [email protected]
{
"mcpServers": {
"yeti": {
"command": "npx",
"args": [
"-y",
"[email protected]"
],
"env": {
"PRODUCT_DESIGN_DB": "<PRODUCT_DESIGN_DB>",
"JIRA_SITE": "<JIRA_SITE>",
"JIRA_EMAIL": "<JIRA_EMAIL>",
"JIRA_API_TOKEN": "<JIRA_API_TOKEN>"
}
}
}
}
{
"mcpServers": {
"yeti": {
"command": "npx",
"args": [
"-y",
"[email protected]"
],
"env": {
"PRODUCT_DESIGN_DB": "<PRODUCT_DESIGN_DB>",
"JIRA_SITE": "<JIRA_SITE>",
"JIRA_EMAIL": "<JIRA_EMAIL>",
"JIRA_API_TOKEN": "<JIRA_API_TOKEN>"
}
}
}
}
{
"servers": {
"yeti": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"[email protected]"
],
"env": {
"PRODUCT_DESIGN_DB": "<PRODUCT_DESIGN_DB>",
"JIRA_SITE": "<JIRA_SITE>",
"JIRA_EMAIL": "<JIRA_EMAIL>",
"JIRA_API_TOKEN": "<JIRA_API_TOKEN>"
}
}
}
}
Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools
This server runs locally, so its tools are listed by your MCP client once it starts.
Environment variables
| Name | Description |
|---|---|
PRODUCT_DESIGN_DBOptional | Absolute path of the SQLite database file. Set it to a folder you keep when running with npx. |
JIRA_SITEOptional | Jira site, e.g. https://your-team.atlassian.net. Only needed for the Jira tools. |
JIRA_EMAILOptional | Email of the Atlassian account. Only needed for the Jira tools. |
JIRA_API_TOKENOptional, secret | Atlassian API token. Only needed for the Jira tools. |
Details
| Package | [email protected] (NPM, stdio) |
| First published | 30 Oct 2026 |
| Last updated | 30 Oct 2026 |
| Registry name | io.github.macorifice/yeti |
More productivity servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
