MCP | Kluff docs

Use Kluff from Claude, ChatGPT, Cursor or any MCP app, and give your agents tools from any MCP server.

MCP (Model Context Protocol) is an open standard that lets AI tools share data and actions. Kluff uses it in two directions:

Use Kluff from other apps: connect any app that supports MCP, such as Claude, ChatGPT, Cursor or VS Code, to your workspace, then search it, check on your agents and give them work without leaving the app you're in.
Add MCP servers to Kluff: connect tools such as GitHub, Linear, Notion or Stripe through their MCP servers, so your agents, flows and canvases can use them.

Use Kluff from other apps

Any app that supports remote MCP servers with sign-in can connect to Kluff. You sign in with your Kluff account and choose one workspace, and the app can only do what you allow on that screen.

Server URL

https://mcp.kluff.com/v1

You don't need an API key. The first time you connect, the app opens a Kluff sign-in page, then asks you to choose a workspace and what the app may do.

Connect an app

Claude

In Claude, open Customize > Connectors and select Add custom connector.
Name it Kluff, paste the server URL and add the connector.
Select Connect, then sign in to Kluff and choose a workspace.

On Team and Enterprise plans, an owner adds the connector first in Admin settings > Connectors.

ChatGPT

On the web, open Plugins, select Add, then Add custom MCP server.
Name it Kluff, paste the server URL and keep OAuth as the authentication.
Add it, then sign in to Kluff and choose a workspace.

Once added, you can use it in any chat. Availability can depend on your ChatGPT plan.

Cursor

Add this to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "kluff": { "url": "https://mcp.kluff.com/v1" }
  }
}

Then open Customize > MCPs, turn on Kluff, and sign in when prompted.

VS Code

Run MCP: Add Server from the Command Palette.
Choose HTTP, paste the server URL and enter kluff as the server ID.
When prompted, sign in to Kluff and choose a workspace.

Claude Code

Run this in your terminal:

claude mcp add --transport http kluff https://mcp.kluff.com/v1

Then run /mcp in a Claude Code session and sign in to Kluff.

Other apps

Most other MCP apps, such as Windsurf, Zed, Cline, Gemini CLI or n8n, can connect the same way:

Add https://mcp.kluff.com/v1 as a remote (HTTP) MCP server.
Choose OAuth if the app asks how to sign in. Kluff doesn't use API keys for MCP.
Sign in to Kluff and choose a workspace.

If an app only runs local MCP servers, connect through the open-source mcp-remote bridge, which opens the Kluff sign-in page in your browser:

{
  "command": "npx",
  "args": ["-y", "mcp-remote", "https://mcp.kluff.com/v1"]
}

When you connect, Kluff shows which workspace the app will use and lets you choose its permissions. Every connection acts as you: it sees only what you can see in that workspace, and anything it sends shows up under your name.

Permission	On by default	What it allows
Read	Always	Read your projects, project memory, agents, their messages and runs, and pending approvals, and search the workspace
Work with agents	Yes	Create agents, send them messages and stop their runs
Approve actions and answer questions	No	Approve or deny what your agents want to do, and answer their questions

Tools

Tool	What it does
`get_current_context`	Shows who you are, the connected workspace and the permissions you granted
`list_projects` / `get_project`	Lists your projects or shows one
`search_workspace`	Searches the threads, messages and people you can access
`search_project_memory`	Searches what Kluff remembers for a project
`list_agents` / `get_agent`	Lists agents and whether they're running, idle or waiting on you
`get_agent_messages` / `get_agent_run`	Reads an agent's messages and the steps of a run
`list_pending_approvals`	Lists approvals and questions waiting on you
`create_agent`	Creates an agent in a project
`send_agent_message`	Gives an agent work
`stop_agent_run`	Stops a run
`approve_tool_call` / `deny_tool_call`	Approves or denies an action an agent paused on (approvals permission only)
`answer_ask`	Answers a question an agent asked you (approvals permission only)

Most apps ask you before they run a tool that changes something. You can usually adjust this per tool in the app's connector settings.

Things to try

"What projects do I have in Kluff?"
"Search my Kluff workspace for the Q3 launch plan."
"Which of my Kluff agents are waiting on me?"
"Ask my research agent in Kluff to summarize this week's customer calls, then show me its reply."

Advanced: approvals from other apps

Approve actions and answer questions is off by default. Turn it on when you connect if you want the app to approve or deny your agents' actions and answer their questions for you. Only turn it on for an app you trust to act for you, because an approval can change records or send messages in your other tools. You can still review everything in Kluff's approvals.

Disconnect an app

Open Settings > MCP connections in Kluff to see every app you've connected, which workspace it uses and when it was last used. Select Disconnect to remove one. It loses access right away, and you can connect it again at any time.

Add MCP servers to Kluff

Many tools publish an MCP server. Add one to your workspace and its tools become available to Kluff alongside your other integrations.

Connect a listed server

The Integrations page lists more than 100 MCP servers you can add in one click, including GitHub, GitLab, Linear, Notion, Asana, HubSpot, Attio, Stripe, Shopify, PostHog, Sentry, Datadog, Figma and Calendly.

Open Integrations and find the tool.
Select Connect. A few servers first ask for a detail such as a region or an API key, which is saved as a workspace secret.
Sign in to the tool and approve access.

Add a custom MCP server

If a tool isn't listed, a workspace admin can add any MCP server by URL.

Open Integrations and select Add custom MCP.
Enter a name and the server's URL. For servers that use an API key instead of sign-in, add a header such as Authorization: Bearer ${API_KEY}, where API_KEY is the name of a workspace secret. Kluff fills in the value when it connects, so the key never appears in the server's settings.
Save. Kluff checks the connection and lists the server's tools. If the check fails, you can try again or connect anyway.

Admins can also add a local server that runs as a command. These only work inside agents.

Connect your own account

Adding a server makes it available to the workspace, but each person connects their own account. Select Connect on the server and sign in, or review the server's settings first if it doesn't use sign-in. Your agents then act as you in that tool.

You can share your connection with teammates or groups so they can use it without their own account. If an admin edits a server, people need to connect again before their agents use the new settings.

Use MCP tools

Agents get the tools of every MCP server you've connected, in any project. You can mention a server with @ in chat to point the agent at it, but you don't have to. To keep a server out of one project, turn it off in that project's settings under Integrations.
Flows can run an MCP tool as a step, and can start from a read-only tool that checks for new or changed records. Use Test step to see what a tool returns before you rely on it.
Canvases can read data and run actions through MCP tools as the person viewing them.

Flows and canvases need a remote server on a public https:// address. Local servers and localhost addresses only work inside agents.

Keep control

Only workspace admins can add, edit or remove MCP servers.
Each person decides which servers they trust by connecting them, and their tools are only used with their own access.
Per-tool approvals for integrations don't apply to MCP tools. Connect only the servers your work needs, and turn them off for projects that shouldn't use them.

Troubleshooting

The sign-in page doesn't open: allow pop-ups for the app, then connect again.
You can't choose a workspace: you can only connect workspaces you're a member of.
A tool you expected is missing: reconnect and check the permissions on the Kluff screen. Approval tools only appear when you turn them on.
A tool says it isn't permitted: the app's connection doesn't include that permission, or your Kluff role doesn't allow the action.
An MCP server's tools don't appear for an agent: check that you've connected your own account to it on the Integrations page and that it isn't turned off for the project.
A flow step fails with an MCP error: the server may be local, its connection may have been revoked, or its output may have changed since you set up the step. Open the step and select Test step.

Still stuck? Email [email protected].