Expert MCP Bot

End-to-end MCP integration agent for creating, configuring, and deploying MCP server configurations within the claude-code-templates ecosystem.

When to Use This Agent

Choose this agent when you need to:

• Create a complete MCP server configuration file for a new service integration
• Set up authentication and environment variables for MCP server deployments
• Optimize an existing MCP configuration for performance and reliability
• Generate installable MCP packages compatible with the claude-code-templates CLI

Consider alternatives when:

• You need to audit the security of an MCP server implementation (use MCP Security Auditor)
• You want to discover third-party servers from registries (use Guide MCP Navigator)

Quick Start

Configuration

Copy
name: expert-mcp-bot
type: agent
category: mcp-dev-team

Example Invocation

Copy
claude agent:invoke expert-mcp-bot "Create an MCP integration for Stripe with payment processing and subscription management"

Example Output

MCP Integration Created: stripe-payments
=========================================

File: cli-tool/components/mcps/stripe-payments.json
Server Name: Stripe Payments MCP
Package: @stripe/mcp-server@latest
Transport: stdio

Environment Variables:
  STRIPE_SECRET_KEY    - Required - Stripe API secret key
  STRIPE_WEBHOOK_SECRET - Required - Webhook signature verification
  STRIPE_API_VERSION   - Optional - Defaults to 2024-12-18

Tools Available: 9
  - create-payment-intent (idempotent)
  - retrieve-payment (read-only)
  - list-subscriptions (read-only)
  - create-subscription (idempotent)
  - cancel-subscription (destructive)
  - create-refund (destructive)
  - list-invoices (read-only)
  - retrieve-customer (read-only)
  - create-customer (idempotent)

Install Command:
  npx claude-code-templates@latest --mcp="stripe-payments" --yes

Core Concepts

Integration Categories Overview

Aspect	Details
API Connectors	REST and GraphQL service integrations (GitHub, Stripe, Slack)
Database MCPs	PostgreSQL, MySQL, MongoDB with connection pooling
Cloud Services	AWS, GCP, Azure resource management
Dev Tools	Linters, build systems, testing frameworks
File Systems	Controlled local filesystem access with path restrictions
Real-time Data	WebSocket streams, event buses, monitoring feeds

MCP Integration Architecture

┌─────────────┐     ┌─────────────┐
│  Config      │────▶│  Package     │
│  Template    │     │  Resolver    │
└─────────────┘     └─────────────┘
        │                   │
        ▼                   ▼
┌─────────────┐     ┌─────────────┐
│  Env Var     │────▶│  Claude Code │
│  Manager     │     │  Runtime     │
└─────────────┘     └─────────────┘

Configuration

Parameter	Type	Default	Description
outputDir	string	"cli-tool/components/mcps/"	Directory for generated MCP configuration files
packageManager	enum	"npx"	Package execution: npx, bunx, or direct command
envValidation	boolean	true	Validate required env vars exist before server start
retryAttempts	number	3	Number of retry attempts for failed connections
connectionTimeout	number	30000	Connection timeout in milliseconds

Best Practices

1. Never Hardcode Secrets in Configuration Files All sensitive values must use environment variable references. Store API keys, tokens, and connection strings in environment variables and reference them in the MCP configuration. This prevents accidental exposure through version control.

2. Pin Package Versions for Production Stability While @latest is convenient for development, production configurations should pin to a specific version. Unpinned packages may introduce breaking changes during automatic updates, causing integration failures without code changes.

3. Group Related API Operations into Single Servers Avoid creating separate MCP configurations for each endpoint of the same service. A single Stripe MCP server should handle payments, subscriptions, and customers together. This reduces connection overhead and simplifies credential management.

4. Document Every Environment Variable Thoroughly Each environment variable in your MCP configuration should include a comment or companion documentation explaining its purpose, format, and where to obtain the value. Users who cannot configure authentication cannot use your integration.

5. Test Configuration on a Clean Environment Before publishing, verify the MCP configuration works on a machine without your local development dependencies. Run the install command in a fresh environment to catch missing dependencies and undocumented setup steps.

Common Issues

1. MCP server fails to start with "command not found" error The specified npm package does not exist or the package name is incorrect. Verify the package name on npm, ensure it exposes a binary entry point, and test with npx directly before embedding in the configuration.

2. Environment variables are set but server reports authentication failure The variable names in the configuration do not match what the MCP server package expects. Check the server package's documentation for exact variable names. Common mismatches include APIKEY vs API_KEY and TOKEN vs ACCESS_TOKEN.

3. Integration works locally but fails after CLI installation The CLI merges configurations into the user's .mcp.json file, which may have conflicting server names or duplicate environment variable references. Use unique, descriptive server names and check for conflicts with existing MCP configurations.