Skip to main content
Glama
johnsorrentino

MCP Namecheap Server

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
NAMECHEAP_API_KEYYesYour Namecheap API key
NAMECHEAP_SANDBOXNoSet to 'true' to use Namecheap's sandbox environment for testing
NAMECHEAP_API_USERYesYour Namecheap API username
NAMECHEAP_USERNAMEYesYour Namecheap account username
NAMECHEAP_CLIENT_IPYesYour whitelisted IP address
NAMECHEAP_ENABLE_CHECKNoEnable domain availability checking (default: true)true
NAMECHEAP_ENABLE_GETLISTNoEnable domain list retrieval (default: true)true
NAMECHEAP_ENABLE_SETCUSTOMNoEnable custom DNS configuration (default: true)true

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
namecheap_get_domain_listB

Get a list of all domains in your Namecheap account

namecheap_check_domain_availabilityC

Check the availability of one or more domains

namecheap_set_custom_dnsC

Set custom DNS nameservers for a domain

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.2/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a clearly distinct purpose with no overlap: checking domain availability, listing owned domains, and setting DNS nameservers. The descriptions clearly differentiate these three separate operations in the domain management workflow.

Naming Consistency5/5

All three tools follow a perfect namecheap_verb_noun pattern with consistent snake_case formatting. The naming convention is predictable and readable throughout the entire tool set.

Tool Count3/5

With only 3 tools, this server feels somewhat thin for a comprehensive domain management system. While the tools cover core operations, typical domain management would include additional functionality like domain registration, renewal, transfer, or contact management.

Completeness2/5

There are significant gaps in the domain management lifecycle. The server lacks essential operations like registering a domain after checking availability, renewing domains, transferring domains, or managing domain contacts/settings beyond DNS. This creates dead ends in typical domain management workflows.

Maintenance

ActivityInactive
ResponsivenessNo issues