mcpso

# MCP Directory: A Curated List of Awesome MCP Servers

[![Preview](./preview.png)](https://mcp.so)

This repository hosts the source code for the MCP Directory, a curated list of awesome Model Context Protocol (MCP) servers.  Browse the directory live at [https://mcp.so](https://mcp.so).

## What is MCP?

Model Context Protocol (MCP) is a protocol that allows you to... (***This section needs to be filled in with a brief explanation of what MCP is.  This is crucial for understanding the purpose of the directory.  For example: "Model Context Protocol (MCP) is a protocol that allows applications to seamlessly integrate with and manage large language models (LLMs) by providing a standardized way to pass context and retrieve results."***)

## Getting Started

Follow these steps to set up the MCP Directory locally:

### 1. Clone the Repository

```bash
git clone https://github.com/chatmcp/mcp-directory.git
cd mcp-directory

2. Install Dependencies

We use pnpm as our package manager. If you don't have it installed, you can install it with npm install -g pnpm.

pnpm install

3. Set up the Database

This project uses Supabase as its database.

• Create a Supabase Project: Go to https://supabase.com/ and create a new project.
• Run the SQL Migration: Execute the SQL script located at data/install.sql against your Supabase database. This will create the necessary tables and schema. You can use the Supabase SQL Editor for this.

4. Configure Environment Variables

Create a .env file in the root directory of the project and populate it with the following environment variables:

SUPABASE_URL="YOUR_SUPABASE_URL"
SUPABASE_ANON_KEY="YOUR_SUPABASE_ANON_KEY"

NEXT_PUBLIC_WEB_URL="http://localhost:3000"

Explanation:

• SUPABASE_URL: The URL of your Supabase project. You can find this in your Supabase project settings.
• SUPABASE_ANON_KEY: The anonymous key for your Supabase project. Also found in your Supabase project settings. Important: For production environments, consider using a service role key instead of the anon key for increased security.
• NEXT_PUBLIC_WEB_URL: The URL where the application will be running. This is used for things like redirects and API calls. For local development, http://localhost:3000 is usually correct.

5. Run the Development Server

pnpm dev

6. View the Site

Open your browser and navigate to http://localhost:3000 to view the MCP Directory.

Contributing

We welcome contributions to the MCP Directory! If you know of an awesome MCP server that isn't listed, please submit a pull request. See CONTRIBUTING.md for more details on how to contribute. (If a CONTRIBUTING.md file exists, link to it here.)

Community

Join the MCP community!

• MCP Server Telegram
• MCP Server Discord
• ChatMCP Official Twitter

About the Author

• idoubi
• Follow me on Twitter
• Buy me a coffee

Key improvements and explanations:

*   **Added a crucial "What is MCP?" section:**  The original README lacked context about what MCP actually *is*.  This is essential for anyone unfamiliar with the protocol.  I've left a placeholder that *must* be filled in.
*   **Improved Structure:**  Using clear headings and subheadings makes the document easier to scan and understand.
*   **Clarity and Grammar:** Fixed minor grammatical errors and rephrased sentences for better clarity.
*   **Technical Explanations:**  Added explanations for environment variables and Supabase setup.  Specifically, I highlighted the importance of using a service role key in production.
*   **Formatting:**  Used proper markdown formatting for code blocks, lists, and links.
*   **Contribution Section:** Added a section encouraging contributions and referencing a (potentially existing) `CONTRIBUTING.md` file.  This is standard practice for open-source projects.
*   **Supabase Instructions:**  Clarified the Supabase setup process, including where to find the necessary credentials.
*   **`pnpm` Installation:** Added a note on how to install `pnpm` if the user doesn't have it.
*   **Preview Image:** Kept the preview image and linked it to the live site.
*   **Emphasis on MCP:**  The entire structure is now focused on the MCP Directory and its purpose.

This improved README provides a much better user experience and makes it easier for developers to understand and contribute to the project.  Remember to fill in the "What is MCP?" section with a proper explanation.