> 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-tools.md).
# MCP Tools
impact.com Model Context Protocol (MCP) tools are actions your AI assistant can take on your live impact.com account once you connect Claude, Cursor, or VS Code to mcp.impact.com. Ask in plain language for Help Center answers, marketing guidance, performance, invoices, partner or program discovery, tracking links, promo codes, payouts, and more.
Your AI assistant calls the right tool and uses your real data, scoped to your account type and permissions. Browse the catalog below, pick a tool that matches how you work, and try a sample prompt to see what is available without leaving chat.
{% 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/%7Binsert_current_page_path%7D.md?ask=)``\
*Rule: Replace `{insert_current_page_path}` with the routing path of this current page.*
{% endhint %}
---
# 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-tools.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 `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.
