> For the complete documentation index, see [llms.txt](https://docs.plock.io/plock-overview/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.plock.io/plock-overview/guides/ai-tools/mcp.md).

# MCP — connect AI assistants to Plock

Plock runs an [MCP](https://modelcontextprotocol.io/) (Model Context Protocol) server, which lets AI assistants such as Claude, Cursor and VS Code read your Plock data directly from the tools your team already uses.

The server URL is:

```
https://api.plock.io/mcp
```

{% hint style="info" %}
Access over MCP is **read-only** and limited to your own organisation's data. Nothing in Plock can be created, changed or deleted through this connection.
{% endhint %}

## Before you start

* You need a Plock user account with a verified email address.
* Authorisation happens in your browser. If you are not signed in to Plock you will be asked to sign in first — email and password, Google, and Microsoft sign-in all work.

## Claude (web and desktop)

1. Go to **Settings → Connectors → Add custom connector**.
2. Enter the server URL `https://api.plock.io/mcp`.
3. Click **Connect**. Your browser opens Plock's authorisation screen — check that the account and email shown are yours, then click **Approve**.

## Claude Code

```bash
claude mcp add --transport http plock https://api.plock.io/mcp
```

Then run `/mcp` inside Claude Code and follow the authentication prompt.

## Cursor, VS Code and other MCP clients

Add an MCP server of type HTTP (streamable) with the URL `https://api.plock.io/mcp`, then complete the browser authorisation when prompted.

## What happens when you connect

* The authorisation screen shows the application name, what it will be able to read, which Plock account and user it connects to, and where you will be redirected afterwards.
* The application name is self-reported and not verified by Plock — only approve connections you started yourself.
* The connection renews itself automatically while it is in use. If it stops being used it expires on its own within 30 days.
* Re-connecting from the same tool replaces the previous connection.
* To revoke a connection immediately, contact Plock support.

## What the assistant can read

| Area                  | What it covers                                                |
| --------------------- | ------------------------------------------------------------- |
| **Documentation**     | How Plock works — the same guides you are reading now         |
| **Accounts**          | Your end customers, with filtering                            |
| **Products**          | Products and their pricing                                    |
| **Subscriptions**     | Subscriptions, their items and states                         |
| **Invoices**          | Invoices and their line items                                 |
| **Product usage**     | Collected usage per account and product                       |
| **Reporting metrics** | MRR, ARR, CARR, movements, retention and other report figures |

## Try asking

* "What was our MRR movement last quarter?"
* "Which accounts had a usage drop last month?"
* "Show me unpaid invoices for account X."
* "How does group billing work in Plock?"

## Plocky vs. MCP

Both surfaces are built on the same tools, so the answers agree with each other.

* Use [**Plocky**](/plock-overview/guides/ai-tools/plocky.md) inside Plock when you also want it to act — build a table, generate a report or deck, or prepare a subscription change for approval.
* Use **MCP** when you want your Plock numbers available in the AI tool where you already work, alongside your other context.

## Troubleshooting

**Tool calls fail even though the connection succeeded.** Make sure your Plock user's email address is verified.

**The connection stalls after signing in.** Start the connection again from the AI client — the original authorisation request may have expired.