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.
Connect your AI assistant to Koop. It does the compliance work in your account and shows you every change before it makes it.
Add Koop as a custom connector, then sign in with your normal Koop login. You don’t need an API key or an install.
claude mcp add --transport http koop https://mcp.koop.ai/client/mcp, then /mcp to sign in.Step-by-step setup for each app. It takes about two minutes.
Paste Koop’s address into your assistant’s connector settings.
Approve what your assistant may do: read, make changes and draft documents. It acts as you, with your role.
Your assistant reads the right skill, does the work and shows you a preview of each change. Then it waits for your OK.
Most of what you can do in the portal, in a conversation.
See progress in every framework, what’s still open and who owns it, and get a weekly report.
From your repository, GitHub settings and connected systems, with every gap listed before anything is filed.
Draft from what’s actually configured, take each version through approval, and remind people who haven’t signed.
Vendors, assets, employees and training, reconciled with your HR system, MDM and cloud accounts.
Your assistant suggests likelihood, impact and a treatment for each risk event. You agree them, then it saves them.
A System Security Plan or Description of System from your code, with a source for every statement, for a person to review.
See your policies, coverages and limits, answer an application, and accept a quote. Payment stays in the portal.
Add contracts and track their requirements, answer Trustcheck requests and, if you’re an admin, prepare and publish your Trust Center.
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.
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 sees only what your role can see in the portal, and what it files shows your name.
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 each preview and each confirmed change with your Koop user and the time.
Uploads and downloads use single-use links, so file contents don’t pass through the conversation.
In the Koop portal, go to Settings › API › Connected Apps and choose Revoke. If your role can’t open Settings, email support@koop.ai.
Koop marks text from your files as data and tells your assistant never to follow instructions in it.
Add the connector from your terminal, then run /mcp, choose koop and sign in.
Add Koop as a remote MCP server with the connector address, then sign in with Koop when the editor asks.
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.
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.