API & MCP › Cursor
Use DNSai in Cursor
Add DNSai to Cursor's MCP config (global or per-project) and the lookup tools load in Agent mode.
✓ Free key works — passed as a headerAny Cursor plan · one domain per request
↓ Download this guide (.md) drop it into your repo or paste it into your assistant
Set it up
Add the server
Edit ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project). Prefer ${env:DNSAI_MCP_TOKEN} over a literal token so the key isn't committed.
{
"mcpServers": {
"dnsai": {
"url": "https://mcp.dnsai.com/mcp",
"headers": { "Authorization": "Bearer ${env:DNSAI_MCP_TOKEN}" }
}
}
}
Your key. Cursor supports a header, so the free key works directly. Get a free key, set it as
DNSAI_MCP_TOKEN, and you're at 100/day. Omit the headers block to run anonymously (25/day). Verify it works
In Cursor Agent, ask:
Use dnsai to look up the MX records for github.com
Every result ends with a plain-English summary, a source link on dnsai.com, and your remaining quota.
Troubleshooting
- Remote (Streamable-HTTP) servers use the
urlfield — notcommand. There's also a one-clickcursor://deeplink; if you publish one, encode it without a real token so the secret doesn't leak.
Sources: Cursor MCP docs
Need bulk, multi-domain, or the full API?
Pro unlocks bulk / multi-domain lookups; Enterprise adds large-scale scanning and the full programmatic API.
See plans & pricing →