MC Pool
A curated collection of Model Context Protocol (MCP) servers for popular SaaS platforms — Stripe, Sentry, Notion, Linear, Datadog, Vercel, PagerDuty, HubSpot, Intercom, Shopify, Google Workspace
README
MCP Pool
Documentation | npm | GitHub
A curated collection of Model Context Protocol (MCP) servers that give AI assistants direct, read-only access to popular SaaS APIs — no dashboard switching required.
MCP Pool bridges the gap between AI chat interfaces and the business tools teams rely on daily. Ask questions in natural language, get real answers backed by live data.
Packages
| Package | Description | Version |
|---|---|---|
| @vineethnkrishnan/stripe-mcp | Stripe — payments, customers, subscriptions, invoices | |
| @vineethnkrishnan/sentry-mcp | Sentry — issues, events, stack traces. Self-hosted support. | |
| @vineethnkrishnan/notion-mcp | Notion — pages, databases, search, content | |
| @vineethnkrishnan/linear-mcp | Linear — issues, projects, teams (GraphQL) | |
| @vineethnkrishnan/datadog-mcp | Datadog — monitors, metrics, events. Multi-site support. | |
| @vineethnkrishnan/vercel-mcp | Vercel — deployments, projects, build logs | |
| @vineethnkrishnan/pagerduty-mcp | PagerDuty — incidents, on-call, services. EU support. | |
| @vineethnkrishnan/hubspot-mcp | HubSpot — contacts, deals, companies | |
| @vineethnkrishnan/intercom-mcp | Intercom — conversations, contacts, support | |
| @vineethnkrishnan/shopify-mcp | Shopify — orders, products, customers | |
| @vineethnkrishnan/google-workspace-mcp | Google Workspace — Gmail, Calendar, Drive, Sheets |
Quick Start
Prerequisites
- Node.js >= 20 (see
.nvmrc)
Use with Claude Desktop
Add to your claude_desktop_config.json:
{
"mcpServers": {
"stripe": {
"command": "npx",
"args": ["-y", "@vineethnkrishnan/stripe-mcp"],
"env": {
"STRIPE_SECRET_KEY": "sk_test_..."
}
}
}
}
Then ask Claude things like:
- "How many active subscriptions do we have?"
- "Why did the last payment for cus_123 fail?"
- "Show me our current Stripe balance."
Development
# Clone and install
git clone https://github.com/vineethkrishnan/mcp-pool.git
cd mcp-pool
npm install
| Command | Description |
|---|---|
npm run build |
Build all packages |
npm test |
Run tests across all packages |
npm run lint:check |
Lint with ESLint |
npm run format:check |
Check formatting with Prettier |
npm run docs:start |
Start docs dev server |
Project Structure
mcp-pool/
├── packages/
│ ├── oauth-core/ # Shared OAuth 2.0 infrastructure
│ │ └── src/
│ │ ├── strategies/ # OAuth & static token strategies
│ │ └── cli/ # Auth login/logout CLI helpers
│ └── <server>/ # MCP server (×11)
│ └── src/
│ ├── index.ts # MCP server entry point
│ ├── services/ # API SDK wrapper
│ ├── tools/ # MCP tool definitions
│ └── common/ # Shared types & utilities
├── docs/ # Docusaurus documentation site
├── .github/workflows/ # CI, quality, security, release
└── package.json # Monorepo root (npm workspaces)
CI/CD
| Workflow | Trigger | What it does |
|---|---|---|
| CI | Push / PR to main |
Lint, test (Node 20 + 22), build |
| Quality | Push / PR to main |
Dead code detection (knip), code duplication (jscpd) |
| Security | Push / PR / weekly | CodeQL analysis, dependency review, Trivy scan |
| Commit Lint | PR | Validates PR title follows Conventional Commits |
| Release | Push to main |
release-please versioning, npm publish, docs deploy |
Adding a New MCP Server
- Create
packages/<name>/following the structure inpackages/stripe/ - Implement a service layer (API wrapper) and tool layer (MCP interface)
- Add tests — aim for full coverage
- Add the package entry to
release-please-config.jsonand.release-please-manifest.json - Add documentation pages in
docs/
See CONTRIBUTING.md for full guidelines.
Commit Convention
All commits follow Conventional Commits:
feat(stripe): add refund support
fix(stripe): handle null customer email
docs: update installation guide
Enforced via commitlint + husky pre-commit hooks.
Documentation
Visit the documentation site for detailed guides on each MCP server.
Roadmap
See the roadmap for planned features and upcoming milestones:
- v0.2.0 — Write operations, SSE transport, streaming responses
- v0.3.0 — Webhooks, multi-account, expanded API coverage, new servers
License
MIT — Vineeth Krishnan
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.