MCP Pool

Documentation | npm | GitHub

A curated collection of Model Context Protocol (MCP) servers that give AI assistants direct 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

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

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

Adding a New MCP Server

1. Create packages/<name>/ following the structure in packages/stripe/

2. Implement a service layer (API wrapper) and tool layer (MCP interface)

3. Add tests — aim for full coverage

4. Add the package entry to release-please-config.json and .release-please-manifest.json

5. 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