hostinger-dns-delete-schema-gap

Hostinger MCP DNS_deleteDNSRecordsV1 — Schema Gap Workaround

The DNS_deleteDNSRecordsV1 MCP tool schema only exposes domain as a parameter, but the Hostinger API requires a filters field (array of {name, type} objects). The tool returns "The filters field is required" when called without it.

Workaround: Call the MCP HTTP endpoint directly via curl with JSON-RPC tools/call payload, passing filters in arguments:

curl -X POST <mcp-server-url>/ \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"DNS_deleteDNSRecordsV1","arguments":{"domain":"arjtech.in","filters":[{"name":"record-name","type":"A"}]}}}'

The MCP server URL is in ~/.claude.json under mcpServers.hostinger-admin.url. Auth is handled internally by the Railway-hosted server.

Related

• gws-capability-expansion-nova (archived)
• mid-session-claude-mcp-add-s-project-doesn-t-load-tools
• claude-code-to-nova-enterprise-backup-v3-2026-03-25 (archived)
• enterprise-capability-expansion-5-pillars-from-digital-employee-analysis
• notebooklm-mcp-integration-pattern
• mcp-streamable-http-requires-sse-handshake
• hostinger-mcp-dnsdeletednsrecordsv1-schema-missing-required
• hostinger-mcp-dns-delete-tool-schema-bug-json-rpc-bypass