> For the complete documentation index, see [llms.txt](https://integrations.impact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://integrations.impact.com/ai-solutions/mcp-quick-start/connect-other-mcp-clients.md).

# Connect Other MCP Clients

Connect any MCP-compatible AI client to impact.com using Dynamic Client Registration.

You can connect an AI client that supports the Model Context Protocol (MCP), other than Claude, Cursor, or VS Code, to the impact.com MCP Server using Dynamic Client Registration (DCR). With DCR, your client registers itself with impact.com when you connect, so you don't need an impact.com-issued client ID or client secret.

## Check the prerequisites

Before you connect, make sure you meet these requirements:

* An account administrator must have turned on MCP access for your impact.com account. See [Enable or Disable MCP access](https://integrations.impact.com/ai-solutions/mcp-quick-start/enable-or-disable-mcp-access).
* You need a valid impact.com login for a brand or partner account.
* Your AI client must support MCP and OAuth sign-in with Dynamic Client Registration.

## Choose the right setup guide

Use this guide for any AI client except [Claude Desktop and Claude Code](https://integrations.impact.com/ai-solutions/mcp-quick-start/mcp-for-claude-desktop-and-claude-code), [Cursor](https://integrations.impact.com/ai-solutions/mcp-quick-start/mcp-for-cursor), and [VS Code](https://integrations.impact.com/ai-solutions/mcp-quick-start/mcp-for-vs-code). impact.com has pre-registered those clients, so follow their verified guides instead.

## Connect using Dynamic Client Registration

Add impact.com MCP to your AI client, then approve the connection on impact.com.

1. In your AI client, add a new MCP server or connector.
2. Enter the server URL: `https://mcp.impact.com/mcp`.
3. Start the connection.
   * Your client registers itself with impact.com in the background. Registration alone doesn't give the client access to your data.
4. When prompted, log in to impact.com in your browser.
   * Only ever enter your password on impact.com, never in the AI client.
5. Review the consent screen:
   * The *account* you're connecting, including its name, ID, and whether it's a brand or partner account. If you have access to more than one impact.com account, choose the one you want to connect.
   * The *application name* requesting access.
   * Where the connection completes: a redirect domain, or *on this device* for local clients.
   * The *permissions* requested, such as read or write access to MCP capabilities.
6. Select **Allow** only if you started this connection yourself and trust the application.
7. Return to your AI client and confirm the connection is active.

After you connect, you can use impact.com MCP tools and skills, based on your account settings and your user permissions. To change accounts later, see [Switch Between MCP Accounts](https://integrations.impact.com/ai-solutions/mcp-quick-start/switch-between-mcp-accounts).

## Understand the risk of unverified clients

With DCR, the client's name and details come from the client itself, not from impact.com. impact.com doesn't verify, certify, or endorse these applications, and can't confirm them as validated or secure integrations. When you approve access, you accept the risk of connecting an unverified application.

## Troubleshoot your connection

If your connection doesn't work, try these fixes:

| Issue                                          | What to try                                                                                                                                                                                                                       |
| ---------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| The connection fails before you can log in.    | Confirm that MCP access is turned on for the account. See [Enable or Disable MCP access](https://integrations.impact.com/ai-solutions/mcp-quick-start/enable-or-disable-mcp-access).                                              |
| You can log in, but tools fail.                | Check your user permissions on impact.com, and see the [mcp.impact.com FAQ](https://integrations.impact.com/ai-solutions/mcp-quick-start/mcp.impact.com-faq).                                                                     |
| Claude asks for a client ID and client secret. | Follow [MCP for Claude Desktop & Claude Code](https://integrations.impact.com/ai-solutions/mcp-quick-start/mcp-for-claude-desktop-and-claude-code.md). Enter the client ID `mcp-impact-claude` and leave the client secret blank. |

## Additional resources

* [MCP Quick Start](https://integrations.impact.com/ai-solutions/mcp-quick-start) — Setup guides for every supported way to connect an AI client to impact.com MCP.
* [mcp.impact.com FAQ](https://integrations.impact.com/ai-solutions/mcp-quick-start/mcp.impact.com-faq) — Answers to common questions about connecting, permissions, and disconnecting MCP clients.
* [MCP Tools](https://integrations.impact.com/ai-solutions/mcp-tools) — The brand, partner, and AI Helper tools available once your client is connected.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://integrations.impact.com/ai-solutions/mcp-quick-start/connect-other-mcp-clients.md?ask=<question>&goal=<user_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 `automate deployments from our CI pipeline` 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.
