PopMCPOps and projects MCP stack for your AI
Where the work is discussed, where it is written down, and the three trackers it is actually recorded in.
- Slack
- Notion
- Linear
- Asana
- ClickUp
app.popmcp.com/mcpThe 5 connections
Work gets decided in Slack, described in Notion, and tracked in whichever system the team that owns it prefers. None of them can see the others.
- SlackAPI credentialConversationsAdmin conversationsAdmin usersFiles229tools21triggers
- NotionAPI credentialBlocksData sourcesCommentsDatabases30tools11triggers
- LinearAPI credentialIntegrationDeleteIssueAttachment506tools24triggers
- AsanaAPI credentialTasksProjectsPortfoliosGoals247tools24triggers
- ClickUpAPI credentialChatTasksTime trackingViews169tools23triggers
Across the stack439 read and 742 write operations, 253 API modules1,181tools103triggers
One question, every connection
The tool names below are the real ones your client calls. Check any chain against the catalog on the integration’s own page.
Turn that thread into an issue and post the link back.
- Slack
slack_conversations_historyslack_conversations_repliesslack_chat_get_permalink - Linear
linear_teamslinear_workflow_stateslinear_issue_create - Slack
slack_chat_post_message
The context stays attached to the ticket and the channel learns where it went — the two halves that normally get lost in a copy-paste.
Give me one standup across all three trackers.
- Linear
linear_cycleslinear_issues - Asana
asana_search_tasks_for_workspace - ClickUp
clickup_get_filtered_team_tasks - Slack
slack_chat_post_message
What is overdue, unassigned or blocked, from three systems at once, posted where the team already reads.
Write this week's update from what actually moved.
- Linear
linear_issueslinear_comments - Asana
asana_get_tasks_for_projectasana_get_stories_for_task - ClickUp
clickup_get_time_entriesclickup_get_lists - Notion
notion_searchnotion_create_pagenotion_append_block_children
The update is assembled from closed issues, task activity and logged time, then filed in the doc where updates live.
Turning it on
Nothing to deploy, and nothing to install on the provider side.
- Connect the accounts
One connection per store, property or ad account. Each takes an API credential off one settings screen. Credentials are encrypted at rest and never reach your AI client.
- Tick what each client reaches
Your client signs in to PopMCP with OAuth and gets only the connections you approve. Writes run the moment it calls them, so keep reporting teammates on read-only.
- Register one URL
app.popmcp.com/mcp, once per client. Claude, ChatGPT, Codex and the rest reach the same five connections with the same permissions.
Five connections need Starter or above — the free tier holds two. See what each plan includes.
The other stacks
Same endpoint, same controls. Most teams end up running two or three of them side by side.
Questions about the ops and projects stack
Can it read private channels and pages?
Only what the credential you connect can already reach. Slack sees the channels its token is in, and Notion sees only the pages and databases you explicitly share with the integration. PopMCP does not widen a connection's access — it is the same account, reached from a different place.
Will it post to Slack without asking?
It can post the moment it calls the tool, so treat a connection with posting rights as one. If you want the summaries without the risk, the read tools alone cover history, threads and permalinks; keep teammates on read-only and the posting tools are not in their list at all.
Do I need all three trackers?
Connect the ones you run. The stack exists because most companies run more than one and cannot consolidate, but Slack plus one tracker plus Notion is already the shape of it — the thread-to-ticket and the written update both work with a single tracker connected.
Connect the ops and projects stack to your AI
Add Slack, Notion, Linear and the rest with credentials you already own, and get one secure MCP URL for all of them.