Skip to content
{mcpdesc}

Add a tool

The tools catalog is a curated list of open-source tools and projects that support or build on the mcpdesc format. This page explains how to get a tool listed.

Prerequisites

Section titled “Prerequisites”

The one hard requirement is the mcpdesc badge, that states the supported version of the MCP Description specification.

We also recommend that a tool:

  • Be open source, or at minimum have a public page that documents the tool support for the MCP Description format,
  • Support the latest version of the MCP Description specification,
  • Identify a point of contact for the projet maintainers.

The tools catalog does not display which version of the MCP Description specification a tool supports — each tool self-declares the information in its own README using the mcpdesc badge.

We only verify that the badge exists and points at a real published specification series.

Add the mcpdesc badge

Section titled “Add the mcpdesc badge”

You can add the mcpdesc badge at the top of your repo’s README using:

[![mcpdesc: 0.8](https://img.shields.io/badge/mcpdesc-0.8-3c68d9.svg)](https://mcpdesc.org)

It renders as:

mcpdesc badge showing version 0.8

  • Set the version segment to the specification series your tool supports, for example 0.8.
  • A 0.8 badge is a coarse-grained compatibility claim, not a claim that every 0.8 prerelease or patch was tested. State the exact tested version, such as 0.8.0, in your README or release notes.
  • If your tool supports multiple versions, we recommend displaying the latest, but you may prefer displaying multiple badges (simply repeat the badge snippet).
  • The badge is self-declared: it is not a certification, conformance guarantee, or endorsement by the {mcpdesc} project.

Submit your tool

Section titled “Submit your tool”

Open a Tool submission issue using the form:

The form collects everything needed to create a catalog entry: tool name, repository URL, a one-line description, license, the latest supported specification version, and a main point of contact.

Have a question first? Start a thread in GitHub Discussions.

What happens next

Section titled “What happens next”

A maintainer will check that your README shows the mcpdesc badge and that its version is a published specification version. On acceptance, we add a structured record for your tool to the catalog and it appears on the tools page.