MCP server setup
Connect DomainCare to Claude, Cursor, and other AI tools using the Model Context Protocol (MCP) server.
MCP server setup
The DomainCare MCP server lets AI assistants interact with your DomainCare account through the Model Context Protocol. List domains, trigger rechecks, manage status pages, view events, and more — all from Claude, Cursor, or any MCP-compatible tool. Published on npm as domaincare-mcp.
Prerequisites
- A DomainCare account with an active paid plan
- An API key (create one at Settings > API Keys)
- Node.js 18 or later
Install
npm install -g domaincare-mcpOr use npx without installing:
npx domaincare-mcpConfigure
Claude Desktop
Add to your claude_desktop_config.json:
{
"mcpServers": {
"domaincare": {
"command": "npx",
"args": ["-y", "domaincare-mcp"],
"env": {
"DOMAINCARE_API_KEY": "dc_your_key_here"
}
}
}
}Config file location:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json
Claude Code
Add to your project's .claude/settings.json or global ~/.claude/settings.json:
{
"mcpServers": {
"domaincare": {
"command": "npx",
"args": ["-y", "domaincare-mcp"],
"env": {
"DOMAINCARE_API_KEY": "dc_your_key_here"
}
}
}
}Cursor
Open Settings > MCP Servers > Add Server and enter:
- Name:
domaincare - Command:
npx -y domaincare-mcp - Environment:
DOMAINCARE_API_KEY=dc_your_key_here
Available tools
Once connected, your AI assistant has access to these tools:
| Tool | Description | Minimum scope |
|---|---|---|
list_domains | List domains with pagination and status filter | Read |
get_domain | Get details for a single domain | Read |
get_checks | Get latest check results per check type | Read |
list_events | View events for a domain with severity and type filters | Read |
add_domain | Add a new domain to your account | Write |
trigger_recheck | Trigger an immediate check sweep for a domain | Write |
update_domain | Enable/disable specific checks for a domain | Write |
get_check_overrides | Get per-check settings: mute, interval, event toggles, severity overrides | Read |
update_check_overrides | Update per-check overrides (partial update, paired events enforced) | Write |
reset_check_overrides | Reset per-check overrides to defaults | Full |
delete_domain | Remove a domain (soft-delete) | Full |
list_status_pages | List all status pages in your organization | Read |
get_status_page | Get details for a single status page | Read |
create_status_page | Create a status page linked to a domain | Write |
update_status_page | Update a status page's slug or title | Write |
delete_status_page | Delete a status page (soft-delete) | Full |
Recommended scope
For most MCP setups, create a Read only API key. This lets your AI assistant query domains, events, and check results without the ability to modify your account.
If you need the AI to add domains, use a Read + Write key. Only use Full access if you specifically need the delete_domain tool — a full-access key lets the AI assistant remove domains from your account.
Verify it works
After configuring, ask your AI assistant:
"List my DomainCare domains"
You should see your domains returned. If you get an authentication error, verify your API key is correct and your subscription is active.
Environment variables
| Variable | Required | Description |
|---|---|---|
DOMAINCARE_API_KEY | Yes | Your API key from Settings > API Keys |
DOMAINCARE_API_URL | No | Override the API base URL (default: https://domaincare.io/api/v1) |
Troubleshooting
"DOMAINCARE_API_KEY is required" — The server could not find your API key. Make sure the env block in your MCP configuration includes the key.
401 errors — Your API key may be expired or revoked. Create a new key at Settings > API Keys.
403 errors — API access requires a paid plan. Free trial accounts cannot use the API or MCP server.
Tool not showing up — Restart your AI tool after changing the MCP configuration. Some tools require a full restart to pick up new servers.