API & MCPA CDN API, and an MCP server for your AI assistant.
Everything you can do in the panel is a documented REST endpoint. Create a scoped key and script it, or connect Claude or Cursor to the hosted MCP server and ask in plain language.
REST API with scoped keys
Manage domains, DNS records, cache, rules, SSL and analytics over HTTPS. Keys can be read-only, so a dashboard or a monitoring job never holds more access than it needs.
- One documented OpenAPI reference
- Read-only and read-write API keys
- Batch calls, such as 1,000 DNS records at once
Hosted MCP server
The MCP endpoint is https://api.nsin.ir/mcp over Streamable HTTP, authenticated with your API key. There is nothing to install. A read-only key is shown only the tools that read.
- Works with Claude Code, Claude Desktop and Cursor
- Purge cache or change a rule in plain language
- Risky tools are marked so the client can ask first
Ready-made integrations
An agent skill teaches coding agents how to use nsin. The acme.sh plugin answers DNS-01 challenges through the API. Team sharing gives colleagues access with roles instead of a shared password.
- Agent skill for Claude, Cursor and more
- acme.sh DNS-01 integration
- Team access with roles
Frequently asked questions
Can I manage nsin entirely from code?
Yes. Everything in the panel is a REST endpoint, authenticated with an API key you create in the panel.
What is the MCP server for?
It lets an AI assistant such as Claude or Cursor call nsin for you: list domains, read analytics, purge cache or edit DNS records, from a sentence you type.
Is it safe to give an AI assistant a key?
Use a read-only key when the assistant only needs to look. Write tools are never shown to a read-only key.
Can I issue certificates with acme.sh?
Yes. The nsin DNS plugin for acme.sh creates the DNS-01 challenge records through the API.