> For the complete documentation index, see [llms.txt](https://help.rhythms.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rhythms.ai/connectivity/connectors/add-a-custom-mcp-connector.md). # Add a custom MCP connector A **custom connector** lets you add any MCP (Model Context Protocol) server that is not already in the Rhythms catalogue, so Rhythms can use it in chat, documents, playbooks, and auto-updating Key Results with your own permissions. You add one from **My connectors**; most servers connect with OAuth, and servers that authenticate with a static token use a header instead. Want it built into Rhythms as a standard connector? You can **request it** (see below), and we will work to add it to the catalogue for the whole workspace. A custom connector is the way to start using it right now. ## Before you start * The MCP server's **URL**. It must use **HTTPS** and point at the server's MCP endpoint (this often ends in `/mcp`). You get this URL from the tool you are connecting, not from Rhythms. Check that platform's own documentation: vendors that publish an MCP server list its URL on their developer, integrations or MCP page, and for a server you host yourself it is the address of your own deployment. * How the server authenticates: * **OAuth** (most servers). If the server supports Dynamic Client Registration you need nothing extra. If it does not, create an OAuth app in that tool and have its **Client ID** and **Client Secret** ready. * **A token header** (some servers). Have the **header name** (for example `DD_API_KEY`) and its value ready. * Ensure you have permission to add custom connectors. Any member can by default, but an admin can restrict this — see [Manage connectors for your workspace](/connectivity/manage-connectors-for-your-workspace.md). ## Add the connector 1. Open **My connectors** from the left sidebar and click **Add custom connector** at the top right of the Connectors page. 2. Enter a **Name** and the **MCP Server URL**. 3. Choose how it authenticates: * **OAuth** (default): just click **Connect**. A browser window opens for you to sign in and authorize. If the server does not support Dynamic Client Registration, open **Advanced settings** first and paste the **Client ID** and **Client Secret** from the OAuth app you created in that tool. * **Token header**: open **Advanced settings**, go to **Authentication headers**, click **Add header**, and enter the header name and value. A header replaces the OAuth step. 4. Click **Connect**. Rhythms validates the server and, for OAuth, opens the sign-in window. When it succeeds the connector shows **Connected**. ![Adding a custom connector in Rhythms: clicking Add custom connector, entering a name and the MCP server's HTTPS URL, then opening Advanced settings to reveal OAuth credentials and authentication headers.](https://4039886202-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEGNgNGJOnocLzqT0TwtU%2Fuploads%2Fgit-blob-c6adce965b143ff6258c8ed377a0e21b322d2a9f%2F9022b633-021c-44d7-bb35-50a8284697fa-add-custom-connector.gif?alt=media) ## After you connect The connector now works everywhere connectors do — chat, documents, playbooks, and auto-updates. Each person connects their own account, so a teammate who wants to use it adds it the same way, or a Rhythms Admin can [share your connection with the team](/connectivity/share-a-connector-with-your-team.md) so they do not have to. A Rhythms Admin can also set which of the connector's tools Rhythms may use, or disconnect it, from the workspace [Connectors settings](/connectivity/manage-connectors-for-your-workspace.md). ## Who can add custom connectors By default any member can add one. A Rhythms Admin can limit this to admins from the **Custom connector permissions** control on the Connectors page; when it is set to **Admins Only**, members see the **Add custom connector** button greyed out with a note to contact their admin. See [Manage connectors for your workspace](/connectivity/manage-connectors-for-your-workspace.md). ## Request it as a built-in connector If you would rather Rhythms added the tool to the connector catalogue so your whole workspace gets it without setting up a custom connector, request it. On the Connectors page, type the tool's name into **Search connectors**. If it appears with a **Coming soon** label, click **Request**; if nothing matches, enter the name under **Can't find what you're looking for?** and click **Request**. The request comes straight to the Rhythms team, and we will do our best to add support for everyone as soon as we can. Adding it as a custom connector, above, is the way to start using it immediately in the meantime. ## Troubleshooting **“Could not validate this MCP server. Please check the URL.”** The URL must use HTTPS, be reachable from Rhythms, and point at the server's MCP endpoint. If your server sits behind a firewall, allow the Rhythms outbound IP ranges. **“This MCP server URL is already connected.”** The server is already added — find it under **Your connections** on the Connectors page rather than adding it again. **Does adding a connector expose it to everyone?** No. Your connection is private to you until a Rhythms Admin shares it. ## Related articles * [Connect Dynatrace](/connectivity/connectors/connect-dynatrace.md) — a full worked example of a custom OAuth MCP connector. * [Manage connectors for your workspace](/connectivity/manage-connectors-for-your-workspace.md) * [Share a connector with your team](/connectivity/share-a-connector-with-your-team.md) * [Use Rhythms from Claude, ChatGPT or Cursor](/connectivity/use-rhythms-from-claude-chatgpt-or-cursor.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.rhythms.ai/connectivity/connectors/add-a-custom-mcp-connector.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.