Connect agents

A connection gives one agent access to your docs. This page explains the three connection modes and the Agent writes setting. It also tells you how to check and revoke a connection.

An agent reads your docs through a connection. A connection has these parts:

Make one connection for each agent. Then each agent has its own name, its own activity and its own revoke action.

kmem serves agents over MCP, the Model Context Protocol. The MCP endpoint of your org is its address followed by /mcp, for example https://acme.kmem.app/mcp. The MCP tab in Connect shows it.

Read and propose is the default mode. It is the right choice for most agents.

Choose Read only for an agent that only answers questions.

Choose Read, propose and write for an agent that you trust to keep docs up to date without a person in between. kmem keeps every version of each doc. You can undo all changes of such a connection from its menu. Read Undo the changes of a connection.

Agent writes is an org setting. It decides if any connection can write without a person in Review.

A new org starts with Agent writes off, unless its creator turned it on. Every org that existed before this setting starts with it off.

When the setting is off, the New connection form gives the reason. It says Agent writes are off for this org, so this choice is not available. An owner or an admin sees Turn on agent writes in Settings. Another member sees Ask an owner or an admin to turn on agent writes.

A connection that somebody made with Read, propose and write acts as Read and propose while the setting is off. Its row says so in Connections. When an owner turns the setting on again, the connection can write again.

Only an owner or an admin can change the setting. Read Agent writes.

A connection reads only the docs that are Open. The New connection form shows this as Docs it can read: Docs marked Open.

A connection also follows the access of the person who made it:

Control who can read a doc explains the levels.

When you create a connection, choose Expires:

An expired connection stops at once. For an agent that uses a token, create a replacement. For ChatGPT, Claude and the Gemini web app, connect again from the client. kmem gives these clients no refresh token.

The MCP tab in Connect lists the clients in this order: ChatGPT, Claude, Claude Code, Cursor, Codex, OpenCode, OpenClaw, Hermes, DeepSeek Harness, Gemini and Other.

kmem has tested Claude Code and Codex. The MCP tab marks every other client Not yet tested with kmem. The steps for those clients come from the documentation of each client.

This procedure is for a client that uses a token. For ChatGPT and Claude, the client creates the connection when you sign in.

kmem creates the connection and shows its setup:

Copy the token now. kmem shows the token only one time. After you reload or close the page, kmem cannot show the token again. kmem stores only a fingerprint of the token, not the token.

To connect another agent, select Create another connection. If you did not copy the token of the current connection, kmem warns you first.

The setup prompt and the token are credentials. Give them only to the agent that the connection is for. Keep them out of shared files, chat rooms and logs.

The Connection check panel shows if the agent reached kmem. It has three checks under You are connected when…:

Each check changes from Waiting to Complete, with a time. When all three are complete, the connection shows the time of the last request, for example Connected · Last request 10:42.

If kmem says No agent request has arrived. Check the endpoint and access method, then try again., the agent did not reach kmem. Check the endpoint, the token and the steps of the client. Then send the check prompt again.

To check a connection later, open Connections, open the menu of the connection, and select Check connection.

When the check is complete, kmem offers a Starter prompt. Select Copy starter prompt and send it to the agent. The agent then proposes a first doc.

Select Connect, then Connections. The tab shows the number of active connections.

The list shows each connection with these columns:

Owners and admins manage the connections of the org.

The menu of a connection can have these items:

kmem says Connection renamed. Agents that use the connection continue to work. Every record from now on uses the new name.

Revoke a connection when an agent must stop its access, for example when somebody loses a laptop.

kmem says Connection revoked. The agent loses access on its next request. The docs and the proposals of the agent stay.

You cannot undo a revoke. To connect the agent again, create a new connection.

A connection with Read, propose and write can change docs without a person. You can reverse all of its changes at one time.

kmem removes the docs that the connection added. It puts the docs that the connection edited back to their earlier version. The history of each doc keeps every version.

If a person changed a doc again after the connection edited it, kmem does not change that doc. The dialog lists such docs.

When a person leaves the org, or an owner or an admin removes that person, every connection of the person in that org stops. kmem revokes those connections at once. This includes connections with no expiry.

If the person joins the org again later, the old connections stay revoked. The person must create new connections.

A password change does not stop agent connections.

Each file is in your home folder, not in a project. A project file can go into a shared repository, and the configuration holds your token or names the variable that holds it.

KMEM_TOKEN is the environment variable that holds the token of the connection. Set it in the environment that starts the client.