mittwald
by mittwald
Manage mittwald managed hosting from your AI assistant: projects, apps, containers, databases, DNS, mail, cronjobs and backups. 116 tools, OAuth 2.1 with PKCE or an API token.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Connect mittwald via MCP
https://mcp.mittwald.de/mcpWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
Use in Agentman
Connect mittwald once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman Studiomittwald Tools & Capabilities (116)
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Limits
- The tool list is directory-sourced, not handshake-verified. The endpoint requires authentication, so we have no per-tool descriptions, no parameter schemas and no
readOnlyHintannotations. Read, write and delete labels on this page are derived from mittwald's naming convention and its documentation, not from the server's own annotations. - No read-only endpoint exists. The only safety separation is the OAuth scope set you approve at the consent screen. Probed 2026-09-08.
- The API is rate-limited and the limits are not published as numbers. mittwald's OpenAPI specification states usage is rate-limited to prevent abuse and directs callers to the
X-Ratelimit-*headers on each response for their own current figures. The REST API's ownRateLimitErrorresponse schema — an API error shape, not an MCP tool — appears on 432 of its 515 paths. mittwald publishes no fixed quota (https://api.mittwald.de/v2/openapi.json, fetched 2026-09-08). - The connector will not move your data for you. SSH, database dumps and backup downloads are handed back as a command or URL rather than executed, per mittwald's own description. Useful as a safety property, but it means the agent cannot complete those tasks end to end.
- You only reach what your own account owns. Every tool acts against your mittwald projects, servers and organisations. This is not a way to inspect someone else's hosting.
- OAuth needs a browser. mittwald says the OAuth path is unsuitable for headless servers and directs those users to API tokens, which do not auto-refresh.
- Rate-limit headers are not exposed on the MCP endpoint's unauthenticated response. Our anonymous probe returned a 401 with an OAuth challenge and no
x-ratelimit-*headers, so we cannot state the connector's own throttle from observation. - Documentation is English on the pages we read. mittwald's developer portal offers a German locale, and its privacy policy is German-only. The MCP documentation subtree we cited served English.
- This connector manages production infrastructure. mittwald's own instruction is to approve destructive or cost-impacting changes explicitly and not to run the agent unattended.
Frequently asked questions
No plan gate is documented for the connector itself. mittwald's Claude Code guide lists only three prerequisites: a mittwald account to authenticate with, a web browser for the OAuth login, and Claude Code installed. What you can actually reach is bounded by the mittwald resources your account already owns, because every tool acts on your own projects and servers.
Both, and OAuth 2.1 with PKCE is the recommended path. mittwald's connection guide presents OAuth as the default for interactive use and an mStudio API token sent as a bearer header as the alternative for CI/CD, headless servers and scripts. The vendor warns that API tokens do not auto-refresh and must be rotated manually.
About one hour. mittwald's connection guide states that OAuth access tokens expire after roughly an hour and that most clients refresh them automatically using the refresh token. API tokens behave differently: mittwald says they stay valid until you revoke them, which is why the vendor flags manual rotation as the trade-off for headless use.
No. mittwald's documentation states your password is entered only at mittwald's own OAuth server in your browser, and the client receives a temporary access token instead. The vendor adds that a compromised token has limited impact because it is short-lived, scoped to the permissions you approved, and revocable from mStudio.
Yes. Eighteen of the 116 tool names are delete or revoke operations, including mittwald_app_uninstall, mittwald_backup_delete, mittwald_container_delete and mittwald_project_delete. mittwald's own guidance says destructive or cost-impacting changes should be approved explicitly, and that the agent should be treated as an operator rather than an unattended process.
No. mittwald states the connector never opens shells, tunnels or file transfers itself, and that SSH access comes back as a command for you to run locally. The mittwald REST API publishes no SSH session endpoint at all, only SSH user management, which is consistent with the tool returning connection details rather than a session.
The refresh token flow is failing. mittwald's re-auth guide lists repeated browser logins and invalid_token errors as symptoms of expired or revoked tokens. Its recovery order is to confirm the server configuration in your client, run an explicit re-login, retry a read-only call first, then resume the interrupted workflow from the step that failed.
Start with the four read scopes mittwald recommends: user:read, customer:read, project:read and app:read. The vendor advises requesting the smallest set that fits your task. Those same four are the default scopes the server publishes in its own OAuth descriptor, out of 46 scopes it supports in total across apps, backups, databases, domains, mail and more.
Sources
- mittwald MCP integration documentation (fetched 2026-09-08) · retrieved 2026-09-08
- mittwald MCP landing page (fetched 2026-09-08) · retrieved 2026-09-08
- Getting Connected to mittwald MCP, including the OAuth vs API token comparison, scope list and FAQ (fetched 2026-09-08) · retrieved 2026-09-08
- Getting Started with Claude Code, including prerequisites, troubleshooting and vendor FAQ (fetched 2026-09-08) · retrieved 2026-09-08
- Re-auth troubleshooting and recovery (fetched 2026-09-08) · retrieved 2026-09-08
- OAuth consent and refresh behaviour (fetched 2026-09-08) · retrieved 2026-09-08
- Backup restore incident runbook (fetched 2026-09-08) · retrieved 2026-09-08
- SSH key self-management and project bootstrap playbooks — and (fetched 2026-09-08) · retrieved 2026-09-08
- Session security review playbook (fetched 2026-09-08) · retrieved 2026-09-08
- mittwald OAuth protected-resource descriptor, RFC 9728 — 46 scopes, four default scopes (fetched 2026-09-08). The path-suffixed form returns the same document. · retrieved 2026-09-08
- mittwald OAuth authorization-server metadata — PKCE
S256, dynamic client registration (fetched 2026-09-08) · retrieved 2026-09-08 - Anonymous
initializeprobe againsthttps://mcp.mittwald.de/mcp— HTTP 401 withWWW-Authenticate: Bearer realm="MCP Server"and a JSON OAuth challenge (2026-09-08). No tool was called and no authentication was attempted. · retrieved 2026-09-08 - Sibling-endpoint probe —
/mcp/readonly,/readonly/mcp,/mcp/ro,/mcp/readwrite,/v1/mcp,/mcp/sse,/messagesall 404; server root lists only/mcpand/health(2026-09-08) · retrieved 2026-09-08 - mittwald OpenAPI specification — rate limiting, authentication, 515 paths (fetched 2026-09-08;
/openapiis a 301 to this path) · retrieved 2026-09-08 - mittwald CLI command reference for
mw app sshandmw ssh-user(fetched 2026-09-08) · retrieved 2026-09-08 - Anthropic Connectors Directory entry (fetched 2026-09-08) · retrieved 2026-09-08
developer.mittwald.depublishes norobots.txtand nollms.txt(both HTTP 404, 2026-09-08), so no crawl policy orContent-Signalwas available to read. Pages were reached from the host's ownsitemap.xml. · retrieved 2026-09-08
Server Info
- Category
- Developer Tools
- Developer
- mittwald
- Tools
- 116
- Domain
- mcp.mittwald.de
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.
Similar MCP Servers for Developer Tools
Related Resources
Ready to connect mittwald?
Connect mittwald once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.