Connect Claude Code

Connect Claude Code to your workspace memory. The server is https://agentics.you/mcp, named agentics in every tool, so an admin can allowlist one name.

One click from the desktop app

In the Agentics desktop app, Connect your agents lists Claude Code with its state. Nothing changes until you confirm.

1. Click Connect. Before anything changes, the app shows what it will do: “Add Agentics to Claude Code for your user, in all your projects.” With it are the command it runs and the file it changes.
2. Click Confirm. The app saves a backup of the file beside it (<file>.agentics-backup-<timestamp>, readable by you only), runs claude mcp add --transport http --scope user agentics https://agentics.you/mcp, then runs claude mcp list to check that agentics is there.

If Claude Code isn't installed, its row says so and offers nothing to click. Once it has agentics, the row says Connected and offers Disconnect.

The app is for macOS and Windows. Get it from Download, which lists each build once a release is published.

By hand

Run this in a terminal. It is the command the app runs:

claude mcp add --transport http --scope user agentics https://agentics.you/mcp

The entry it writes to ~/.claude.json includes:

{
  "mcpServers": {
    "agentics": {
      "type": "http",
      "url": "https://agentics.you/mcp"
    }
  }
}

If CLAUDE_CONFIG_DIR is set, the file is .claude.json in the folder it names.

~ is your home folder.

Sign in

Sign in from Claude Code: run claude mcp login agentics in a terminal, or type /mcp in a session and choose agentics.

A console API key (ak_…) does not work here. Production answers HTTP 401 {"error":"invalid_token"} to one.

Until you sign in, claude mcp list shows ! Needs authentication. That is the server's 401, not a bad address.

Without a browser

A machine that can't open a browser sends an agent key (agk_mcp_…) instead of signing in. Create one under API keys, Agent keys: it is shown once. Keep it in the environment, not in a file you commit.

claude mcp add --transport http --scope user agentics https://agentics.you/mcp --header "Authorization: Bearer ${AGENTICS_AGENT_KEY}"

Check it worked

Run claude mcp list. It lists agentics at https://agentics.you/mcp.

Then ask your agent to use it:

remember answers with saved true and a receipt_hash. recall returns that memory in results. Open the verify_url: the check does not show the memory's text.

A claude -p run cannot open the sign-in itself. Sign in once in an interactive session first, or use an agent key.

Disconnect

In the desktop app, click Disconnect, then Confirm. It backs up the file, runs claude mcp remove --scope user agentics, then runs claude mcp list to check that agentics is gone.

By hand, run:

claude mcp remove --scope user agentics

If your organization manages Claude Code

Before it changes anything, the app reads these files. One that blocks agentics stops the connect: the row says “Blocked by your organization's policy” and names the file. One that already provides agentics means there is nothing to add. A file that exists but can't be read stops the connect too.

• Claude Code's managed MCP file. When it exists, Claude Code loads only the servers it lists, and none when the list is empty. The app looks at /Library/Application Support/ClaudeCode/managed-mcp.json on macOS, C:\Program Files\ClaudeCode\managed-mcp.json on Windows and /etc/claude-code/managed-mcp.json on Linux.
• Claude Code's managed settings. deniedMcpServers can block agentics, allowedMcpServers can leave it out, and managedMcpServers can provide it. The app looks at /Library/Application Support/ClaudeCode/managed-settings.json on macOS, C:\Program Files\ClaudeCode\managed-settings.json on Windows and /etc/claude-code/managed-settings.json on Linux.

What the app can't check

• Server-managed settings and MDM profiles aren't visible on this computer. claude mcp list shows a server they block.

If it does not connect

More errors are on Connect any MCP client.