> 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-skills/install-an-mcp-skill.md).

# Install an MCP Skill

Every impact.com skill installs the same way, whichever AI client you use. This guide covers Claude, Cursor, and VS Code. Each skill's own page provides the skill package and a sample prompt to run it.

## Before you start

1. Make sure MCP access is enabled for your account. Account administrators control\
   this for everyone on the account, and can [enable or disable MCP access](/ai-solutions/mcp-quick-start/enable-or-disable-mcp-access.md).
2. Connect your AI client. See [MCP for Claude Desktop & Claude Code](/ai-solutions/mcp-quick-start/mcp-for-claude-desktop-and-claude-code.md), [MCP for Cursor](/ai-solutions/mcp-quick-start/mcp-for-cursor.md), or [MCP for VS Code](/ai-solutions/mcp-quick-start/mcp-for-vs-code.md).
3. Open the skill you want to use from [MCP Skills](/ai-solutions/mcp-skills.md), then download or copy its skill package.
4. Keep the `name` and `description` from the package frontmatter, because your client uses them to list the skill and trigger it automatically.

{% hint style="success" %}
**Note:** You need both MCP and the skill. MCP supplies live impact.com data, and the skill tells your assistant how to run the workflow.
{% endhint %}

## Install in Claude

In Claude Desktop, you upload skills through your settings.

1. Select your profile name at the bottom of the sidebar, then select **Settings**.
2. In the *Customize* section, select **Skills**.
3. Select **Add** ![](https://3238951795-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiVbdCghMC6mw51rrphG6%2Fuploads%2F2TKFDMY7RSc7BclbbJJV%2Fdropdown.svg?alt=media\&token=381aa52f-923f-4215-9d68-d3cc1432f682)**\[Drop-down menu]**, then select **Upload a skill**.
4. Select the skill package you downloaded.
5. Confirm the skill appears in your skills list.

## Install in Cursor

Cursor reads skills from a folder in your project or your home directory. The folder name must match the `name` in the package frontmatter, which uses lowercase letters and hyphens.

1. Create `.cursor/skills/<skill-name>/` in your project root, for example `.cursor/skills/partner-weekly-performance-digest/`.
2. Add the `SKILL.md` file from the skill package inside that folder.
3. Optionally, create the same folder at `~/.cursor/skills/` instead, so the skill applies across all your codebases.
4. In Agent chat, type `/` and select the skill by name.

Cursor also reads skills from shared paths such as `.agents/skills/`, `.claude/skills/`, and `.codex/skills/`.

## Install in VS Code

VS Code reads skills from a folder in your workspace or your user profile. The folder name must match the `name` in the package frontmatter, which uses lowercase letters and hyphens.

1. In VS Code settings, enable **Use Agent Skills**.
2. Create `.github/skills/<skill-name>/` in your project root for a single workspace, or `~/.copilot/skills/<skill-name>/` for all your projects.
3. Add the `SKILL.md` file from the skill package inside that folder.
4. In Copilot Chat, type `/skills` or open the *Agent Customizations* menu to confirm the skill is active.

## Run the skill

1. Open a chat where [mcp.impact.com](https://mcp.impact.com/) is connected.
2. Use the sample prompt from the skill's page, or describe the job in your own words.
3. Answer any follow-up questions about program, date range, and destinations so the skill can call the right tools.

Your client can also run the skill on its own when your request matches the skill's description, so you do not always need to name it.

You’ll know the skill worked when the assistant returns real-time data from your connected impact.com account instead of general guidance. Refer to each skill's dedicated page for a detailed description of its output.

If the skill runs but returns no data, see the troubleshooting answers in the [MCP Skills FAQ](/ai-solutions/mcp-skills/mcp-skills-faq.md).

## See also

<table data-view="cards"><thead><tr><th></th><th data-type="content-ref"></th></tr></thead><tbody><tr><td></td><td><a href="/ai-solutions/mcp-quick-start.md">MCP Quick Start</a></td></tr><tr><td></td><td><a href="/ai-solutions/mcp-skills/brand-skills.md">Brand Skills</a></td></tr><tr><td></td><td><a href="/ai-solutions/mcp-skills/partner-skills.md">Partner Skills</a></td></tr><tr><td></td><td><a href="/ai-solutions/mcp-skills/mcp-skills-faq.md">MCP Skills FAQ</a></td></tr></tbody></table>


---

# 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-skills/install-an-mcp-skill.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.
