Namemyapp MCP Server

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 11 min ago.

claude mcp add namemyapp --transport http https://mcp.namemy.app/mcp

{
  "mcpServers": {
    "namemyapp": {
      "url": "https://mcp.namemy.app/mcp"
    }
  }
}

[mcp_servers.namemyapp]
url = "https://mcp.namemy.app/mcp"

{
  "mcpServers": {
    "namemyapp": {
      "url": "https://mcp.namemy.app/mcp"
    }
  }
}

{
  "mcpServers": {
    "namemyapp": {
      "url": "https://mcp.namemy.app/mcp"
    }
  }
}

This one needs environment variables set before it will start: NAMEMYAPP_API_KEY (Optional. Get a free key at https://namemy.app/app/api-keys.), NAMEMYAPP_AGENT_SOURCE (Attribution tag (e.g. 'claude-desktop'). Default 'mcp'.). The author declared them in the registry entry; get the values from the project itself.

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

This server publishes 1 more address. The block above uses the one we reach during checks; the full list is under Endpoints below, and the author may intend a particular one for your client.

Available tools 13

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

Endpoints