# Hook MCP server

Preview
The Hook MCP server is in preview. Its tools, and what they take and return, can change at any time without notice. Its availability and uptime are not currently guaranteed. It is not generally available yet: contact Hook to ask for access.

The Hook MCP server lets an AI assistant, such as Claude, work with Hook on behalf of one of your members. It uses the [Model Context Protocol](https://modelcontextprotocol.io), so any assistant that supports remote MCP servers can connect to it.

The [MCP tool reference](/mcp/openapi) lists every tool, with its description and inputs. The [MCP changelog](/mcp_changelog) lists what changed in each version.

## What it can reach

- **It acts as one member.** Each person signs in with their own Hook account. The tools return only what that member can access in Hook, and nothing from any other organization.
- **Most tools only read.** The tool reference groups them under "Read only".
- **A few tools make changes, as the member.** They are grouped under "Makes changes":
  - Notes: create a note on a customer, and edit or delete the member's own notes.
  - Signals: raise or edit a signal, accept or dismiss a detected signal, clear an active one or make it the primary one for its product, and add, edit or delete status updates.
  - Alerts: complete, dismiss, save or unsave an alert, comment on one, and edit or delete the member's own comments.
Each change is made as the member who signed in, and shows in Hook as theirs. Many cannot be undone, so each of these tools tells the assistant to confirm the change with the person before making it. Nothing else can be created, changed or deleted.
- **It is not an API key.** There is no shared secret to store. Each member's assistant holds a token for that member alone, issued when they sign in.


## Server address

Use the address for the region your organization is hosted in.

| Region | Address |
|  --- | --- |
| Europe | `https://connect.hook.co/mcp` |
| United States | `https://connect.us.hook.co/mcp` |


## Connect an assistant

1. In your assistant, add a remote MCP server, often called a custom connector.
2. Enter the server address for your region.
3. When the assistant asks you to sign in, sign in with your own Hook account.
4. Ask it something, such as "Which of my customers renew in the next 30 days?"


### Claude team and enterprise plans

On a Claude team or enterprise plan, an owner of the Claude organization adds the connector once for everyone. Until they do, other members see "Ask an organization owner to add this for your team".

After the owner has added it, each member connects it and signs in to Hook themselves. The owner's sign-in is not shared.

## If sign-in is refused

- Check that you are signing in with the Hook account you use for the organization you want to reach.
- Check that you are using the address for your organization's region.
- If it is still refused, your organization may not have access to the MCP server yet. Contact Hook.


## After Hook adds or changes tools

An assistant reads the list of tools when the connector starts, and keeps that list. After Hook releases new or changed tools, a connected assistant goes on showing the old list until the connector is restarted.

- In Claude Desktop, quit the app and open it again.
- In other assistants, disconnect the server and connect it again.


If an assistant sends an input that a tool no longer has, the tool replies with an error that names the input and lists the ones it takes.

## Limits

- **Lists** return 10 items unless the assistant asks for more. A list can return up to 25 items in one call, or up to 100 for lists with short rows, such as customers. Each list gives the total count, and the assistant can ask for the next part.
- **Long content**, such as an email body or a brief, is cut short when it is very long, and the result says so. A long meeting transcript is returned in parts.