Background
MCP (Model Context Protocol) is like USB-C for AI—a standardized way to connect tools, data sources, and APIs to AI assistants like Claude. Instead of constantly switching between your AI assistant and various dashboards, MCP servers let you manage infrastructure, content, and tickets directly from your conversation.
The MCP servers developed here follow strict security standards designed for production use. Each server implements defense-in-depth security:
- Token Protection – API credentials stored as encrypted strings, never logged or exposed
- Input Validation – Pydantic models enforce strict data types and allowlists
- API Hardening – TLS verification, timeouts, and hardcoded endpoints prevent SSRF attacks
- No Dangerous Operations – No filesystem access, shell execution, or code evaluation
- Supply Chain Security – Automated CVE scanning via GitHub Actions and Dependabot
For the full design philosophy and security architecture, read: Building MCP Servers the Right Way: Security Standards and Cross-Platform Design
Available MCP Servers
| Server | Description | For | Links |
|---|---|---|---|
| MCP Cloudflare | Manage DNS records, Transform Rules, Page Rules, and cache operations directly from Claude | Developers, sysadmins, and architects managing Cloudflare infrastructure | GitHub | PyPI | Container |
| MCP WordPress | Create, edit, and manage posts, pages, media, and comments through Claude | Content creators, technical writers, and DevOps teams automating content workflows | GitHub | PyPI | Container |
| MCP Request Tracker | Search, create, update, and manage RT tickets with time tracking and workflow automation | Sysadmins and support teams using Request Tracker for ticket management | GitHub | PyPI | Container |