Koop MCPDocs

Overview

Get started with Koop MCP

Connect your AI assistant to Koop. It does the compliance work in your account and shows you every change before it makes it.

Start here

Add one address to your AI assistant

Add Koop as a custom connector, then sign in with your normal Koop login. You don’t need an API key or an install.

Koop connector address
https://mcp.koop.ai/client/mcp
In Claude Code, run claude mcp add --transport http koop https://mcp.koop.ai/client/mcp, then /mcp to sign in.

Choose your AI assistant

Step-by-step setup for each app. It takes about two minutes.

How it works

Step 1

Add the connector

Paste Koop’s address into your assistant’s connector settings.

Step 2

Sign in with Koop

Approve what your assistant may do: read, make changes and draft documents. It acts as you, with your role.

Step 3

Ask in your own words

Your assistant reads the right skill, does the work and shows you a preview of each change. Then it waits for your OK.

What your assistant can do in Koop

Most of what you can do in the portal, in a conversation.

Run your compliance program

See progress in every framework, what’s still open and who owns it, and get a weekly report.

Collect and file evidence

From your repository, GitHub settings and connected systems, with every gap listed before anything is filed.

Write and approve policies

Draft from what’s actually configured, take each version through approval, and remind people who haven’t signed.

Keep inventories current

Vendors, assets, employees and training, reconciled with your HR system, MDM and cloud accounts.

Score your risks

Your assistant suggests likelihood, impact and a treatment for each risk event. You agree them, then it saves them.

Draft system documents

A System Security Plan or Description of System from your code, with a source for every statement, for a person to review.

Work with your insurance

See your policies, coverages and limits, answer an application, and accept a quote. Payment stays in the portal.

Handle contracts and your Trust Center

Add contracts and track their requirements, answer Trustcheck requests and, if you’re an admin, prepare and publish your Trust Center.

Skills come built in

Koop’s 19 skills tell your assistant how to do each job in Koop, step by step. They come with the connector, so there is nothing to install. Just ask.

You stay in control

Your assistant works under your name, so Koop keeps it inside your permissions and gives it a preview of each change to show you.

It signs in as you

It sees only what your role can see in the portal, and what it files shows your name.

It previews changes

Koop makes a change only when your assistant sends back the exact preview it showed you, and only if nothing changed since. Keep your assistant’s approval prompts on for Koop.

Koop logs every change

Koop logs each preview and each confirmed change with your Koop user and the time.

Files stay out of the chat

Uploads and downloads use single-use links, so file contents don’t pass through the conversation.

Disconnect any time

In the Koop portal, go to Settings › API › Connected Apps and choose Revoke. If your role can’t open Settings, email support@koop.ai.

Your files are data, not instructions

Koop marks text from your files as data and tells your assistant never to follow instructions in it.

Your assistant can’t

Do anything your role can’t do in the portal
Make a change before showing it to you and getting your OK
Acknowledge a policy for you
Pay for insurance or see payment details
Create, change or delete API keys
Approve and publish a policy in one step

Other ways to connect

Claude Code

Add the connector from your terminal, then run /mcp, choose koop and sign in.

>_
Terminal
$ claude mcp add --transport http koop https://mcp.koop.ai/client/mcp
Full Claude Code steps

Cursor and VS Code

Add Koop as a remote MCP server with the connector address, then sign in with Koop when the editor asks.

Cursor
~/.cursor/mcp.json
{ "mcpServers": { "koop": { "url": "https://mcp.koop.ai/client/mcp" } } }
VS Code
.vscode/mcp.json
{ "servers": { "koop": { "type": "http", "url": "https://mcp.koop.ai/client/mcp" } } }

Scripts and CI

Scripts can send a Koop API key instead of signing in. The key needs the koop:read scope, plus koop:write to make changes, and it acts as the person who created it. The portal can’t set scopes on a new key yet, so email support@koop.ai for help.

>_
Terminal
$ claude mcp add --transport http koop https://mcp.koop.ai/client/mcp \ --header "Authorization: Bearer YOUR_KOOP_API_KEY"

For auditors

Auditors use a separate connector, Koop Audit, at https://audit-mcp.koop.ai/mcp. Sign in with your auditor portal login. It works only on audits of clients whose Koop account has AI assistants turned on.

Questions

What does Koop MCP cost?
Get more informationGet more information
Which AI assistants work with Koop?
Get more informationGet more information
Is my Koop account ready?
Get more informationGet more information
Can my assistant change things without me?
Get more informationGet more information
Do I need an API key?
Get more informationGet more information
How do I disconnect?
Get more informationGet more information

More resources