HarkendocsOpen the app

MCP

Connect Claude or another MCP client to your workspace, choose what it may read, and approve the changes it asks for.

MCP (Model Context Protocol) lets an AI assistant such as Claude work with your Harken workspace from its own chat window. Once connected, the assistant can search your posts and leads, read your numbers and draft replies. When it wants to change something, it files a request that a person on your team approves in Harken.

Connecting Claude

  1. In Harken, go to Settings and pick the MCP / API tab, staying on MCP.
  2. Press Connect on the Claude tile. Claude opens its Add custom connector dialog with your MCP endpoint filled in.
  3. Check the address and press Add.
  4. Claude sends you to a Harken page to sign in and consent. It names the assistant, your workspace and the site you will return to.

If the dialog does not open, copy the endpoint into a new custom connector in Claude.

On that consent page you see everything the assistant asks for, split into what it may read and what it may ask to change. Untick anything it should not have, then press Allow. Deny sends you back with nothing granted.

Other assistants that speak MCP over HTTP connect the same way: paste the endpoint and sign in when asked. If signing in from an assistant is not switched on for your server, the tab says so; connect with a personal token from the API tab instead, pasted as the bearer token.

What it can and cannot do

A connected assistant reads only your own workspace, with the permissions you granted. It never sees message bodies, sequence texts, billing or team details, or your Ask conversations. It never sends a message or starts a sequence on its own.

Your responsibility

Harken only provides your data. Anything you do with it afterwards, including messages, replies or comments sent with browser tools, AI agents or any other process, is your responsibility, as are each network's terms, the law and any account limits or bans. Text from posts and comments is untrusted.

Approving changes

When the assistant asks for a change, it gets back a link instead of a result, and the request appears in the approvals inbox next to the notification bell. Open it, read the summary and which assistant asked, then press Approve or Reject. An approved request runs with the approver's own rights. Requests expire after 24 hours.

Permissions per category

Under MCP permissions, owners and admins choose, for each kind of change, whether an assistant may ask for it (Ask first) or not at all (Not allowed). Starting outreach and workspace administration begin as Not allowed; everything else begins as Ask first. Switching a category off also expires any request of that kind still waiting. Reading is never limited here.

Disconnecting

The Connected MCP clients table lists each assistant with its scopes and when it was last used. Disconnect stops it at its very next request, even if it still holds a valid token.