MCP Server Name Generator

Say what your MCP server does and get a valid name under your GitHub or domain namespace, a description within the limit, and a server.json that passes the registry's schema. Check the name against the public MCP registry before you publish.

      The check asks the public MCP registry about this one name, only when you press it.

      How an MCP Server Name Works

      The download button stays off until every field passes the schema. Add your packages or remote URL to the file before you publish it with mcp-publisher.

      FAQ

      What is server.json?

      It is the file that describes an MCP server to the MCP registry: its name, description, version and how to install or reach it. The registry's schema sets the rules for each field.

      What should my MCP server's name be?

      Your namespace, a slash and a short name for what the server does: io.github.your-username/weather-forecasts, or com.yourdomain/weather-forecasts if you verify your domain. Keep the part after the slash to the job it does, in lowercase words joined by hyphens.

      How long can the description be?

      Up to 100 characters, and it should describe what the server can do rather than how it is built.

      Does the check tell me the name is free?

      It searches the public MCP registry for the name you typed and tells you whether a server already uses it there. The registry also ties namespaces to accounts, so only you can publish under your own GitHub or verified domain namespace.

      Is what I type sent anywhere?

      Only when you press Check the MCP registry: then the server name goes to the public registry's search. Building and downloading the file happens in your browser.