Skip to content
KRPUS
Sign up

SET IT UP

Four steps to an agent on a leash.

A few minutes, most of them spent deciding what the agent may touch.

  1. 1Create a bundleOne folder of memory for one subject. Start free; go Pro when you need more room.
    Platform architecturebundle · fra.korpus.cloud
  2. 2Create an agent, set its leashName it, give it the one bundle it needs, and in it only the paths it may write: read, create, update, delete, each ticked on its own. Nothing else, and never more than you reach. You are the person it answers to.
    agent/archivistworks for you
    • bundlePlatform architecture
    • adr/**read, create, update
    • diagrams/**read, create, update
    • security/**none
  3. 3Connect twiceOnce as you (me), with you in the loop: Korpus is listed in Claude's connector directory, just search for Korpus; often quicker, add it as a custom connector. Once as the agent, in Claude Code or a CI job, signed in at its own address or with its key: it holds only its leash, so it does its job and nothing else.
    # you, to set things up: listed in Claude's connector directory, or as a custom connector
Korpus
https://mcp.fra.korpus.cloud/<username>/me

# the agent, for the daily work: Claude Code or CI, signed in or with its key
korpus-<username>-archivist
https://mcp.fra.korpus.cloud/<username>/archivist
  4. 4Ask for the jobTalk to the me connection. It sets up the agent’s leash; your AI app runs the schedule.
    you → Korpus (me)

    Schedule a routine for every morning at 7. Compare the CDK code in sources/ with diagrams/overview, fix what drifted, and draft an ADR when a decision changed. Run it as the archivist agent, not as me.

    routine drift-check · daily 07:00 · as archivist

That's it. Every morning your agent does the work, inside its leash, and each change reads @you via archivist.

CONNECT CLAUDE

Korpus in claude.ai, desktop and mobile.

One remote MCP server, signed in with OAuth. You need a Korpus account; free is enough to start.

  1. 1Add the connectorKorpus is listed in Claude's connector directory: Settings → Connectors, search for Korpus and choose Connect. Often quicker: Add custom connector, name it Korpus, paste the URL below.
  2. 2Sign in and allowClaude opens Korpus. Sign in with a passkey or an emailed code, keep it on me (you, with every right), then Allow.
  3. 3Use it anywhereA connector added on claude.ai also works in Claude for desktop and mobile. Turn it on per chat from the tools menu.

Listed in Claude. Korpus is an approved connector in Claude's connector directory; search for Korpus. Either way, directory or custom connector, Claude connects to the official Korpus server as me, you with every right.

Claude's connectors sign in through the browser. At your own address they are me; at an agent's address they are that agent, which holds only its bundles and what it may do in each, so it does its job and nothing else. For a job that sends a fixed header, an agent can also hold a key. Connect an app under Agents gives the exact setup for each; the steps are in Connect.

# you (me): custom connector named Korpus
https://mcp.fra.korpus.cloud/<username>/me
# an agent: Claude Code, an AI app or CI, signed in or with its key
https://mcp.fra.korpus.cloud/<username>/<agent>

One tool per action

  • list_folder · read_concept · search_conceptsread onlyWalk folders, read concepts, search titles and text. Claude needs no OK for these.
  • read_index · read_logread onlyEach folder's generated index (titles and descriptions) and log (what changed, why and by whom).
  • create_concept · update_concept · delete_conceptchangesWrite concepts, each with a line saying what changed. Claude asks for your OK.
  • create_bundle · create_agent · create_keychangesBundles, teams and people, agents and their keys. Only as me.

Each tool does one thing, named so you can tell what Claude is about to do. An agent sees only the bundles and paths you gave it, does only what you allowed there, and gets none of the managing tools. Every tool: API reference.

Try asking

  • List my Korpus bundles.
  • Open my runbooks bundle and summarise its README.
  • Show the open known issues in my support bundle.
  • Add a known issue: export fails on large PDFs, severity medium.
  • Write a new concept notes/deploy-checklist with the steps we just discussed.
  • Search my API catalog bundle for deprecated APIs.
  • Create a new bundle called Review check.
  • How do agents and their access work in Korpus?

Free and Pro

  • Free: Every feature: markdown concepts with type, tags and relations, full-text search, teams and shares, agents held to their bundles and paths. Your personal space and up to 3 free teams, each 5 MB of concepts and 50 MB of files, 3 bundles and 3 people.
  • Pro: The same tools with more room, for one team (a team of one too): 1 GB of concepts and 10 GB of files, up to 1000 bundles, 10 people and higher request rates.

Every plan has usage limits; Claude sees how full they are with get_usage. Pricing.

Disconnect

Remove the connector in Claude, and revoke its connection under Agents in Korpus; its tokens stop working at once.

Your data. Korpus receives Claude's tool calls and answers them; never your conversation. Hosted in Frankfurt (eu-central-1). Not for health data or PHI. See Privacy and Terms.

Help. Write to support@korpus.cloud.

Give your agents a memory your team can read.

Free to start, no card needed. For a demo or running it in your own AWS account, write to us.

Start freeGet in touch