├── CODE_OF_CONDUCT.md ├── CONTRIBUTING.md ├── LICENSE └── README.md /CODE_OF_CONDUCT.md: -------------------------------------------------------------------------------- 1 | # Contributor Covenant Code of Conduct 2 | 3 | ## Our Pledge 4 | 5 | We as members, contributors, and leaders pledge to make participation in our 6 | community a harassment-free experience for everyone, regardless of age, body 7 | size, visible or invisible disability, ethnicity, sex characteristics, gender 8 | identity and expression, level of experience, education, socio-economic status, 9 | nationality, personal appearance, race, religion, or sexual identity 10 | and orientation. 11 | 12 | We pledge to act and interact in ways that contribute to an open, welcoming, 13 | diverse, inclusive, and healthy community. 14 | 15 | ## Our Standards 16 | 17 | Examples of behavior that contributes to a positive environment for our 18 | community include: 19 | 20 | * Demonstrating empathy and kindness toward other people 21 | * Being respectful of differing opinions, viewpoints, and experiences 22 | * Giving and gracefully accepting constructive feedback 23 | * Accepting responsibility and apologizing to those affected by our mistakes, 24 | and learning from the experience 25 | * Focusing on what is best not just for us as individuals, but for the 26 | overall community 27 | 28 | Examples of unacceptable behavior include: 29 | 30 | * The use of sexualized language or imagery, and sexual attention or 31 | advances of any kind 32 | * Trolling, insulting or derogatory comments, and personal or political attacks 33 | * Public or private harassment 34 | * Publishing others' private information, such as a physical or email 35 | address, without their explicit permission 36 | * Other conduct which could reasonably be considered inappropriate in a 37 | professional setting 38 | 39 | ## Enforcement Responsibilities 40 | 41 | Community leaders are responsible for clarifying and enforcing our standards of 42 | acceptable behavior and will take appropriate and fair corrective action in 43 | response to any behavior that they deem inappropriate, threatening, offensive, 44 | or harmful. 45 | 46 | Community leaders have the right and responsibility to remove, edit, or reject 47 | comments, commits, code, wiki edits, issues, and other contributions that are 48 | not aligned to this Code of Conduct, and will communicate reasons for moderation 49 | decisions when appropriate. 50 | 51 | ## Scope 52 | 53 | This Code of Conduct applies within all community spaces, and also applies when 54 | an individual is officially representing the community in public spaces. 55 | Examples of representing our community include using an official e-mail address, 56 | posting via an official social media account, or acting as an appointed 57 | representative at an online or offline event. 58 | 59 | ## Enforcement 60 | 61 | Instances of abusive, harassing, or otherwise unacceptable behavior may be 62 | reported to the community leaders responsible for enforcement at 63 | [INSERT CONTACT METHOD]. 64 | All complaints will be reviewed and investigated promptly and fairly. 65 | 66 | All community leaders are obligated to respect the privacy and security of the 67 | reporter of any incident. 68 | 69 | ## Enforcement Guidelines 70 | 71 | Community leaders will follow these Community Impact Guidelines in determining 72 | the consequences for any action they deem in violation of this Code of Conduct: 73 | 74 | ### 1. Correction 75 | 76 | **Community Impact**: Use of inappropriate language or other behavior deemed 77 | unprofessional or unwelcome in the community. 78 | 79 | **Consequence**: A private, written warning from community leaders, providing 80 | clarity around the nature of the violation and an explanation of why the 81 | behavior was inappropriate. A public apology may be requested. 82 | 83 | ### 2. Warning 84 | 85 | **Community Impact**: A violation through a single incident or series 86 | of actions. 87 | 88 | **Consequence**: A warning with consequences for continued behavior. No 89 | interaction with the people involved, including unsolicited interaction with 90 | those enforcing the Code of Conduct, for a specified period of time. This 91 | includes avoiding interactions in community spaces as well as external channels 92 | like social media. Violating these terms may lead to a temporary or 93 | permanent ban. 94 | 95 | ### 3. Temporary Ban 96 | 97 | **Community Impact**: A serious violation of community standards, including 98 | sustained inappropriate behavior. 99 | 100 | **Consequence**: A temporary ban from any sort of interaction or public 101 | communication with the community for a specified period of time. No public or 102 | private interaction with the people involved, including unsolicited interaction 103 | with those enforcing the Code of Conduct, is allowed during this period. 104 | Violating these terms may lead to a permanent ban. 105 | 106 | ### 4. Permanent Ban 107 | 108 | **Community Impact**: Demonstrating a pattern of violation of community 109 | standards, including sustained inappropriate behavior, harassment of an 110 | individual, or aggression toward or disparagement of classes of individuals. 111 | 112 | **Consequence**: A permanent ban from any sort of public interaction within 113 | the community. 114 | 115 | ## Attribution 116 | 117 | This Code of Conduct is adapted from the [Contributor Covenant][homepage], 118 | version 2.0, available at 119 | https://www.contributor-covenant.org/version/2/0/code_of_conduct.html. 120 | 121 | Community Impact Guidelines were inspired by [Mozilla's code of conduct 122 | enforcement ladder](https://github.com/mozilla/diversity). 123 | 124 | [homepage]: https://www.contributor-covenant.org 125 | 126 | For answers to common questions about this code of conduct, see the FAQ at 127 | https://www.contributor-covenant.org/faq. Translations are available at 128 | https://www.contributor-covenant.org/translations. -------------------------------------------------------------------------------- /CONTRIBUTING.md: -------------------------------------------------------------------------------- 1 | # Contributing to Awesome Remote MCP Servers 2 | 3 | Thank you for your interest in contributing to Awesome Remote MCP Servers! This is a curated, opinionated list focused on high-quality, official MCP servers. This document provides guidelines and instructions for contributing to this repository. 4 | 5 | ## Quality Standards 6 | 7 | Before submitting a server for inclusion, please ensure it meets these criteria: 8 | 9 | - **Official Support**: The server must be officially supported by its maintainers 10 | - **Production Ready**: Must be stable and suitable for production use 11 | - **Active Maintenance**: Regular updates and bug fixes 12 | - **Security**: Proper authentication and security measures, with OAuth 2.0 support preferred 13 | - **Reliability**: Proven track record of uptime and performance 14 | - **Community**: Active user community and support channels 15 | 16 | ## How to Contribute 17 | 18 | ### 1. Fork the Repository 19 | 20 | First, fork this repository to your GitHub account. 21 | 22 | ### 2. Add Your Remote MCP Server 23 | 24 | Add your remote MCP server to the table in the README.md file. Each entry should follow this format: 25 | 26 | ```markdown 27 | | Server Name | Category | URL | Authentication | Maintainer | 28 | |------------|----------|-----|----------------|------------| 29 | | Your Server | Category | `https://your-server-url` | OAuth | [Your Organization](https://your-org-url) | 30 | ``` 31 | 32 | Required information: 33 | - **Server Name**: The name of your MCP server 34 | - **Category**: One of the following: 35 | - Language Models 36 | - Software Development 37 | - RAG-as-a-Service 38 | - Payments 39 | - Data Analysis 40 | - Other 41 | - **URL**: The complete URL to access your MCP server 42 | - **Authentication**: Must be OAuth 2.0, following the MCP spec 43 | - **Maintainer**: The official maintainer or organization with a link to their website 44 | 45 | ### 3. Additional Requirements 46 | 47 | Please ensure your contribution includes: 48 | 49 | - Link to official GitHub repository or website 50 | - Evidence of active maintenance (e.g., recent commits, releases) 51 | - Documentation of security measures 52 | - Information about the support channels 53 | - Any relevant benchmarks or performance metrics 54 | - Production deployment examples (if available) 55 | 56 | ### 4. Submit a Pull Request 57 | 58 | 1. Create a new branch for your changes 59 | 2. Make your changes 60 | 3. Submit a pull request with a clear description of: 61 | - Why the server meets our quality criteria 62 | - How it's being used in production 63 | - Any notable features or benefits 64 | 65 | ## Code of Conduct 66 | 67 | By participating in this project, you agree to abide by the [Contributor Covenant Code of Conduct](CODE_OF_CONDUCT.md). 68 | 69 | ## Questions? 70 | 71 | If you have any questions about contributing, please open an issue in the repository. -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | MIT License 2 | 3 | Copyright (c) 2024 Awesome Remote MCP Servers Contributors 4 | 5 | Permission is hereby granted, free of charge, to any person obtaining a copy 6 | of this software and associated documentation files (the "Software"), to deal 7 | in the Software without restriction, including without limitation the rights 8 | to use, copy, modify, merge, publish, distribute, sublicense, and/or sell 9 | copies of the Software, and to permit persons to whom the Software is 10 | furnished to do so, subject to the following conditions: 11 | 12 | The above copyright notice and this permission notice shall be included in all 13 | copies or substantial portions of the Software. 14 | 15 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR 16 | IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, 17 | FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE 18 | AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER 19 | LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, 20 | OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE 21 | SOFTWARE. -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Awesome Remote MCP Servers 2 | 3 | > 📧 **Subscribe to the Newsletter** Stay informed about new MCP servers and updates: 4 | > [Subscribe](https://remotemcp.substack.com/subscribe) 5 | 6 | > Not a developer & looking for ChatGPT Custom Integrations or Claude Custom Connectors? [Check out the Remote MCP Server List](https://www.remote-mcp.com/) 7 | 8 | A curated, opinionated list of high-quality **remote** Model Context Protocol (MCP) servers. This repository focuses on listing official and well-maintained MCP servers that can be accessed over the internet, helping developers discover reliable and production-ready services for their AI applications. 9 | 10 | ## What is MCP? 11 | 12 | [Model Context Protocol](https://modelcontextprotocol.io/) (MCP) is a protocol that enables AI models to interact with external tools and resources. Remote MCP servers allow clients to securely connect to these services over the internet. 13 | 14 | ### What are Custom Integrations? 15 | 16 | This is Claude's branding for connecting to remote MCP servers. 17 | 18 | ### What are Custom Connectors? 19 | 20 | This is OpenAI's branding for connecting to remote MCP servers. 21 | 22 | ## Why Remote only? 23 | 24 | Remote MCP servers are a more secure and easier way to use MCP. 25 | - Security wise, if you trust the provider's URL, and you are authenticated, then the security model is the same as using the Web. 26 | - Ease of use wise, you can copy & paste the server URL and you're away. No installing NPM packages etc. 27 | - They are the ONLY way to use MCP servers with Web based clients. 28 | 29 | ## How can I use an MCP server listed here? 30 | 31 | There are two main ways to use remote MCP servers on this list. 32 | 33 | 1. [Using a MCP ready client](#mcp-client) (Claude, ChatGPT, Cursor, etc.) 34 | 2. [In an API request to an LLM provider](#api-request) (OpenAI, Anthropic, Gemini, etc.) 35 | 36 | ## Authentication options 37 | 38 | This list has a mix of authentication options, different methods are better suited to certain use cases: 39 | 40 | - **OAuth 2.1**: This is an industry standard for authentication and is supported by MCP Clients like Claude. Adoption amongst clients is growing, but not yet widespread. 41 | For this all you need to connect is the server URL, and the client will guide you through the authentication flow. 42 | - **OAuth 2.1 🔐**: Indicates OAuth 2.1 authentication *without* dynamic client registration support. This means you may need to pre-register your client application with the provider, or use an API key pre generated by the provider. 43 | - **API Key**: An alternative to OAuth 2.0, this required to have an API key for the server. This is useful when using an API request to an LLM provider, rather than an MCP client. 44 | - **Open**: Easy to copy and paste and get started, but not as secure. This is the easiest way to get started, but not the most secure. 45 | 46 | 47 | ## Quality Criteria 48 | 49 | This is not an exhaustive list of all remote MCP servers. We maintain high standards for inclusion: 50 | 51 | - **Official Support**: Servers that are maintained by their underlying companies are preferred 52 | - **Production Ready**: Must be stable and suitable for production use 53 | - **Active Maintenance**: Regular updates and bug fixes 54 | - **Security**: Proper authentication and security measures, with OAuth 2.0 or API Key support required 55 | - **Reliability**: Proven track record of uptime and performance 56 | - **Community**: Active user community and support channels 57 | 58 | ## Remote MCP Server List 59 | 60 | | Name | Category | URL | Authentication | Maintainer | 61 | |------|----------|-------------|----------------|------------| 62 | | Asana | Project Management | `https://mcp.asana.com/sse` | OAuth2.1 | [Asana](https://asana.com) | 63 | | Audioscrape | RAG-as-a-Service | `https://mcp.audioscrape.com` | OAuth2.1 | [Audioscrape](https://www.audioscrape.com) | 64 | | Atlasian | Software Development | `https://mcp.atlassian.com/v1/sse` | OAuth2.1 🔐 | [Atlassian](https://atlassian.com) | 65 | | Box | Document Management | `https://mcp.box.com` | OAuth2.1 🔐| [Box](https://box.com) | 66 | | Canva | Design | `https://mcp.canva.com/mcp` | OAuth2.1 | [Canva](https://canva.com) | 67 | | Carbon Voice | Productivity | `https://mcp.carbonvoice.app` | OAuth2.1 | [Carbon Voice](https://getcarbon.app) | 68 | | Cloudflare Workers | Software Development | `https://bindings.mcp.cloudflare.com/sse` | OAuth2.1 | [Cloudflare](https://cloudflare.com) | 69 | | Cloudflare Observability | Observability | `https://observability.mcp.cloudflare.com/sse` | OAuth2.1 | [Cloudflare](https://cloudflare.com) | 70 | | Cloudinary | Asset Management | `https://asset-management.mcp.cloudinary.com/sse` | OAuth2.1 | [Cloudinary](https://cloudinary.com) | 71 | | Dialer | Outbound Phone Calls | `https://getdialer.app/sse` | OAuth2.1 | [Dialer](https://getdialer.app) | 72 | | Egnyte | Document Management | `https://mcp-server.egnyte.com/sse` | OAuth2.1 | [Egnyte](https://egnyte.com) | 73 | | Firefly | Productivity | `https://api.fireflies.ai/mcp` | OAuth2.1 | [Firefly](https://fireflies.ai) | 74 | | Find-A-Domain | Productivity | `https://api.findadomain.dev/mcp` | Open | [Find-A-Domain](https://findadomain.dev) | 75 | | GitHub | Software Development | `https://api.githubcopilot.com/mcp` | OAuth2.1 🔐 | [GitHub](https://github.com) | 76 | | Globalping | Software Development | `https://mcp.globalping.dev/sse` | OAuth2.1 | [Globalping](https://globalping.io/) | 77 | | Grafbase | Software Development | `https://api.grafbase.com/mcp` | OAuth 2.1 | [Grafbase](https://grafbase.com) | 78 | | Hive Intelligence | Crypto | `https://hiveintelligence.xyz/mcp` | OAuth 2.1 | [Hive Intelligence](https://hiveintelligence.xyz/) | 79 | | Instant | Software Development | `https://mcp.instantdb.com/mcp` | OAuth | [Instant](https://www.instantdb.com/) | 80 | | Intercom | Customer Support | `https://mcp.intercom.com/sse` | OAuth2.1 | [Intercom](https://intercom.com) | 81 | | Invidio | Video Platform | `https://mcp.invideo.io/sse` | OAuth2.1 | [Invidio](https://invideo.io/) | 82 | | Jam | Software Development | `https://mcp.jam.dev/mcp` | OAuth2.1 | [Jam.dev](https://jam.dev/) | 83 | | Kollektiv | Documentation | `https://mcp.thekollektiv.ai/sse` | Oauth2.1 | [Kollektiv](https://github.com/alexander-zuev/kollektiv-mcp) | 84 | | Linear | Project Management | `https://mcp.linear.app/sse` | OAuth2.1 | [Linear](https://linear.app) | 85 | | Listenetic | Productivity | `https://mcp.listenetic.com/v1/mcp` | OAuth2.1 | [Listenetic](https://app.listenetic.com) | 86 | | Meta Ads by Pipeboard | Advertising | `https://mcp.pipeboard.co/meta-ads-mcp` | OAuth2.1 | [Pipeboard](https://pipeboard.co) | 87 | | monday.com | Productivity | `https://mcp.monday.com/sse` | OAuth2.1 | [monday MCP](https://github.com/mondaycom/mcp) | 88 | | Neon | Software Development | `https://mcp.neon.tech/sse` | OAuth2.1 | [Neon](https://neon.tech) | 89 | | Netlify | Software Development | `https://netlify-mcp.netlify.app/mcp` | OAuth2.1 | [Netlify](https://netlify.com) | 90 | | Notion | Project Management | `https://mcp.notion.com/sse` | OAuth2.1 | [Notion](https://notion.so) | 91 | | Octagon | Market Intelligence | `https://mcp.octagonagents.com/mcp` | OAuth2.1 | [Octagon](https://octagonai.co) | 92 | | OneContext | RAG-as-a-Service | `https://rag-mcp-2.whatsmcp.workers.dev/sse` | OAuth2.1 | [OneContext](https://onecontext.ai) | 93 | | PayPal | Payments | `https://mcp.paypal.com/sse` | OAuth2.1 | [PayPal](https://paypal.com) | 94 | | Plaid | Payments | `https://api.dashboard.plaid.com/mcp/sse` | OAuth2.1 🔐| [Plaid](https://plaid.com) | 95 | | Prisma Postgres | Database | `https://mcp.prisma.io/mcp` | OAuth2.1 | [Prisma Postgres](https://www.prisma.io/docs/postgres/integrations/mcp-server#remote-mcp-server) 96 | | Rube | Other | `https://rube.app/mcp` | Oauth2.1 | [Composio](https://composio.dev) | 97 | | Scorecard | AI Evaluation | `https://scorecard-mcp.dare-d5b.workers.dev/sse` | OAuth2.1 | [Scorecard](https://scorecard.io) | 98 | | Sentry | Software Development | `https://mcp.sentry.dev/sse` | OAuth2.1 | [Sentry](https://sentry.io) | 99 | | Stripe | Payments | `https://mcp.stripe.com/` | OAuth2.1 & API Key | [Stripe](https://stripe.com) | 100 | | Stytch | Authentication | `http://mcp.stytch.dev/mcp` | OAuth2.1 | [Stytch](https://stytch.com) | 101 | | Square | Payments | `https://mcp.squareup.com/sse` | OAuth2.1 | [Square](https://square.com) | 102 | | Turkish Airlines | Airlines | `https://mcp.turkishtechlab.com/mcp` | OAuth2.1 | [Turkish Technology](https://mcp.turkishtechlab.com/) | 103 | | Vercel | Software Development | `https://mcp.vercel.com/` | OAuth2.1 | [Vercel](https://vercel.com) | 104 | | Webflow | CMS | `https://mcp.webflow.com/sse` | OAuth2.1 | [Webflow](https://webflow.com) | 105 | | Wix | CMS | `https://mcp.wix.com/sse` | OAuth2.1 | [Wix](https://wix.com) | 106 | | Simplescraper | Web Scraping | `https://mcp.simplescraper.io/mcp` | OAuth2.1 | [Simplescraper](https://simplescraper.io) | 107 | | WayStation | Productivity | `https://waystation.ai/mcp` | OAuth2.1 | [WayStation](https://waystation.ai) | 108 | | Zenable | Security | `https://mcp.www.zenable.app/` | OAuth2.1 | [Zenable](https://zenable.io) | 109 | | Zine | Memory | `https://www.zine.ai/mcp` | OAuth2.1 | [Zine](https://www.zine.ai/) | 110 | | Cloudflare Docs | Documentation | `https://docs.mcp.cloudflare.com/sse` | Open | [Cloudflare](https://cloudflare.com) | 111 | | Astro Docs | Documentation | `https://mcp.docs.astro.build/mcp` | Open | [Astro](https://astro.build) | 112 | | DeepWiki | RAG-as-a-Service | `https://mcp.deepwiki.com/sse` | Open | [Devin](https://devin.ai/) | 113 | | Hugging Face | Software Development | `https://hf.co/mcp` | Open | [Hugging Face](https://huggingface.co) | 114 | | Semgrep | Software Development | `https://mcp.semgrep.ai/sse` | Open | [Semgrep](https://semgrep.dev/) | 115 | | Remote MCP | MCP Directory | `https://mcp.remote-mcp.com` | Open | [Remote MCP](https://remote-mcp.com/) | 116 | | OpenMesh | Service Discovery | `https://api.openmesh.dev/mcp` | Open | [OpenMesh](https://openmesh.dev) | 117 | | OpenZeppelin Cairo Contracts | Software Development | `https://mcp.openzeppelin.com/contracts/cairo/mcp` | Open | [OpenZeppelin](https://openzeppelin.com) | 118 | | OpenZeppelin Solidity Contracts | Software Development | `https://mcp.openzeppelin.com/contracts/solidity/mcp` | Open | [OpenZeppelin](https://openzeppelin.com) | 119 | | OpenZeppelin Stellar Contracts | Software Development | `https://mcp.openzeppelin.com/contracts/stellar/mcp` | Open | [OpenZeppelin](https://openzeppelin.com) | 120 | | OpenZeppelin Stylus Contracts | Software Development | `https://mcp.openzeppelin.com/contracts/stylus/mcp` | Open | [OpenZeppelin](https://openzeppelin.com) | 121 | | LLM Text | Data Analysis | `https://mcp.llmtxt.dev/sse` | Open | [LLM Text](https://llmtxt.dev) | 122 | | GitMCP | Software Development | `https://gitmcp.io/docs` | Open | [GitMCP](https://gitmcp.io) | 123 | | Close | CRM | `https://mcp.close.com/mcp` | API Key | [Close](https://help.close.com/docs/mcp-server) | 124 | | HubSpot | CRM | `https://app.hubspot.com/mcp/v1/http` | API Key | [HubSpot](https://hubspot.com) | 125 | | Needle | RAG-as-a-service | `https://mcp.needle-ai.com/mcp` | API Key | [Needle](https://needle-ai.com) | 126 | | Zapier | Automation | `https://mcp.zapier.com/api/mcp/mcp` | API Key | [Zapier](https://zapier.com) | 127 | | Apify | Web Data Extraction Platform | `https://mcp.apify.com` | API Key | [Apify](https://apify.com) | 128 | | Dappier | RAG-as-a-Service | `https://mcp.dappier.com/mcp` | API Key | [Dappier](https://dappier.com/) | 129 | | Mercado Libre | E-Commerce | `https://mcp.mercadolibre.com/mcp` | API Key | [Mercado Libre MCP Server](https://mcp.mercadolibre.com/) | 130 | | Mercado Pago | Payments | `https://mcp.mercadopago.com/mcp` | API Key | [Mercado Pago MCP Server](https://mcp.mercadopago.com/) | 131 | | Short.io | Link shortener | `https://ai-assistant.short.io/mcp` | API Key | [Short.io](https://short.io) | 132 | | Telnyx | Communication | `https://api.telnyx.com/v2/mcp` | API Key | [Telnyx](https://telnyx.com) | 133 | | Dodo Payments | Payments | `https://mcp.dodopayments.com/sse` | API Key | [Dodo Payments](https://dodopayments.com) | 134 | | Polar Signals | Software Development | `https://api.polarsignals.com/api/mcp/` | API Key | [Polar Signals](https://www.polarsignals.com/blog/posts/2025/07/17/the-mcp-for-performance-engineering) | 135 | | Manifold | Forecasting | `https://api.manifold.markets/v0/mcp` | Open | [Manifold](https://manifold.markets) | 136 | | Javadocs | Software Development | `https://www.javadocs.dev/mcp` | Open | [Javadocs.dev](https://javadocs.dev) | 137 | 138 | ### MCP Clients 139 | 140 | A complete list of MCP clients can be found [here](https://modelcontextprotocol.io/clients). Here are some examples of installation with Claude. 141 | 142 | ### Claude 143 | 144 | #### Custom Integrations 145 | 146 | Anthropic has added [native support for Remote MCP into Claude](https://www.anthropic.com/news/integrations). It's currently available on Pro plans. 147 | 148 | Add these servers as *Custom Integrations* in the integrations section of your Claude app settings. 149 | 150 | ##### Step-by-Step Instructions 151 | 152 | 1. Navigate to Settings > Profile 153 | 2. Locate the "Integrations" section 154 | 3. Click "Add more" 155 | 4. Add your integration's remote MCP server URL 156 | 5. Finish configuring your integration by clicking "Add" 157 | 158 | Full instructions can be found [here](https://support.anthropic.com/en/articles/11175166-about-custom-integrations-using-remote-mcp). 159 | 160 | ### ChatGPT 161 | 162 | #### Custom Connectors 163 | 164 | OpenAI's support for remote MCP is currently in beta. It's integrated into the Deep Research function. 165 | 166 | Full instructions can be found [here](https://help.openai.com/en/articles/11487775-connectors-in-chatgpt#h_d2a53d4230). 167 | 168 | ##### Step-by-Step Instructions 169 | 170 | 1. Navigate to Settings > Profile 171 | 2. Locate the "Connectors" section 172 | 3. Click "Add Connector" 173 | 4. Add your connector's remote MCP server URL 174 | 5. Finish configuring your connector by clicking "Save" 175 | 176 | ### Other MCP Clients 177 | 178 | Note: As the MCP spec is still in development, not all clients may support all features. In particular client support of OAUTH is not yet widespread. 179 | 180 | For desktop clients the configuration you need to add to your client's config file will be 181 | 182 | ```json 183 | { 184 | "mcpServers": { 185 | "": { 186 | "command": "npx", 187 | "args": [ 188 | "mcp-remote", 189 | "" 190 | ] 191 | } 192 | } 193 | } 194 | ``` 195 | 196 | ### API Libraries 197 | 198 | Official support for MCP in API requests is supported by the following LLM providers: 199 | 200 | - [Anthropic](https://docs.anthropic.com/en/docs/agents-and-tools/mcp-connector) 201 | - [OpenAI](https://platform.openai.com/docs/guides/tools-remote-mcp) 202 | - [Gemini](https://ai.google.dev/gemini-api/docs/function-calling?example=meeting#model_context_protocol_mcp) 203 | 204 | Note that it's easier to get started with API Token, based authentication for these servers. See the [FAQs](#faqs) section for more details. 205 | 206 | 207 | ## FAQs 208 | 209 | ### Can I use an Oauth MCP server in an API request to an LLM provider? 210 | 211 | Yes, but you will need to manage your own OAuth authentication flow, in order to obtain an access token. 212 | A quick way to obtain an access token to test a server is to follow the instructions in Anthropic's guide [Obtaining an access token for testing](https://docs.anthropic.com/en/docs/agents-and-tools/mcp-connector#obtaining-an-access-token-for-testing) section. 213 | This is not generally recommended for production use, as it is not a secure way to authenticate users. 214 | 215 | ### Why do some servers have a `/sse` and others a `/mcp`? 216 | 217 | The `/sse` endpoint is for the Server Sent Events (SSE) protocol. It is being slowly deprecated in favor of the `/mcp` endpoint. 218 | The `/mcp` endpoint is for the Streamed HTTP protocol. 219 | In the future some clients may only support adding servers by the prefix preceding the 'sse' or 'mcp' and self-discovering full URL. 220 | We will update this list as we see this happening. 221 | 222 | ## Contributing 223 | 224 | We welcome contributions! Please follow these guidelines: 225 | 226 | 1. Fork the repository 227 | 2. Add your remote MCP server to the appropriate category 228 | 3. Include the following information: 229 | - Server name 230 | - Category 231 | - URL 232 | - Authentication requirements (Only OAuth 2.0, following the MCP spec is supported) 233 | - Example usage 234 | 4. Submit a pull request 235 | 236 | ## Acknowledgments 237 | 238 | - Inspired by the [Model Context Protocol](https://modelcontextprotocol.io/) 239 | 240 | ## Community 241 | 242 | Join the MCP community to stay updated and connect with other developers: 243 | 244 | - [Reddit Community](https://www.reddit.com/r/mcp/) 245 | 246 | ## License 247 | 248 | This project is licensed under the MIT License - see the [LICENSE](LICENSE) file for details. 249 | --------------------------------------------------------------------------------