---
title: "Add a tool"
description: "How to get an open-source tool listed in the mcpdesc tools catalog — the prerequisites, the mcpdesc badge, and where to submit."
source: "https://mcpdesc.org/docs/add-a-tool/"
---

The [tools catalog](/tools) 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

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 version.

## Add the mcpdesc badge

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

```markdown
[![mcpdesc](https://img.shields.io/endpoint?url=https://mcpdesc.org/badge/0.7.0.json)](https://mcpdesc.org)
```

> Note that the badge reference is hosted at mcpdesc.org, so the label, version, and brand color stay consistent across every tool and can be maintained centrally over time.

It renders as:

![mcpdesc badge showing version 0.7.0](/img/mcpdesc-0.7.0-badge.png)

* Use the file for the spec version your tool supports, e.g. `/badge/0.7.0.json`.
* 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

Open a **Tool submission** issue using the form:

* [Submit a tool →](https://github.com/mcpdesc/mcpdesc.org/issues/new?template=tool-submission.yml)

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](https://github.com/orgs/mcpdesc/discussions).

## 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](/tools).