Template: what an MCP server entry must state

Description

A house entry. Written by the people who run Promptea, published here so the catalogue has something to show and so the required fields have a worked example.

This shelf is empty of real servers on purpose: it opens with the template rather than with somebody else’s project reposted without asking. If you maintain a server, this is the shape we want, and it maps onto the fields of the official server.json so you are not writing anything twice.

Required in every entry

• Name and identifier. The reverse DNS name from your server.json, for example io.github.you/thing.
• What it gives the agent. Tools, resources and prompts, listed by name, one line each.
• What it needs. Runtime, transport, and every credential. Name the scopes, not just the service.
• Blast radius. What it can write to, delete or spend. If it only reads, say so plainly, it is a selling point.
• Licence and repository. Both, always.

Skeleton

{
  "name": "io.github.you/thing",
  "description": "One sentence. What an agent can do that it could not before.",
  "repository": { "url": "https://github.com/you/thing", "source": "github" },
  "version": "0.1.0",
  "packages": [
    {
      "registryType": "npm",
      "identifier": "@you/thing-mcp",
      "transport": { "type": "stdio" },
      "environmentVariables": [
        { "name": "THING_TOKEN", "description": "read-only token", "isSecret": true }
      ]
    }
  ]
}

The field reviewers care about most

Blast radius. A registry that lists twenty thousand servers and never says which ones can delete your files is a phone book, not a catalogue. Say what yours can reach, and say it before the install instructions.