Skip to content
domainspacesi

Manage your .si domains from an AI agent

DomainSpace runs an MCP (Model Context Protocol) server. After you create an access token in your dashboard, an AI agent can check domain availability, read your domains and orders and edit DNS records for you.

What an agent can do

A person always pays

No tool charges anything. When an agent prepares a registration or renewal it only gets a link. You open it while logged in, check the registrant details, accept the terms and the withdrawal-waiver consent, and pay by card on the Stripe page. The agent cannot give that consent for you and never sees your card details.

Tools

ToolPermissionWhat it does
check_domainreadAvailability and first-year price of a .si name.
list_domainsreadYour domains with expiry date and renewal state.
get_domainreadDetails of one of your domains.
list_dns_recordsreadThe DNS records of one of your domains.
add_dns_recorddns:writeAdd a DNS record (same validation as the dashboard).
delete_dns_recorddns:writeDelete a DNS record.
start_registrationpurchaseCheck a name and return the checkout link for you to open. Buys nothing.
start_renewalpurchaseReturn the dashboard link where you renew a domain, while renewal is open. Buys nothing.
list_ordersreadYour recent orders and their status.
get_orderreadThe status of one order, to follow it until the domain is registered.

Permissions

Each token has one or more permissions. A tool call without the right permission fails with a message that names it. Choose only what the agent needs.

Set up

  1. Log in (or sign up) and open API access in your dashboard.
  2. Create a token with the permissions you want. Copy it right away: it is shown only once.
  3. Add the server to your agent, for example with the command below.

Claude Code

claude mcp add --transport http domainspace https://domainspace.si/mcp --header "Authorization: Bearer dsp_YOUR_TOKEN"

Other clients

{
  "mcpServers": {
    "domainspace": {
      "type": "http",
      "url": "https://domainspace.si/mcp",
      "headers": {
        "Authorization": "Bearer dsp_YOUR_TOKEN"
      }
    }
  }
}

Clients that connect to remote MCP servers over HTTP and allow custom headers accept a configuration like this; the key names vary, so check your client's documentation. Replace the placeholder with your token.

We have tested the server with the official MCP TypeScript SDK client over Streamable HTTP. Other clients should work if they support that transport and custom headers. Signing in with OAuth is not supported yet: use a token.

Safety

Create a tokenNo account yet? Sign up