[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"pack-detail-mcp-productivity-suite-fr":3,"seo:pack:mcp-productivity-suite:fr":97},{"code":4,"message":5,"data":6},200,"操作成功",{"pack":7},{"slug":8,"icon":9,"tone":10,"status":11,"status_label":12,"title":13,"description":14,"items":15,"install_cmd":96},"mcp-productivity-suite","📎","#16A34A","new","Nouveau · cette semaine","Suite de Productivité MCP — Connecte l'IA à tes outils de travail","Dix serveurs MCP pour le knowledge worker qui vit dans Notion, Linear, Slack, GitHub, Google Workspace et Jira — et qui veut que Claude\u002FCodex\u002FCursor lisent et écrivent dans ces outils au lieu d'en parler. Serveurs officiels d'abord, agrégateurs multi-outils ensuite, plus des conseils d'auth et de scope pour ne pas donner à l'agent plus qu'il ne faut.",[16,28,36,44,52,60,67,75,82,89],{"id":17,"uuid":18,"slug":19,"title":20,"description":21,"author_name":22,"view_count":23,"vote_count":24,"lang_type":25,"type":26,"type_label":27},838,"32ffd470-52d3-4616-b088-122358a85cef","notion-mcp-connect-ai-agents-your-knowledge-base-32ffd470","Notion MCP — Connect AI Agents to Your Knowledge Base","Official MCP server for Notion workspace access. Search pages, read content, create and update databases, and manage tasks in Notion through Claude Code tool calls.","Notion",206,0,"en","mcp","MCP",{"id":29,"uuid":30,"slug":31,"title":32,"description":33,"author_name":34,"view_count":35,"vote_count":24,"lang_type":25,"type":26,"type_label":27},2822,"ed6f4647-de3c-4b1d-bf90-5f19903641c6","linear-mcp-project-management-for-claude-code-cursor","Linear MCP — Project Management for Claude Code & Cursor","Linear's official MCP lets Claude Code, Cursor, Codex CLI manage Linear issues, projects, cycles. Search by status, create issues from chat, link PRs.","Linear",108,{"id":37,"uuid":38,"slug":39,"title":40,"description":41,"author_name":42,"view_count":43,"vote_count":24,"lang_type":25,"type":26,"type_label":27},650,"d5a6ae87-bad8-48af-9ac6-e185dfdec309","slack-mcp-team-messaging-server-ai-agents-d5a6ae87","Slack MCP — Team Messaging Server for AI Agents","MCP server that connects AI agents to Slack workspaces. Send messages, read channels, search history, manage threads, and automate team communication via natural language. 1,500+ stars.","Slack",127,{"id":45,"uuid":46,"slug":47,"title":48,"description":49,"author_name":50,"view_count":51,"vote_count":24,"lang_type":25,"type":26,"type_label":27},655,"d6e7f6a5-0243-4507-b119-132ec9253843","github-mcp-repository-management-ai-agents-d6e7f6a5","GitHub MCP — Repository Management for AI Agents","Official GitHub MCP server that gives AI agents access to repos, issues, PRs, code search, and Actions. Create branches, review PRs, and manage projects via natural language. 5,000+ stars.","GitHub",138,{"id":53,"uuid":54,"slug":55,"title":56,"description":57,"author_name":58,"view_count":59,"vote_count":24,"lang_type":25,"type":26,"type_label":27},3146,"07565199-d466-4fdf-83f7-3e12f339a8b7","google-workspace-mcp-gmail-calendar-drive-for-agents","Google Workspace MCP — Gmail\u002FCalendar\u002FDrive for Agents","Google Workspace MCP exposes Gmail, Calendar, and Drive actions as MCP tools so agents can summarize inboxes and manage schedules with minimal scopes.","MCP Hub",61,{"id":61,"uuid":62,"slug":63,"title":64,"description":65,"author_name":58,"view_count":66,"vote_count":24,"lang_type":25,"type":26,"type_label":27},3200,"1a2f8e2b-7c7d-4a0c-bcbb-1d9b1a0b9d0f","mcp-atlassian-jira-confluence-tools-for-agents","MCP Atlassian — Jira + Confluence Tools for Agents","mcp-atlassian is an MCP server for Jira and Confluence so your agent can search, create, and update issues\u002Fpages via IDE MCP configuration.",5,{"id":68,"uuid":69,"slug":70,"title":71,"description":72,"author_name":73,"view_count":74,"vote_count":24,"lang_type":25,"type":26,"type_label":27},2785,"6df0de55-d600-4bf0-a6cd-72b551f551be","le-chat-connectors-slack-notion-drive-tools-for-claude","Le Chat Connectors — Slack, Notion, Drive Tools for Claude","Le Chat ships pre-validated connectors for Slack, Notion, Drive, Linear, Figma. Wire them into Claude Code or Cursor as MCP servers via le-chat-mcp.","Mistral AI",80,{"id":76,"uuid":77,"slug":78,"title":79,"description":80,"author_name":58,"view_count":81,"vote_count":24,"lang_type":25,"type":26,"type_label":27},515,"1abeff10-d6be-45f3-b47c-f5998d7a08a4","airweave-context-retrieval-layer-ai-agents-50-integrations-1abeff10","Airweave — Context Retrieval Layer for AI Agents, 50+ Integrations","Open-source context retrieval layer connecting AI agents to 50+ apps including Notion, Slack, GitHub, and Jira. Unified search API with MCP support.",140,{"id":83,"uuid":84,"slug":85,"title":86,"description":87,"author_name":58,"view_count":88,"vote_count":24,"lang_type":25,"type":26,"type_label":27},698,"cf74621a-0188-4222-8c9b-285873183b56","composio-250-tool-integrations-ai-agents-cf74621a","Composio — 250+ Tool Integrations for AI Agents","Connect AI agents to 250+ tools (GitHub, Slack, Gmail, Jira, etc.) with managed auth and natural language actions. Works with LangChain, CrewAI, and OpenAI.",82,{"id":90,"uuid":91,"slug":92,"title":93,"description":94,"author_name":58,"view_count":95,"vote_count":24,"lang_type":25,"type":26,"type_label":27},806,"b84b96fd-0fc2-439d-9f29-4fb564bc2ded","tempo-mcp-calendar-time-tracking-agents-b84b96fd","Tempo MCP — Calendar and Time Tracking for Agents","MCP server that gives AI agents calendar awareness and time tracking. Tempo MCP integrates with Google Calendar and Toggl for scheduling, time logging, and availability checks.",129,"tokrepo install pack\u002Fmcp-productivity-suite",{"pageType":98,"pageKey":8,"locale":25,"title":99,"metaDescription":100,"h1":101,"tldr":102,"bodyMarkdown":103,"faq":104,"schema":120,"internalLinks":126,"citations":139,"wordCount":152,"generatedAt":153},"pack","MCP Productivity Suite — 10 Servers to Connect AI to Your Work Tools","Notion, Linear, Slack, GitHub, Google Workspace, Atlassian — ten MCP servers that turn Claude\u002FCodex\u002FCursor into a real teammate inside the tools you already use. Auth, scope safety, and an opinionated install order.","MCP Productivity Suite — Connect Your AI Agent to the Tools You Actually Use","Ten MCP servers for the knowledge worker. Start with one official SaaS connector, get the OAuth dance right, lock scopes down, then add a second tool. Multi-tool aggregators come last — they're a power move, not a starting point.","## What's in this pack\n\nThis is the suite for the person whose week is half Notion docs, a quarter Linear tickets, and the rest scattered across Slack threads, GitHub PRs, Gmail, and a calendar that lies to them. The goal is not \"plug in everything.\" The goal is to get Claude\u002FCodex\u002FCursor to **read and write the tools you actually live in**, one tool at a time, without giving the agent more permission than you'd give an intern on day one.\n\nEvery pick here is an MCP server (Model Context Protocol) that exposes tool calls — search a Notion page, create a Linear ticket, draft a Slack reply, read a Gmail thread, comment on a GitHub PR. Most are official servers from the vendor. A few are multi-tool aggregators (Le Chat Connectors, Airweave, Composio) for when you want one MCP that reaches a dozen SaaS apps. **Aggregators are useful but they're also a bigger blast radius — they go last in this pack on purpose.**\n\n## Install order — pick one SaaS, then the next\n\n1. **Notion MCP** — start here if your team's source of truth is Notion. Search pages, read content, append blocks, manage database rows. Read-only token first; you can always upgrade scopes later.\n2. **Linear MCP** — if you triage tickets daily, this is the highest-leverage pick. Create issues from a Slack thread, comment on issues from a PR, move statuses without leaving the editor.\n3. **Slack MCP** — read channels you're already in, post as yourself, fetch threads for context. Treat the bot scope like a loaded gun: start in DM-only, add channels deliberately.\n4. **GitHub MCP** — repository management, PR review, issue triage. If you're an engineer this is non-negotiable; if you're a PM, the read-only flavor still pays for itself by Friday.\n5. **MCP Atlassian** — Jira + Confluence in one server. Substitute for Asana if your team is Atlassian-shaped (most enterprises are). Scope to one project before you scope to a workspace.\n6. **Google Workspace MCP** — Gmail, Calendar, Drive in one. Read calendar for free; sending email needs an explicit scope upgrade. **Don't grant `gmail.send` until you've watched it draft for a week.**\n7. **Tempo MCP** — Calendar + time tracking. The piece Google Workspace MCP can't do: log hours, query worklogs, build weekly summaries. Skip if you don't track time.\n8. **Le Chat Connectors** — Mistral's bundle: Slack + Notion + Drive in a single MCP. Pick this **instead of** installing 3 separate servers if you don't need the deeper per-tool capabilities.\n9. **Airweave** — context retrieval across 50+ integrations. Use as a unified search\u002Fread layer; pair with the official write-capable servers above. Heavier setup, bigger payoff.\n10. **Composio** — 250+ tool integrations including the long tail (HubSpot, Intercom, Salesforce, Trello). The escape hatch when a vendor has no official MCP.\n\n## Auth tips — get this right or skip the pack\n\n- **OAuth > raw API tokens** whenever offered. OAuth tokens are scoped, revocable, auditable. Raw API tokens with `admin:write` are how blast radii happen.\n- **Notion**: create an internal integration, share it to *one* parent page first. Database access is per-page; the integration sees only what you explicitly share.\n- **Linear**: personal API key works, but OAuth app with team-scoped permissions is safer for any agent that touches production tickets.\n- **Slack**: bot token (`xoxb-`) for posting, user token (`xoxp-`) only if you need to read DMs. Never paste either into a public repo — Slack auto-revokes tokens that hit GitHub, but agents reading config files can still leak them upstream.\n- **GitHub**: prefer fine-grained Personal Access Tokens scoped to specific repos. Avoid classic PATs with `repo` scope unless you actually need to write to *every* repo you can see.\n- **Google Workspace**: separate scopes for read-vs-write. Calendar read is harmless; Gmail send is not. Most aggregators ask for the kitchen sink — say no, then add scopes one at a time.\n- **Atlassian**: API token + email pair for Cloud, OAuth for Server. Project-scoped users are a 5-minute admin task that prevents most of the \"agent moved 400 tickets\" disasters.\n\n## Scope safety — a checklist before each install\n\n1. **Read-only first**. Almost every MCP server has a read-only flavor. Wire it in, prove the agent's call patterns match what you expected, *then* upgrade to write.\n2. **One workspace, one project**. Don't scope a new MCP to your entire org. Pick the lowest-stakes project you have and scope to it.\n3. **Watch the first 5 calls**. Most MCP clients (Claude Code, Cursor, Codex) log tool calls. Tail them while the agent works for the first hour.\n4. **Rotate tokens on a schedule**. 90 days is plenty. Calendar reminder, not a TODO.\n5. **Audit who has what**. Notion integrations, GitHub apps, Slack bots — each platform has an admin page that lists every connected token. Visit it monthly.\n6. **Kill switches**. Know how to revoke each integration *before* you install it. \"How do I yank this token at 2am\" should have an answer.\n\n## Workflows this pack unlocks\n\n- **Weekly review without tab-switching** — Notion + Linear + Calendar in one agent context. Ask: \"What shipped, what slipped, what's blocking next week?\" and let it pull from the three sources directly.\n- **PR-to-ticket loop** — GitHub MCP reads the diff, Linear MCP creates a follow-up ticket with the PR linked, Slack MCP notifies the right channel. Three tool calls, no human glue.\n- **Customer thread digest** — Slack + Gmail + Notion. Agent reads a customer escalation thread, drafts a Notion postmortem stub, leaves the Gmail reply in drafts for you to send.\n- **Standup replacement** — Calendar + Linear + Slack. Agent reads yesterday's closed tickets, today's calendar, and posts a Slack standup that's actually accurate.\n\n## Common pitfalls\n\n- **Granting `admin:*` scopes \"just to test\"** — you'll forget. Start scoped; expand only when needed.\n- **Installing 5 MCP servers in one afternoon** — overwhelms the agent's tool-call budget and makes failures hard to diagnose. One per day, verify, then the next.\n- **Forgetting that OAuth tokens expire** — refresh flow needs to work, or the agent silently degrades to \"I don't have access to that tool\" answers a month later.\n- **Aggregators that re-surface every scope as their own** — Airweave\u002FComposio\u002FLe Chat each ask for combined scopes. Read what they're actually requesting; it's often more than the sum of the individual integrations.\n- **Letting the agent loose on a shared Slack channel** — set a dedicated `#agent-output` channel for the first month. Promote to your team channels only after the failure mode is well understood.\n- **No revocation drill** — if you can't revoke all 10 integrations in 5 minutes, you don't have a suite, you have a liability.",[105,108,111,114,117],{"q":106,"a":107},"Do I need all ten MCP servers, or can I just install the ones for tools I use?","Just the ones you use. The pack is a menu, not a recipe. A solo founder might run only Notion + GitHub + Calendar. A PM might run Linear + Slack + Notion + Google Workspace. The aggregators (Le Chat Connectors, Airweave, Composio) are alternatives or supplements — pick one if you want broader coverage with less setup, but you'll trade some depth per-tool.",{"q":109,"a":110},"Should I use the official Notion\u002FSlack\u002FGitHub MCP, or an aggregator like Composio that covers all of them?","Start with official servers. They're maintained by the vendor, scopes map cleanly to that vendor's permission model, and you can audit one tool at a time. Aggregators are excellent when you need the long tail (HubSpot, Intercom, Linear-plus-five-other-PM-tools) or when the per-tool capability set in the official server is more than you need. Most teams end up running both: official servers for the 3-4 tools they touch hourly, aggregators for the rest.",{"q":112,"a":113},"How dangerous is letting an MCP agent write to Slack or send Gmail?","More dangerous than reading. The mitigation is scope, not avoidance: a Slack bot scoped to one channel and a Gmail account with only `gmail.compose` (drafts, not send) is genuinely safe to give an agent. The unsafe path is granting `chat:write` across all channels plus `gmail.send` and walking away. Watch the first 50 actions, then expand scope based on observed behavior.",{"q":115,"a":116},"Which MCP server should I install first if I'm new to MCP entirely?","Notion MCP if you live in Notion, or GitHub MCP if you're an engineer. Both have clean OAuth, well-documented scopes, and the cost of a mistake is recoverable (Notion has page-level undo; GitHub PR comments and issues can be deleted). Avoid Slack and Gmail as your first MCP — the audience for mistakes is bigger and the recovery is slower.",{"q":118,"a":119},"What about Asana — there's no official MCP yet?","Correct, no official Asana MCP at time of writing. Two workarounds: (1) Composio includes Asana as one of its 250+ integrations, so it works via the aggregator path; (2) if your team is open to a switch, MCP Atlassian (Jira) and Linear MCP both have first-class servers and richer agent tool surfaces. We're tracking the official Asana MCP and will add it to this pack when it ships.",{"@context":121,"@type":122,"name":123,"description":124,"numberOfItems":125,"inLanguage":25},"https:\u002F\u002Fschema.org","ItemList","MCP Productivity Suite","Ten MCP servers for knowledge workers, covering Notion, Linear, Slack, GitHub, Google Workspace, Atlassian, and multi-tool aggregators — with auth and scope-safety guidance.",10,[127,131,135],{"url":128,"anchor":129,"reason":130},"\u002Fen\u002Fai-tools-for\u002Fmcp","All MCP server configs on TokRepo","Browse the full MCP catalog beyond this curated pack",{"url":132,"anchor":133,"reason":134},"\u002Fen\u002Ftopics","Other topic packs","Adjacent packs include AI coding agents, multi-agent frameworks, and personal RAG",{"url":136,"anchor":137,"reason":138},"\u002Fen\u002Ffeatured","Featured assets on TokRepo","These MCP servers live in the broader curated catalog",[140,144,148],{"claim":141,"source_name":142,"source_url":143},"Model Context Protocol is an open standard for connecting AI assistants to data and tools","Model Context Protocol docs","https:\u002F\u002Fmodelcontextprotocol.io\u002F",{"claim":145,"source_name":146,"source_url":147},"Notion supports per-page integration permissions via internal integrations","Notion developers docs","https:\u002F\u002Fdevelopers.notion.com\u002F",{"claim":149,"source_name":150,"source_url":151},"GitHub fine-grained Personal Access Tokens scope access to specific repositories","GitHub authentication docs","https:\u002F\u002Fdocs.github.com\u002Fen\u002Fauthentication\u002Fkeeping-your-account-and-data-secure\u002Fmanaging-your-personal-access-tokens",1120,"2026-05-22T09:00:00Z"]