MCP servers for a product ops agent
The MCP server bundle to build an AI that connects product analytics to engineering work.
3 servers · ~34 tools · Last updated June 17, 2026
TL;DR: Product ops lives between analytics and engineering. This bundle lets an agent read product usage, then turn insights into issues and tie them back to the codebase — closing the loop from signal to shipped change.
Bottom line: start with Linear MCP Server (official remote) and add the rest as your needs grow. All 3 install together via the merged config below (~34 tools total).
Tool budget: this stack exposes about 34 tools. That's within Cursor's practical ~40-tool ceiling, so all servers can stay enabled together. Check your own config →
What's in the stack
One-click config
All 3 servers merged into a single block — pick your client and paste.
{
"mcpServers": {
"linear-mcp-server-official-remote": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://mcp.linear.app/mcp"
]
},
"github-mcp-server": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"GITHUB_PERSONAL_ACCESS_TOKEN",
"ghcr.io/github/github-mcp-server"
],
"env": {
"GITHUB_PERSONAL_ACCESS_TOKEN": "<your-github-pat>"
}
},
"posthog-mcp-server-official-remote": {
"command": "npx",
"args": [
"-y",
"mcp-remote@latest",
"https://mcp.posthog.com/mcp",
"--header",
"Authorization:${POSTHOG_AUTH_HEADER}"
],
"env": {
"POSTHOG_AUTH_HEADER": "Bearer <your-personal-api-key>"
}
}
}
}Paste into ~/Library/Application Support/Claude/claude_desktop_config.json and fully restart Claude Desktop. Replace any placeholder keys/tokens with your own.
Capabilities this stack covers
FAQ
What does a product ops agent automate?
It can summarize analytics, draft issues for the friction it finds, and link them to the relevant code — work that's otherwise manual triage.
Can I use Amplitude/Mixpanel?
Swap the analytics slot if you use a different tool; the rest of the loop stays the same.