dynu-mcp

MCP server for Dynu — a Dynamic DNS, domain registration, email hosting, and cloud compute (VPS) provider. Exposes the full public Dynu REST API v2 as MCP tools.

MSPbots Connector

The MCP Gateway built for MSPs: visible, controlled, and your data stays where it belongs.

Get started at connect.mspbots.ai →

MSPbots Connector gives your AI clients one MCP URL to reach your entire MSP stack (RMM, PSA, documentation, security, finance), and gives you control over who can call which tool and a record of everything that was called.

Hosted service: connect.mspbots.ai · Free to use.

Why Connector

Quick start

1. Sign up at connect.mspbots.ai.

2. Connect your vendors. Pick from 150+ connectors and authorize each one on the vendor's own page, or bring your own API keys. No extra vendor accounts needed.

3. Set access. Create roles and decide which tools each role may call. Nothing is allowed until you allow it.

4. Add your MCP URL to your AI client. Copy the URL from your Connector dashboard into Claude, ChatGPT, Cursor, VS Code, Gemini, Codex, or any MCP-capable client.

5. Ask your AI to do real work, and watch every call appear in the audit log.

Features

Unified gateway

• One MCP URL for all your AI clients

• 150+ connectors across the MSP stack

• Custom MCP servers supported, free

• Authorization happens on each vendor's own page; the AI never sees passwords or tokens

• Bring your own credentials: use the vendor API keys you already have

• Multiple accounts per app; connect once, reuse across AI clients

• Tool search: finds the right action for the task

• One sign-in; vendor credentials are injected behind the scenes and OAuth tokens refresh automatically

Visibility

• Audit log for every tool call (who, which vendor, when)

• Usage dashboard: call volume, top vendors, error rate, per-user activity

• Export audit logs to CSV, or stream to Loki, Graylog, or LogScale (SIEM)

• Optional recording of tool arguments and result summaries (off by default, enabled per organization)

Control

• Per-role, per-tool allowlist, deny by default

• owner / admin / member roles

• SCIM provisioning with Entra ID, Okta, JumpCloud, and Google Workspace

Security

• Credentials encrypted one record at a time (AES-256-GCM, per-record key)

• AI clients authenticate with OAuth 2.1 + PKCE

• Vendor responses are scanned for prompt-injection patterns and returned as structured data. This is one layer of defense, not a guarantee against every attack.

• Static egress IP for customer firewall and API allowlisting

Pricing

Free.

Links: connect.mspbots.ai · mspbots.ai

Related MCP server: dynadot-mcp

Overview

• Stateless HTTP service. No credentials are ever persisted — each request supplies its own API key via a header, used only for the lifetime of that single request.

• Supports concurrent requests; per-request credential isolation is done via Python contextvars, not a global/shared client instance.

• Entry points: POST /mcp (MCP protocol) and GET /health (health check).

• Default port: 8080 (configurable via MCP_HTTP_PORT).

Scope

30 tools, trimmed down from an initial 117-tool build covering Dynu's full OpenAPI 3.0 spec. The platform this MCP runs behind aggregates every enabled vendor MCP's tools into a single Gemini/Vertex model call, which caps out at 512 total function declarations — with 50+ vendor MCPs registered, each one needs to stay lean. Kept, across the same 6 categories: dns (8 — MSPbots' real GET /dns endpoint plus core record/service CRUD), email (7 — service list/detail, account create/read/update/delete), compute (4 — instance list/detail/start/stop), domain (2 — list/detail), monitor (7, full category), ping (2, full category). Cut entirely: domain registration administration (glue records, name servers, auto-renewal, lock/unlock), email's blacklist/whitelist/alias/distribution-list/DKIM management, and compute's backup/snapshot/VNC/reinstall operations — see Known Gaps. MSPbots itself only calls 1 endpoint (GET /dns), which is kept.

Authentication

Dynu authenticates with a single static API key (found in the API Credentials area of the Dynu control panel). MSPbots' own integration convention sends this key as the raw value of the API-Key header, and this server forwards it exactly that way.

HEADER Authorization Parameters

Missing the header returns 401:

{
  "error": "Missing credentials",
  "message": "This server requires the X-Dynu-Api-Key header",
  "required_headers": ["X-Dynu-Api-Key"],
  "optional_headers": []
}

Environment Variables

MCP Endpoint

• POST /mcp — MCP protocol (streamable HTTP transport)

• GET /health — health check, returns {"status": "ok"} (pure local liveness probe, does not depend on the Dynu API)

Tool List

Tool names are derived from each operation's own summary in the vendor's OpenAPI spec (e.g. "Get a list of domains for DNS service" → dynu_get_list_domains_dns_service); the one naming collision (both GET /ping and POST /ping share an identical summary) is disambiguated with a _get/_post suffix. body parameters for POST operations are accepted as a generic dict — see the vendor's OpenAPI spec's Models section (linked below) for the exact field names/types of each resource.

Test Example

# Health check
curl -s http://localhost:8080/health

# Call a tool via the MCP protocol (streamable HTTP) — requires an
# initialize handshake first per the MCP spec; abbreviated example below
# shows the tool-call request body only:
curl -s -X POST http://localhost:8080/mcp   -H "X-Dynu-Api-Key: <your-dynu-api-key>"   -H "Content-Type: application/json"   -H "Accept: application/json, text/event-stream"   -H "mcp-session-id: <session-id-from-initialize>"   -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "tools/call",
    "params": {
      "name": "dynu_get_list_domains_dns_service",
      "arguments": {}
    }
  }'

Live-verified (2026-07-29): dynu_get_list_domains_dns_service (the same endpoint MSPbots itself calls, zero parameters) was called end-to-end through this running server with a real API key and returned real DNS domain records for the account.

API Reference

• Overview: https://www.dynu.com/Support/API

• Official OpenAPI 3.0 spec (Swagger): https://www.dynu.com/files/dynu.api/Dynu.API.OAS.zip

Known Gaps

• Trimmed from 117 to 30 tools, by explicit user decision: the platform this MCP runs behind aggregates every enabled vendor MCP's tools into a single Gemini/Vertex model call, which caps at 512 total function declarations — with 50+ vendor MCPs registered, each needs to stay lean. Kept: MSPbots' real GET /dns endpoint, core DNS record/service CRUD (8), core email service/account CRUD (7), basic compute instance list/detail/start/stop (4), domain list/detail (2), and Monitor/Ping in full (9). Cut entirely: domain registrar administration (glue records, nameservers, auto-renewal, lock/unlock/cancel), email's blacklist/whitelist/alias/distribution-list/DKIM management, and compute's backup/snapshot/VNC/reinstall/password-change operations. Any of these can be re-added on request if a real use case needs them.

• Compute and domain write operations remain higher-stakes even after trimming — dynu_start_instance/dynu_stop_suspend_instance act on real VPS instances. Treat these as destructive/irreversible and confirm with a human before invoking.

• body parameters are untyped (dict) rather than fully modeled — the OpenAPI spec's Models section defines the exact schema per resource (e.g. DNS.dnsRecordA), but reproducing all of them as typed Python parameters was out of scope. Callers should shape the body dict per the linked spec.

• Only dynu_get_list_domains_dns_service (MSPbots' own endpoint) was live-verified with real account data. The remaining 29 tools are structurally correct (schema validated, MCP-protocol tools/list confirmed, tool count re-verified after trimming) but not individually smoke-tested — several are write/destructive operations that would create, modify, or delete real DNS records, email accounts, or VPS instances, so they weren't exercised against the live test account.