MCP Integration
mittwald MCP lets you manage your hosting infrastructure through AI assistants like Claude, Copilot, or ChatGPT using natural language.
This is part of the Agentic Integration capabilities at mittwald. While IDE Integration focuses on code generation, MCP enables infrastructure management through natural language.
Quick Start
Connect your AI tool to the mittwald MCP server:
https://mcp.mittwald.de/mcp
Choose your tool and follow the setup guide:
| Tool | Type | Setup Time |
|---|---|---|
| Claude Desktop | Desktop/Web App | ~5 min |
| ChatGPT | Web/Mobile App | ~5 min |
| Claude Code | CLI | ~10 min |
| GitHub Copilot | IDE Extension | ~10 min |
| Cursor | IDE | ~10 min |
| Codex CLI | CLI | ~10 min |
Once connected, try a simple command in your AI tool:
Use mittwald MCP to list my projects
What is MCP?
MCP (Model Context Protocol) is an open standard that connects AI assistants to external services. Instead of building separate integrations for each AI tool, mittwald provides one MCP server that works with all MCP-compatible clients.
Your AI assistant sends requests to the mittwald MCP server, which translates them into API calls and returns results. You interact in natural language; the protocol handles the rest.
Agentic Integration: AI That Takes Action
Traditional AI assistants suggest what to do. Agentic AI executes it.
Instead of receiving API documentation to copy-paste, you describe your goal:
"Create a project with WordPress, MySQL database, and daily backups"
The agent determines which tools to call, handles authentication, executes the steps in sequence, and reports the result. Multi-step workflows that previously required manual coordination happen automatically.
Agents have guardrails: destructive operations require confirmation, and you maintain oversight of what actions are taken.
Authentication
mittwald MCP uses OAuth 2.1 with PKCE for authentication. When you connect a tool:
- You authenticate directly with mittwald in your browser
- You approve specific permissions for the tool
- mittwald issues a temporary token to the tool
- The tool uses this token—never your password
Tokens are scoped to specific permissions, expire automatically, and can be revoked anytime. Your credentials stay with mittwald.
For CI/CD pipelines or headless environments, you can also use API tokens instead of OAuth.
MCP Ecosystem Servers
In addition to the mittwald MCP server, teams often combine third-party MCP servers for product-specific tasks:
- OpenSearch MCP: Search indices, inspect mappings, and review cluster behavior
- Apache Solr MCP: Hybrid keyword/vector search workflows on Solr-backed data
- TYPO3 MCP: TYPO3 content and backend automation via MCP
For a comprehensive list of available MCP servers, see the MCP Server Registry.
Related Documentation
Explore other agentic integration capabilities:
- IDE Integration — Use mittwald AI models for code generation
- Agent Skills — Pre-built workflows for migrations and deployments
Next Steps
- Getting Connected — Detailed setup guides for all supported tools
- Tutorials — End-to-end walkthroughs for common scenarios
- How-To Guides — Task-focused guides for day-to-day operations
- Runbooks — Incident recovery procedures