@namemyapp/mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NAMEMYAPP_API_KEY | No | Bearer token for authed mode. Get a free key at https://namemy.app/app/api-keys. | |
| NAMEMYAPP_API_URL | No | Override for staging / self-hosted. | https://namemy.app |
| NAMEMYAPP_AGENT_SOURCE | No | Attribution tag stamped on every API call + buyUrl. | mcp |
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
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| buy_linkA | Build a one-click purchase URL the user can open to buy a domain on namemy.app. Always available (works without an API key). Use this when the user has decided on a name they like — hand them the URL and they sign up + pay in their browser. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
Only one tool exists, so there is no possibility of confusion between tools.
With a single tool, naming consistency is inherent; no conflicts arise.
A single tool feels thin for domain purchasing; ideally additional tools like search or check would be present, but the tool serves a specific purpose.
Only the purchase link generation is provided, missing essential operations like domain search, availability check, or management, leaving the surface incomplete.