​

MCPs Node (Model Context Protocol)

​

Overview

​

What are MCPs?

• Documentation lookup (Context7)
• Database connections (PostgreSQL, MongoDB)
• File systems
• Custom APIs

​

MCP Structure

{
  "context7": {
    "command": "npx",
    "args": ["-y", "@context7/mcp-server"],
    "env": {
      "CONTEXT7_API_KEY": "your-key"
    }
  }
}

​

Built-in MCPs

​

Context7 (Documentation Lookup)

{
  "context7": {
    "command": "npx",
    "args": ["-y", "@context7/mcp-server"],
    "env": {
      "CONTEXT7_API_KEY": "your-api-key"
    }
  }
}

​

File System MCP

{
  "filesystem": {
    "command": "npx",
    "args": ["-y", "@modelcontextprotocol/server-filesystem", "/allowed/path"]
  }
}

​

Database MCPs

{
  "postgresql": {
    "command": "npx",
    "args": ["-y", "@modelcontextprotocol/server-postgres"],
    "env": {
      "DATABASE_URL": "postgresql://user:pass@localhost/db"
    }
  }
}

​

Creating Custom MCPs

1. Click “Add New MCP”
2. Enter name (e.g., “Internal API”)
3. Define command: node server.js
4. Add arguments: ["--port", "3000"]
5. Set environment variables (API keys, URLs)
6. Save to workspace library

​

Configuration

• Edit command and args
• Set environment variables
• Configure connection settings
• Test connectivity

​

Real-World Examples

​

Example 1: Slack Integration

{
  "slack": {
    "command": "node",
    "args": ["slack-mcp-server.js"],
    "env": {
      "SLACK_TOKEN": "xoxb-your-token",
      "SLACK_CHANNEL": "#general"
    }
  }
}

• Send Slack messages
• Read channel history
• Search conversations

​

Example 2: Redis Cache

{
  "redis": {
    "command": "node",
    "args": ["redis-mcp.js"],
    "env": {
      "REDIS_URL": "redis://localhost:6379"
    }
  }
}

• Cache frequently-used data
• Store session information
• Implement rate limiting

​

Example 3: AWS Services

{
  "aws": {
    "command": "node",
    "args": ["aws-mcp-server.js"],
    "env": {
      "AWS_REGION": "us-east-1",
      "AWS_ACCESS_KEY_ID": "your-key",
      "AWS_SECRET_ACCESS_KEY": "your-secret"
    }
  }
}

• Upload files to S3
• Query DynamoDB
• Invoke Lambda functions

​

Security Considerations

• MCPs have full system access based on their permissions
• Store credentials in environment variables (not hardcoded)
• Use read-only database accounts when possible
• Audit MCP server code before use
• Restrict network access via firewalls

​

MCP vs. Skills

​

Troubleshooting

​

MCP won’t connect

1. Command path is correct
2. Dependencies installed (npx can find package)
3. Environment variables set correctly
4. Network connectivity (for remote services)
5. Authentication credentials valid

​

MCP is slow

• Add caching layer
• Use connection pooling
• Implement rate limiting
• Choose geographically-close servers

​

Next Steps

• Hooks Node - Lifecycle events
• Sub-agents Node - Specialized agents