Product Updates

Inside the OSIR MCP Server: 100 Tools for AI-Native Domain Management

2026-06-08 · Name.al Team

Your AI Assistant, Meet Your Registrar

Most "AI" features in this industry are a chat box bolted onto a dashboard. OSIR is built the other way around: a native Model Context Protocol (MCP) server that exposes the real registrar to any AI assistant. Connect it once, and Claude, ChatGPT, Cursor, or your own agent can search, register, transfer, and configure domains, DNS, VPS, and billing through natural language - using the same operations as the dashboard and the REST API.

This post is the complete tour: how to connect it, all 100 tools grouped by what they do, and what that unlocks.

What is MCP?

MCP (Model Context Protocol) is an open standard that connects AI assistants to external tools and data. An MCP server publishes a set of callable tools; any MCP client discovers and invokes them automatically. There is no SDK to install and no glue code to write - the assistant reads the tool list and calls what it needs.

Connect OSIR to Claude in Under a Minute

You do not need a config file. Add OSIR as a custom connector:

1. In Claude, open Customize and go to Connectors.
2. Click +, then Add custom connector.
3. Set Name to OSIR.
4. Set the Remote MCP server URL to https://be.osir.com/mcp/http.
5. Save, then authenticate with your OSIR account when prompted.

That is it. The same remote MCP server URL works in any MCP client that supports a remote (streamable HTTP) server.

All 100 Tools, by Category

The server exposes 100 tools across 10 categories. You never call these by name - your assistant picks the right one - but seeing the full surface area shows how much is actually possible.

Domains and transfers (23)

The core of the registrar: search, register, renew, transfer, and configure.

checkDomainAvailability, checkKeywordAvailability, checkKeywordAvailabilitySummary, validateDomainName, registerDomain, renewDomain, transferDomain, initiateTransfer, cancelTransfer, getTransferQuote, getTransferStatus, listPendingTransfers, lockDomain, unlockDomain, updateDomainAutoRenew, updateDomainPrivacy, updateNameservers, getDomainInfo, getDomainPricing, getDomainExtensions, getDomainAuditTrail, listUserDomains, listCategorizedTlds

Domain name suggestions (6)

Turn a rough idea into a shortlist of brandable, available names.

generateDomainSuggestions, bulkDomainSuggestions, suggestAlternatives, addPrefixToDomain, addSuffixToDomain, spinDomainWords

DNS (6)

Full record management plus zone setup.

createDnsRecord, getDnsRecord, listDnsRecords, updateDnsRecord, deleteDnsRecord, initializeDnsZone

Nameserver hosts (4)

Register and manage host (glue) records for custom nameservers.

checkHostAvailability, createHost, getHostsForDomain, deleteHost

Contacts (6)

Manage the registrant, admin, and technical contacts ICANN requires.

createContact, getContact, listContacts, updateContact, deleteContact, getContactsForDomain

VPS and servers (16)

Order a server, install an operating system on it, manage the SSH keys you log in with, and browse dedicated hardware.

orderVps, buildVpsInstance, listVpsOsTemplates, listVpsPackages, getVpsPackageDetails, listVpsLocations, listMyVpsInstances, countMyVpsInstances, getVpsInstanceDetails, deleteVpsInstance, changeVpsPaymentTerm, loginToVpsPanel, addSshKey, listMySshKeys, deleteSshKey, getDedicatedServerCatalog

Ordering and building are two separate things. orderVps allocates the server; installing an operating system on it is a second operation. The normal path passes an OS image from listVpsOsTemplates and a key from addSshKey straight into orderVps, so the build starts with the order and you get a ready machine. Order without naming an OS and you get a real, paid server sitting unbuilt.

buildVpsInstance is the reinstall and recovery path, and it matters because of an asymmetry worth remembering: rebuilding is free and retryable forever, while re-ordering spends money and strands the first server. If a build fails, always build again rather than buying a second box.

Apps and hosting (10)

Deploy and operate apps: upload a bundle, deploy it, watch status and logs, set secrets, and provision a managed database.

osirAppCreateUpload, osirAppDeploy, osirAppList, osirAppStatus, osirAppLogs, osirAppSetSecret, osirAppProvisionDatabase, osirAppDelete, osirAppMoveToOwned, osirAppGetSource

Email hosting (11)

Enable email on a domain, verify the DNS, and create and manage mailboxes.

listMailPlans, getMailboxQuote, enableMailDomain, listMailDomains, getMailDnsRecords, verifyMailDns, createMailbox, listMailboxes, setMailboxPassword, deleteMailbox, getMailboxUsage

Enabling a domain for email is free; mailboxes are the paid product. When the domain runs on OSIR nameservers the required DNS records are published automatically; otherwise the assistant hands you the records and verifies them with verifyMailDns. Creating a mailbox goes through a quote and the confirmation gate, and the generated password is returned exactly once - store it when you see it.

Billing and payments (8)

Check balance, review invoices, preview fees before you commit, and pay.

getAccountBalance, listInvoices, getInvoiceDetails, getInvoiceStatistics, payInvoice, createPaymentSession, previewPaymentFees, getPaymentTransactions

Account and platform (10)

Profile, authentication, audit logs, and safe execution of confirmed actions.

getMyProfile, getAccountSummary, getAuthStatus, loginWithDevice, checkDeviceLoginStatus, logout, getMyAuditLogs, getRecentActivity, getProductCatalog, executeConfirmedAction

Not Just Tools: 10 Built-in Prompts

Alongside the 100 tools, the server ships 10 guided prompts. A prompt is a reusable, server-supplied workflow the assistant can pull in when a question needs more than a single call - it carries the domain expertise so you do not have to supply it.

The clearest example is dns_setup_guide. Ask "how do I set up DNS for a website?" and the assistant can load that prompt to get the record types, a worked website example, and the email configuration, instead of improvising an answer from general knowledge. Prompts appear in most MCP clients under a slash-command or attachment menu, separately from the tool list.

What It Looks Like in Practice

Because the tools cover the whole platform, you can describe a goal and let the assistant chain the steps:

• "Is coolstartup.io available, and what would two years with privacy cost?" runs checkDomainAvailability, getDomainPricing, and previewPaymentFees.
• "Register it, turn on auto-renew, and point it at 192.0.2.10." runs registerDomain, updateDomainAutoRenew, and createDnsRecord.
• "Enable email on my domain and create an info@ mailbox." runs enableMailDomain, getMailboxQuote, and createMailbox.
• "Which of my domains expire in the next 30 days, and renew them." runs listUserDomains, then renewDomain for each.

A note on safety: actions that cost money or are hard to reverse go through a confirmation step (executeConfirmedAction), so an assistant proposes and you approve before anything commits.

Beyond a Chat Window: Autonomous Agents

The same capabilities are available to fully autonomous systems over Google's Agent-to-Agent (A2A) protocol. An agent spinning up a new product can register a domain, configure DNS, and provision a server as steps in a larger workflow, with no human clicking through a dashboard. This is the difference between an AI feature and an AI-native registrar.

MCP and A2A are two views of one platform, not two products - both are built on the same shared service layer, so an operation behaves identically whichever way you reach it. Where MCP hands an assistant 100 individual tools, A2A wraps them into 7 specialist agents with 53 skills, coordinated by an orchestrator that plans and runs multi-step work:

The distinction matters when you are choosing an integration. Use MCP when a human is in the loop and an assistant should pick tools conversationally. Use A2A when another agent is the caller and you want to hand over a whole task - "register this name and put it behind a server" - and have the orchestrator sequence it. The agent card is public at https://be.osir.com/.well-known/agent.json.

Try It

Add the connector with https://be.osir.com/mcp/http, then ask your assistant to check a domain. For the full setup guide and the live tool catalog, see the MCP server page. For all four integration paths - MCP, A2A, CLI, and REST - see AI Integration, or dive into the Developer Docs for the complete API reference.

Image by aleksandarlittlewolf on Magnific