Contents

Docs / How-to guides

List a server and publish it to the MCP Registry

Give a server a page at its address and an entry in the MCP Registry, under your own domain.

A listing gives a server two things: a page for people at its address, and an entry in the MCP Registry, which clients and directories read. Listing is free.

On the server's Settings tab, the Listing card says whether it's listed. Choose Set up a listing to open the Listing page.

What a listing needs

Under Before it's listed, the page checks each of these as it is now:

  • Others can connect: the server is public, or open to its API's users. A server only your team can connect to can't be listed. Change access first.
  • A verified publisher: a domain you've proved is yours, as below.
  • Checks pass: the live deploy has no errors. Checks lists what they look for.
  • Live for 30 days: counted from its first production deploy that went live. Until then, the page says the day it can be listed.
  • A support contact: an email address or an https link.
  • A privacy policy: an https link. People see it before they connect.

Neither switch turns on until every one is met.

Official or built on its API

Once the publisher is verified, the list also says how the server is listed. It's Official when the API it calls is on the publisher's domain, like a server that calls api.acme.com published by acme.com. Otherwise it's listed as built on that API, by your domain: a server that calls api.stripe.com, published by acme.com, shows as Built on stripe.com.

Choose the publisher

The publisher is the domain a workspace's listings go out under. There's one per workspace, and every server in it is listed under that domain, so only an owner or admin can choose it.

Under Publisher, Sokie suggests the domain the server's API is on: choose Use acme.com to take it, since a listing there is Official. Or type another under Or another domain and choose Use this domain. Sokie keeps the domain it's registered under, so api.acme.com becomes acme.com.

Then add two TXT records at your DNS provider:

TypeNameValue
TXT_sokie.acme.comsokie-verify= and the code Sokie shows
TXTacme.comv=MCPv1; k=ed25519; p= and the key Sokie shows

The first proves the domain is yours. The second lets Sokie publish to the MCP Registry under it. Most providers add your domain to a name for you, so you type _sokie for the first and @ for the second. Keep the second as a TXT record of its own, even if the domain has others.

Sokie checks every minute for a day after you choose the domain, and stops once both are found. Check now looks right away. When both are in, the card says Both in place. Leave them there: the MCP Registry looks for the second each time Sokie publishes.

To change the publisher, choose Use another domain. A new domain gets new records to add. While any server in the workspace is listed, the publisher can't change: take them out of listings first.

Turn it on

Under Where it's listed, there are two switches.

A page at the server's address lists it. Anyone who opens the address in a browser sees what the server does, who publishes it, what agents may do there, how to sign in and how to add it. Before it's listed, a browser there sees only how to add it.

The MCP Registry publishes it there, under your publisher's domain reversed and the listing's name, like com.acme/invoicing. It turns on once the server is listed and the second record is found. The name stays the same once it's published, even if you rename the listing.

The Registry gets the listing's name, its one line as the description, the server's address as its website, and https://<address>/mcp to connect to. What the MCP Registry gets, beside the form, shows the entry as it will be.

Sokie publishes it again after each production deploy, and when you save a change to what people see. The version comes from the deploy: deploy #58 publishes 1.58.0, and a change saved on the same deploy publishes 1.58.1.

Under the switch, Sokie says how the last publish went: Published, with its version and the deploy it came from, or why the Registry refused it. After a refusal, Publish again tries once more, and the next deploy tries again by itself. If the second record is gone from your domain, add it again: the value is the same.

Take it out of listings

Turn off The MCP Registry and Sokie marks the server's entry deleted in the Registry. The page at its address stays listed.

Turn off A page at the address and the server isn't listed any more. Its Registry entry is marked deleted too.

If Sokie takes a listing down, the page says why, and it can't be listed again. Write to hello@sokie.sh about it.

What people see

Under What people see, set what the page says:

  • Name: up to 60 characters. It starts as the server's name.
  • Category: Commerce, Communication, Data, Developer tools, Finance, Marketing, Productivity, Support or Other.
  • In one line: what it does, in up to 100 characters.
  • Support and Privacy policy, from the list above.
  • Show how many calls it answers each month: a total, never who made them.
  • Show uptime and latency: this month's calls answered, and today's p95.

Save listing saves without listing it. On a listed server, the page and the Registry entry follow. A listed server keeps its support contact and privacy policy: you can change them, but not clear them.

Members, admins and the owner can change a listing; viewers can only read it.