VS Code · Zed · Cline · Roo · Continue · JetBrains · Amazon Q · Goose · MCP with API key
DNSai for other MCP clients
DNSai is a standard remote MCP server over Streamable HTTP. Any client that can send an Authorization header can use it; here are working settings for Zed, Cline, Roo Code, Continue, JetBrains AI Assistant, Amazon Q Developer / Kiro and Goose.
What you can ask Other MCP clients
Example answers use made-up domains.
“What does northwind.example use for email and DNS?”
Connect in 3 steps (about 3 minutes)
- Create a DNSai API key.
- Add the DNSai URL with an "Authorization: Bearer" header in your client's MCP settings.
- Ask your assistant about your domains.
Signed-in Enterprise customers get the exact click-by-click steps and ready-to-paste configuration for Other MCP clients, a one-click API key for it, and a live connection check.
Other MCP clients requirements: An MCP client with Streamable HTTP and custom headers. DNSai Enterprise plan.
Security
- Other MCP clients sends an API key in the Authorization header. Use an expiring key made for Other MCP clients and keep it in an environment variable.
- Account and organization owners can make API keys and assistants read-only, so they can read your data but never change it or start scans.
- Starting a credit-spending Deep Scan always needs an estimate and your explicit confirmation.
- DNSai data comes from public DNS and web records. Your watchlists, notes and tags stay private to your account and are only shared with an AI tool you connect yourself.
Connect Other MCP clients to DNSai
The API and AI connectors are included with DNSai Enterprise plans. Every member of your organization shares one set of limits, and every call counts from the first one.
Other integrations
Last checked 2026-10-29.