Connect AI tools to aclipp with MCP

The aclipp MCP server lets compatible AI clients work with the PR data directly. You can explore coverage, inspect outlets, authors and project configuration, and analyze AI visibility data without exporting it first, and you can set up projects and the competitors they are measured against, then add coverage and update existing outlets and authors without leaving the client.

Reading is the default. Writing is opt-in: a client only gets it if it asks for a write permission such as clippings:write or prompts:write and you approve it on the consent screen. Every delete asks you to confirm first. A delete tool takes up to 25 records at once, asks once for all of them, and reports which were deleted and which failed. Replacing report blocks or dashboard charts removes anything omitted from the replacement.

All clients connect to the hosted endpoint at https://api.aclipp.com/mcp. You do not need to run an aclipp server or a local development process. There are two ways to authenticate, and they differ in one way worth knowing: an API key always covers exactly one organization, while signing in with aclipp can cover several.

• Sign in with aclipp (OAuth): for interactive clients such as Claude and ChatGPT. No API key needed; you approve the connection in your browser.
• API key: for developer tools such as Claude Code and Cursor, or wherever you prefer a long-lived credential.

Supported clients

Before you start

You need an aclipp workspace with API access enabled. For Claude and ChatGPT, your normal aclipp login is all it takes. For Claude Code and Cursor you also need an aclipp API key with the read scopes your AI client should use.

Sign in with aclipp (OAuth)

When you connect aclipp in a client, either from the client's connector list or by adding https://api.aclipp.com/mcp as a custom connector, the client discovers the aclipp sign-in flow on its own and opens your browser. You sign in with your aclipp account, then approve the connection:

1. Choose the organizations the client may access. If you belong to only one, it is used and there is nothing to pick. If you belong to several, select every organization this connection should cover, and optionally tick Include future organizations so a workspace you are invited to afterwards is covered without reconnecting. Tools then take an optional organizationId; omit it and the call acts in your default organization.
2. Choose the projects. All projects are included by default, which also covers projects created later. Narrow the selection if the client should only see specific projects.
3. Approve. Expand Show permissions to see the requested actions for each area. The client receives exactly those permissions; write access is included only if the client requested it.

Connections are personal: they act on your behalf and end when you leave the organization. Workspace admins see every connection under Settings, Developers, Connected apps and can disconnect any of them immediately.

Claude (web)

aclipp is a Claude connector, so there is no server to set up.

1. Open Settings, then Connectors, and search for "aclipp".
2. Click Connect and complete the aclipp sign-in in the browser window.
3. In a chat, enable the aclipp connector in the tools menu. The aclipp tools are now available.

On Team and Enterprise plans an admin may need to enable connectors first.

If you cannot find aclipp in the list, you can still add it as a custom connector: choose "Add custom connector" and enter https://api.aclipp.com/mcp as the URL. Custom connectors require a paid Claude plan.

Claude Desktop

Claude Desktop uses the same connector settings as Claude on the web: search for "aclipp" under Settings, Connectors, click Connect, and complete the browser sign-in.

ChatGPT

aclipp is available as a ChatGPT plugin, so there is no server to set up.

1. Open the aclipp plugin in ChatGPT and add it.
2. Complete the aclipp sign-in in the browser window and approve the connection.
3. In a chat, enable the aclipp plugin. The aclipp tools are now available.

On Team and Enterprise plans an admin may need to allow plugins first.

If you prefer to set it up yourself, you can still add aclipp as a custom connector through developer mode: open Settings, then Apps & Connectors, then Advanced, and enable developer mode. Then create a connector with the MCP server URL https://api.aclipp.com/mcp and OAuth as the authentication method. This requires a paid plan; on Team and Enterprise plans an admin must allow it.

ChatGPT snapshots the tool definitions when a connection is approved. Reconnect aclipp after it releases new tools so ChatGPT refreshes its list.

Create an API key

For Claude Code and Cursor, open workspace API settings and create a key for your AI client. The full key is shown only once, so copy it before closing the dialog.

Grant only the scopes you need:

The scopes determine which tools the client sees. You can also restrict the key to specific projects.

Some tools need both the write and the read scope for their resource, because they read the record to do their job. Every delete tool except delete_monitoring needs both, for example delete_prompt needs prompts:write and prompts:read, and the report and dashboard update and replace tools need the read scope to base the change on the document's current version.

MCP exposes updates to existing outlets and authors. Creating or deleting them requires the REST API. MCP can create reports and dashboards, change their settings, and replace their contents; deleting them also requires the REST API. An API key used for MCP does not add tools beyond the catalog below.

alerts:write allows creating, updating and deleting alerts through MCP. To pause an alert's emails without deleting it, set enabled to false with update_alert.

Claude Code

Run this command in your terminal and replace the example key with your new key:

claude mcp add \
  --transport http \
  --scope user \
  --header "Authorization: Bearer aclipp_live_..." \
  aclipp https://api.aclipp.com/mcp

claude mcp add \
  --transport http \
  --scope user \
  --header "Authorization: Bearer aclipp_live_..." \
  aclipp https://api.aclipp.com/mcp

The user scope makes the connection available in every Claude Code project on your computer.

Start Claude Code and enter:

/mcp

/mcp

The aclipp server should be connected and show its available tools. You can also check the connection from a terminal:

claude mcp list

claude mcp list

Cursor

Open the global MCP configuration at ~/.cursor/mcp.json, or create .cursor/mcp.json when the connection should only be available in one project. Add:

{
  "mcpServers": {
    "aclipp": {
      "url": "https://api.aclipp.com/mcp",
      "headers": {
        "Authorization": "Bearer aclipp_live_..."
      }
    }
  }
}

{
  "mcpServers": {
    "aclipp": {
      "url": "https://api.aclipp.com/mcp",
      "headers": {
        "Authorization": "Bearer aclipp_live_..."
      }
    }
  }
}

Replace the example key, save the file, and open Cursor's MCP settings. The aclipp server should become available with its permitted tools. Restart Cursor or toggle the server off and on if it does not reconnect immediately.

Do not commit a project-level .cursor/mcp.json containing an API key. Prefer the global configuration for a personal connection.

Available MCP tools

The server only registers tools permitted by the connection's scopes. This is the complete current tool catalog:

Keep this table in sync when MCP tools or their required scopes change.

Try your first analysis

Start by letting the client discover the project and its configuration:

Use aclipp to list my projects. For the relevant project, inspect its
configuration and summarize this year's coverage by channel, country,
sentiment, and outlet. Highlight the strongest coverage and any notable gaps.

Use aclipp to list my projects. For the relevant project, inspect its
configuration and summarize this year's coverage by channel, country,
sentiment, and outlet. Highlight the strongest coverage and any notable gaps.

The client can resolve tag IDs through the project configuration and should use the analytics catalog for valid metric, shape, dimension, and aggregation combinations. Series, breakdown, and table queries require a date range of no more than 366 days. Row-producing queries are bounded and tell the client when a result was truncated.

For example:

Compare our coverage in Germany and Austria during the last quarter. Break it
down by channel and sentiment, list the top outlets, and cite the clippings
behind any important conclusion.

Compare our coverage in Germany and Austria during the last quarter. Break it
down by channel and sentiment, list the top outlets, and cite the clippings
behind any important conclusion.

Troubleshooting

Connection failed

Confirm that the configured URL is https://api.aclipp.com/mcp. In Claude Code, run claude mcp list. In Cursor, open the MCP settings and inspect the server status.

Authentication failed

For OAuth connections, disconnect the connector in the client and connect again; the browser sign-in issues a fresh grant. This is also needed after an admin disconnected the connection or after you left the organization. For API keys, create a new key if the configured key was revoked, copied incorrectly, or is no longer available. aclipp API keys use the aclipp_live_... format, and the header value must start with Bearer .

A tool is missing

Tools are registered according to the connection's scopes, and a tool only appears when the connection holds every scope that tool needs. Some tools need more than one: every delete tool except delete_monitoring also reads the record to describe it in the confirmation prompt, and the report and dashboard update and replace tools read the document to base the change on its current version.

OAuth connections receive the supported scopes requested by the client; if the client requests no scopes, aclipp grants the full supported read set and no write access. For API keys, update or replace the key with the scopes the tool needs, then reconnect the server so the client refreshes its tool list.

A tool can also appear and still be refused. Tools are offered on scopes alone, but an OAuth connection acts with your role in the workspace, and that role is rechecked on every call. An editor, for example, may create dashboards but not change them, so update_dashboard is offered and then answers that the change is not permitted. API keys are not bound by a role this way.

Too many requests

The MCP server allows 300 requests per minute and 20,000 per day, counted per signed-in user or per API key. Over the limit, calls fail with 429 and a Retry-After header; wait that long before retrying. See Rate limits.

The client shows an outdated tool list

Reconnect the aclipp server or start a new client session. ChatGPT snapshots tool definitions when a connection is approved, so reconnect it there as well.

Remove the connection

For Claude and ChatGPT, disconnect the connector or plugin in the client's settings. Workspace admins can also disconnect any OAuth connection under Settings, Developers, Connected apps, which cuts off access within a minute.

Remove the user-scoped Claude Code server with:

claude mcp remove aclipp --scope user

claude mcp remove aclipp --scope user

For Cursor, remove the aclipp entry from mcp.json. Revoke the API key in workspace API settings when it is no longer needed.

Keep the API key safe

The API key is stored in the client's private configuration. Never commit it or paste it into a chat, issue, screenshot, or shared terminal transcript. Use a separate, minimally scoped key for each client so you can revoke one connection without affecting another.