An MCP server needs three names, not one: the package people install, the tool prefix agents see in every call, and the domain that hosts docs and config. The reliable pattern is a short lowercase stem that survives all three, -mcp on the package, and .dev for docs or .io for an API-first service.
Why an MCP server needs three names, not one
The package name is what runs in a client config: npx pgshim-mcp. The tool prefix is what the model reads when it decides what to call: pgshim_query, pgshim_schema. The domain is what a developer opens when the server fails at 2 a.m. and the README is suddenly the most important document in the project.
Most naming advice optimizes the first one and forgets the other two. That is why half the MCP servers in the wild have a decent npm package and a tool namespace that collides with every other database server on the client.
The official registry adds a fourth surface: names are published in reverse-DNS form, such as io.github.username/server-name. The registry name does not have to match the npm package, but it should share the same stem. Otherwise nobody can connect the package they installed to the server they approved.
The package name: -mcp vs mcp-
Use the suffix. foo-mcp reads as one server; mcp-foo reads as one item in a family of MCP tools, which is a promise you may not want to keep. The suffix also sorts next to related packages in npm search and survives the moment you add a second server.
Keep the stem short enough to type in a config file and specific enough to search. Two real words joined without a hyphen beat a three-word description. Check npm, PyPI, and crates.io before you commit, because a great domain with a taken package name forces an awkward alias. The naming styles in our domain name ideas guide apply here: command-style and tool-style stems age better than puns.
The tool prefix: the name agents actually read
Every tool a server exposes should share one stable prefix. If the stem is pgshim, the tools are pgshim_query, pgshim_schema, and pgshim_explain. Do not prefix with mcp_. The protocol is already implied by the connection, and the extra token appears in every tool call the model reasons about.
The prefix is also the collision boundary. Two servers that both expose query will confuse a client with several of them installed. A stem that describes the data source, not the protocol, keeps the namespace readable.
The domain: .dev vs .io vs .app
Pick the domain by the server's first public job. Documentation and installation instructions point at .dev, which requires HTTPS and is preloaded in browsers, so it behaves like a technical default. An API-first server with a dashboard or pricing page fits .io. A hosted interface that a non-developer might open fits .app.
The rest of the set has narrower uses. .sh works when the server ships with a CLI wrapper or an install script. .co is the short stand-in for a company site. .xyz is the budget choice for an experiment that may not survive the week. The pricing and credibility trade-offs are compared in our best TLDs for developers guide.
10 real name + domain pairs for a Postgres MCP server
I ran the namebox generator for an MCP server that wraps a Postgres database, using the tool and command philosophies. These are names it returned. I checked each one against the registry via RDAP at the time of writing. Availability changes, so verify before you register.
pgshim.io— pg + shim, a thin compatibility layer. Five letters plus the TLD, easy to paste into a client config. Register pgshim.ioquerygate.app— query + gate. Reads as the endpoint that controls database access, and.appsignals a usable interface. Register querygate.approwbridge.co— row + bridge. Bridges table rows to MCP clients;.coreads as a serious short alternative to.com. Register rowbridge.coschemawire.dev— schema + wire. Suggests live introspection, which is the part of a database server developers actually trust. The.devTLD fits a docs-first project. Register schemawire.devpgfetch.app— pg + fetch, a single action. Short enough to read as a command and clear enough to explain itself. Register pgfetch.apppgrelay.sh— pg + relay. Works if the server ships with a CLI wrapper or an install script, which is exactly what.shpromises. Register pgrelay.shmcpq.dev— MCP plus query, clipped to four letters. A strong config alias; the.devsite holds the setup docs. Register mcpq.devpgdrv.co— Postgres driver, clipped. The.coTLD suits a startup-facing landing page more than a long technical path. Register pgdrv.cosqlmcp.app— SQL + MCP with nothing hidden. The safest pick if search discoverability matters more than brand. It says what it does before anyone opens it. Register sqlmcp.apppgsrv.xyz— Postgres server, clipped. The.xyzTLD is the budget option for a weekend experiment that might grow into something real. Register pgsrv.xyz
Pre-publish checklist
- Search the stem on npm, PyPI, crates.io, and GitHub before you commit.
- Confirm the tool prefix does not collide with a server your users already run.
- Register the domain before the announcement, not after the first spike.
- Match the reverse-DNS registry name to the package stem.
- Run a basic trademark search in your target market. A domain is not a trademark.
- Point the README, the registry entry, and the install command at the same name.
Next steps
- Domain name ideas for your next project — the naming styles behind the pairs above.
- Best TLDs for developers — how .dev, .io, .app, .co, .sh, and .xyz compare.
- Generate MCP server name ideas — describe the server, get 12 candidates checked against the registry.