# How to Contribute a New MCP Server to the Awesome-MCP-Servers Repository

> Learn how to contribute a new MCP server to the awesome-mcp-servers repository by forking, branching, updating README.md, and submitting a pull request. Get your server listed today.

- Repository: [Frank Fiegel/awesome-mcp-servers](https://github.com/punkpeye/awesome-mcp-servers)
- Tags: how-to-guide
- Published: 2026-09-04

---

**To contribute a new MCP server, fork the punkpeye/awesome-mcp-servers repository, create a dedicated branch, add your server entry to README.md following the established format and alphabetical ordering, then submit a pull request for maintainer review.**

The awesome-mcp-servers repository maintains a curated list of Model Context Protocol (MCP) server implementations. Contributing a new server follows a standardized workflow defined in [`CONTRIBUTING.md`](https://github.com/punkpeye/awesome-mcp-servers/blob/main/CONTRIBUTING.md) that ensures consistency and quality across all entries.

## Step-by-Step Contribution Workflow

### Fork and Clone the Repository

Start by clicking the **Fork** button on the GitHub page to create your own copy of the project. As documented in [`CONTRIBUTING.md`](https://github.com/punkpeye/awesome-mcp-servers/blob/main/CONTRIBUTING.md) at line 10, forking creates the isolated workspace needed for your changes. Then clone your fork locally:

```bash
git clone https://github.com/<your-username>/awesome-mcp-servers.git
cd awesome-mcp-servers

```

### Create a Feature Branch

Create a dedicated branch for your addition to keep changes isolated from the `main` branch. According to [`CONTRIBUTING.md`](https://github.com/punkpeye/awesome-mcp-servers/blob/main/CONTRIBUTING.md) at line 12, use a descriptive name like `add-new-server`:

```bash
git checkout -b add-new-my-server

```

### Add Your Server Entry to README.md

Edit the [`README.md`](https://github.com/punkpeye/awesome-mcp-servers/blob/main/README.md) file to insert your server in the **Server Implementations** section (found at line 73). Follow the established format precisely:

- **Server name** – Link to the GitHub repository
- **Description** – One-sentence summary of functionality
- **Category icons** – Place appropriate emojis (e.g., 📇 for TypeScript/JavaScript, ☁️ for cloud, 🏠 for local) as defined in the legend at [`README.md`](https://github.com/punkpeye/awesome-mcp-servers/blob/main/README.md) line 46
- **Alphabetical order** – Insert the entry in the correct alphabetical position within its category to maintain the list structure

### Commit Your Changes

Stage the modified [`README.md`](https://github.com/punkpeye/awesome-mcp-servers/blob/main/README.md) and commit with a clear, descriptive message. The guidelines at [`CONTRIBUTING.md`](https://github.com/punkpeye/awesome-mcp-servers/blob/main/CONTRIBUTING.md) line 24 recommend the format `Add <ServerName> MCP server`:

```bash
git add README.md
git commit -m "Add MyServer MCP server"

```

### Push and Open a Pull Request

Push your branch to your fork as shown at [`CONTRIBUTING.md`](https://github.com/punkpeye/awesome-mcp-servers/blob/main/CONTRIBUTING.md) line 30:

```bash
git push origin add-new-my-server

```

Then open a pull request against the original repository. As outlined at [`CONTRIBUTING.md`](https://github.com/punkpeye/awesome-mcp-servers/blob/main/CONTRIBUTING.md) line 36, provide a descriptive title and body explaining your addition. Maintainers will review your submission following the process at line 38.

## Critical Formatting Requirements

To ensure your contribution meets repository standards, adhere to these specific guidelines from [`CONTRIBUTING.md`](https://github.com/punkpeye/awesome-mcp-servers/blob/main/CONTRIBUTING.md):

- **Consistency** – Match existing markdown style, punctuation, and capitalization (line 43)
- **Alphabetical ordering** – Entries must be sorted alphabetically within categories (line 44)
- **One server per line** – Improves readability and simplifies diffs (line 46)
- **Accurate metadata** – Verify repository URLs and descriptions are correct and current

## Summary

- Fork the punkpeye/awesome-mcp-servers repository and create a dedicated feature branch before making changes
- Add your server entry to [`README.md`](https://github.com/punkpeye/awesome-mcp-servers/blob/main/README.md) in the Server Implementations section, following the format: name linked to repo, brief description, and category icons from the legend
- Maintain alphabetical order within categories and limit entries to one per line as required by [`CONTRIBUTING.md`](https://github.com/punkpeye/awesome-mcp-servers/blob/main/CONTRIBUTING.md)
- Commit with descriptive messages like "Add ServerName MCP server" and push to your fork
- Open a pull request against the main repository for maintainer review

## Frequently Asked Questions

### What file should I edit to add my MCP server?

You must edit the [`README.md`](https://github.com/punkpeye/awesome-mcp-servers/blob/main/README.md) file in the repository root. Specifically, add your entry to the **Server Implementations** section (located at line 73), placing it in the appropriate category sub-section in alphabetical order.

### What format should I follow when adding a new server?

Follow the existing entry format: link the server name to its GitHub repository, provide a one-sentence description, and append the appropriate category emojis (such as 📇 for TypeScript or ☁️ for cloud services) as defined in the legend at [`README.md`](https://github.com/punkpeye/awesome-mcp-servers/blob/main/README.md) line 46.

### Does my server entry need to be in a specific order?

Yes. According to [`CONTRIBUTING.md`](https://github.com/punkpeye/awesome-mcp-servers/blob/main/CONTRIBUTING.md) line 44, entries must be added in alphabetical order within their respective categories. This organization helps users locate tools quickly and maintains the curated list structure.

### What should my commit message say?

Use a clear, descriptive commit message in the format "Add ServerName MCP server" as recommended at [`CONTRIBUTING.md`](https://github.com/punkpeye/awesome-mcp-servers/blob/main/CONTRIBUTING.md) line 24. This convention helps maintainers identify your contribution during the review process described at line 38.