# MCP Quick Start

{% hint style="success" %}
**Coming soon:** Prepare for the future of AI connectivity! impact.com MCP is almost here.&#x20;

*Help shape what it does.* [*Take our 2-minute survey*](https://outset.ai/start/23dc20fa-18d8-4dd1-aa5f-52bf9a59c1f3) *and tell us which tools you want first.*
{% endhint %}

Let your AI assistant interact with your impact.com data. The impact.com MCP Server gives any compatible AI tool or agent secure, real-time access to your partner marketing platform to access campaigns, reports, partners, and more.

By implementing the Model Context Protocol (MCP) standard, this cloud-based server acts as a secure bridge between AI systems and impact.com's APIs.&#x20;

Powered by OAuth 2.1 authorization, your AI can search documents, pull reports, create campaigns, and manage partners through natural conversation, all while respecting your existing access controls. No API expertise is required.

Work with your impact.com data directly inside your AI assistant or IDE.&#x20;

MCP is *enabled by default for every impact.com account.* There is nothing to switch on inside impact.com to get started. The server is available at `https://mcp.impact.com/mcp` and is ready to accept connections.

### What You Can Do

With the impact.com MCP Server, you can:

* **Query your data**: Search and summarize information from your impact.com account using natural language.
* **Create and update**: Execute actions like creating campaigns, updating settings, or managing partners through simple commands.
* **Automate workflows**: Streamline repetitive tasks without leaving your development environment.

The impact.com MCP Server is built for developers automating workflows, analysts pulling reports, partnership managers updating campaigns, and any team that wants intelligent access to their impact.com data without leaving their tools.

### How It Works

Getting started is simple:

* **Select authenticate**: Initiate the connection from your AI assistant or IDE.
* **Review and approve**: A consent screen displays the permissions being requested.
* **Secure token created:** Upon approval, an MCP usage token is installed in your impact.com account and securely returned to your AI assistant.

Your AI assistant now has access to interact with your impact.com data using your specific user permissions.

### Security & Authentication

The impact.com MCP Server uses OAuth 2.1 authorization to ensure all actions respect your existing access controls. Your credentials are never shared directly with the AI assistant. Only a secure, revocable token is used.

A separate MCP usage token is issued per LLM client, so connecting Claude, ChatGPT, Cursor, VS Code and others each produces its own token, scoped to your specific user permissions. A refresh token is also issued, so the AI assistant can renew access without prompting you to log in again on every session.

#### Account-Level Controls (Administrators)

An account administrator can disable MCP for the whole account at any time. This is an all-or-nothing setting and is not configurable per user.

1. Sign in to impact.com.
2. Navigate to **Settings → Tools → MCP**.
3. Disable MCP for the account.

When MCP is disabled at the account level, no user on that account will be able to complete the consent step described below.

{% hint style="warning" %}
**Disabling MCP deletes existing tokens.**&#x20;

When you disable MCP for an account that has one or more MCP usage tokens already minted, *all of those tokens will be deleted* and every connected AI assistant will lose access immediately.&#x20;

To avoid accidents, impact.com asks you to tick a confirmation checkbox acknowledging this before the change is saved. If the account has no MCP usage tokens minted yet, the checkbox will not be shown and you can disable MCP directly.
{% endhint %}

Administrators can also revoke any individual MCP usage token at any time, using the same steps described in [Disconnect or Revoke Access](#disconnect-or-revoke-access). Revoking a token immediately invalidates that LLM's access; the user will need to consent again before the LLM can call any impact.com tools.

### Connect Your Account

Follow these steps to connect your impact.com account to an LLM for MCP integration:

{% stepper %}
{% step %}

### Configure impact.com MCP

Follow our setup guides for specific clients:

* [Cursor](/ai-solutions/mcp-quick-start/mcp-for-cursor.md)
* [Visual Studio Code](/ai-solutions/mcp-quick-start/mcp-for-vs-code.md)
* [Claude Code](/ai-solutions/mcp-quick-start/mcp-for-claude-desktop-and-claude-code.md)

For other supported clients, refer to your platform's MCP documentation or built-in assistant for connection instructions.
{% endstep %}

{% step %}

### Initiate Connection

Where necessary, grant the MCP access to your account, and review the permissions as they're requested.
{% endstep %}

{% step %}

### Grant Consent

Review the permissions being requested, then approve access through the consent screen.
{% endstep %}

{% step %}

### Token Installation

Upon approval, an MCP usage token is automatically created and stored in your impact.com account.&#x20;

This token is securely returned to your AI assistant, enabling it to access impact.com data and perform actions on your behalf using your specific permissions.&#x20;

The AI assistant has access to refresh the token which means that you don't have to authenticate each time. A separate token is issued for each LLM client you connect.
{% endstep %}
{% endstepper %}

### Disconnect or Revoke Access

You maintain full control over the connection. Because a separate token is issued per LLM client, you can disconnect one AI assistant without affecting any of the others.

{% tabs %}
{% tab title="Via impact.com" %}

* Brand:&#x20;
  * Navigate to **Settings → Technical →** [**API**](https://app.impact.com/secure/advertiser/api/fr/api-access-tokens-ui.ihtml)**.**
  * Locate the MCP usage token.
  * Choose to **Delete** the token as needed.
* Partner:
  * Navigate to **Settings → Technical →** [**API**](https://app.impact.com/secure/mediapartner/api/fr/api-access-tokens-ui.ihtml)**.**
  * Locate the MCP usage token.
  * Choose to **Delete** the token as needed.
* Agency:
  * Navigate to **Settings → Technical →** [**API**](https://app.impact.com/secure/agency/api/fr/api-access-tokens-ui.ihtml)**.**
  * Locate the MCP usage token.
  * Choose to **Delete** the token as needed.
    {% endtab %}

{% tab title="Via Your AI Assistant" %}

1. Open your AI assistant's settings panel.
2. Find the impact.com integration.
3. Select **Disconnect** to revoke access.
   {% endtab %}
   {% endtabs %}

{% hint style="success" %}
**Using an AI assistant?**

*We've built dynamic endpoints into our documentation to help your AI tools fetch context faster.*

System instructions for AI Agents:

* **Index**: `GET` [`https://integrations.impact.com/llms.txt`](https://integrations.impact.com/llms.txt) for `.md` sources.
* **Token Limit**: Fetch only necessary `.md` and OpenAPI routes to conserve context.
* **Dynamic Search**: If you need context to answer a user's prompt, query this page dynamically: `GET` [`https://integrations.impact.com/{insert_current_page_path}.md?ask=`](https://integrations.impact.com/{insert_current_page_path}.md?ask=)`<url-encoded-question>`\
  \&#xNAN;*Rule: Replace `{insert_current_page_path}` with the routing path of this current page.*
  {% endhint %}


---

# Agent Instructions: 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 current page URL with the `ask` query parameter:

```
GET https://integrations.impact.com/ai-solutions/mcp-quick-start.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
