Product Manager MCP
Related Servers
Alternatives to Product Manager MCP
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceRuns 13 agent slash-command workflows across Linear, GitHub, Google Docs, Slack, Firecrawl, Sheets, Tavily, Forms, Calendar, Gmail, Stripe, Granola and Notion — turning shipped features into blog and social drafts and handling competitor pricing, mention monitoring, SEO gaps, webinars, newsletters and launch-day tracking. Every credential is your own, kept in the OS keychain or client config, and anything that writes, sends or deletes is shown for approval first.29Apache 2.0
- AlicenseBqualityBmaintenanceRuns 20 slash-command workflows across Google Calendar, Gmail, Linear, Slack, Granola, Google Docs, GitHub, Stripe, Notion, Google Forms, Sheets and Drive to produce morning briefs, meeting prep, action items assigned to owners and weekly updates. Reads proceed without asking, while anything that creates, sends, changes or deletes is shown for approval first.47Apache 2.0
- AlicenseBqualityBmaintenanceEnables an agent to run ten ready-made research and monitoring workflows — competitor digests, cited reports, paper alerts, market maps, regulatory and due-diligence watches — pulling from Firecrawl, Tavily, GitHub and landing results in Notion, Slack, Google Docs, Sheets and Linear. Fields are filed with the user's own keys held in the operating system keychain, and every action that creates, sends or changes anything is shown and approved first.21Apache 2.0
- FlicenseNot gradedqualityDmaintenanceA multi-agent product-management copilot that automates morning briefings, metrics answers, knowledge lookups over an Obsidian vault, and PRD/ticket drafting.-
- AlicenseNot gradedqualityBmaintenanceEnables freelancers and agencies to run eight back-office workflows across Stripe, Google Drive, Linear, Google Calendar, Gmail, GitHub, Google Docs, Granola, Google Sheets and Firecrawl, covering client onboarding, invoices from calendar and commits, status reports, scope-creep detection, site audits and overdue invoice chasers. Reads run freely, while anything that creates, sends, changes or deletes is shown for approval first, with credentials kept in your own OS keychain and no proxying through any third-party server.Apache 2.0
- AlicenseNot gradedqualityBmaintenanceAn MCP server that turns CI failures, pull requests, security alerts, and Slack threads into Linear issues, Slack posts, changelogs, docs, and reports with evidence attached, through 25 agent-run workflows over 59 tools spanning GitHub, Linear, Slack, Notion, Google Docs, Google Calendar, Google Sheets, Firecrawl, and Tavily. It also handles credential setup in the OS keychain and pauses for approval before any create, send, change, or delete call.Apache 2.0
TDQS
Scored across 51 tools
Most tools are clearly distinguished by service prefix and resource/action naming (e.g., linear_issues_list vs linear_search_issues, slack_chat_post_message vs slack_conversations_history). However, linear_project_update_create is misleading: it posts a status update on a project, not updates the project itself, and its description references a non-existent `project_update` tool, causing confusion.
Tool names consistently use snake_case with a service prefix and action verb at the end (e.g., linear_issue_create, slack_conversations_invite, gdocs_documents_get). Minor deviations exist: connect and connection_status lack a service prefix, and notion_pages_retrieve_markdown uses 'retrieve_markdown' while other read tools use 'get'.
With 51 tools spanning 14 different services, the set is far too large for a focused product manager server. While the breadth of integrations explains some volume, many tools are single-operation (e.g., only list or create) and could be consolidated, making the surface feel bloated and unwieldy.
Core CRUD operations are missing across nearly all resources: no update or delete for issues, projects, documents, Slack messages, or Gmail drafts. Several tools referenced in descriptions (linear_teams_list, linear_workflow_states_list, linear_project_update, gforms_forms_batch_update, github_releases_create) are absent, which will cause agent failures when following documented workflows.