Anysphere · MCP with API key

DNSai for Cursor

Add DNSai to Cursor and its agent can look up DNS records, email security and DNS change history while it edits your code or infrastructure.

What you can ask Cursor

Example answers use made-up domains.

“Does our new email provider need DNS changes for proseware.example?”

Yes: MX still points at Google, and SPF lacks the new provider's include. Here is the diff for your DNS file.

Connect in 3 steps (about 2 minutes)

Create a DNSai API key and set it as DNSAI_API_KEY.
Add DNSai to ~/.cursor/mcp.json (or the project's .cursor/mcp.json).
Enable it in Cursor Settings > MCP and ask Agent about your domains.

Signed-in Enterprise customers get the exact click-by-click steps and ready-to-paste configuration for Cursor, a one-click API key for it, and a live connection check.

Cursor requirements: Cursor. DNSai Enterprise plan.

Security

Cursor sends an API key in the Authorization header. Use an expiring key made for Cursor 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 Cursor 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.