Give your agents a memory that outlives the session.

Create an account below to set up a beta workspace. After sign-in, profile completion and verification, you can finish setup on a free, non-expiring plan with no billing details required. Then point your agents at it using the setup steps that appear here.

Before you connect

Choose a compatible client

HeurChain supports MCP OAuth and API-key connections. Signing in with Google or GitHub here opens your website account; an MCP app requests its own permission to access your workspace.

For an OAuth-capable MCP client, use https://api.heurchain.com/mcp/sse and follow its connection flow. Initial OAuth connectivity has been verified; refresh, revoke/reconnect and Gemini web/mobile compatibility still need end-to-end validation.

API-key clients can continue using SSE with X-HeurChain-API-Key and X-HeurChain-Tenant, or the REST API. These values are not an OAuth Client ID or Client secret. See connection details.

Set up your beta workspace

Already have an account? Sign in to continue. Use your existing sign-in method.

Using Google or GitHub? We'll ask for your name and referral source right after you return.

or register with email

Your workspace is live

Credentials

Copy these now. The API key is shown once — if you lose it, rotate a new one from the dashboard.

Tenant ID

—

API key

—

Treat the API key like a password. It carries full read/write access to your workspace, and anything your agents store is readable by anything else holding it.

Point your agent here

Paste this to your agent

One block. It carries your credentials and the full setup protocol — storing them, verifying the connection, installing the skill, and the settings that matter. Paste it into Claude Code, Hermes, OpenClaw, or any agent that can run shell commands, and it will configure itself.

These examples use API-key authentication. OAuth-capable MCP clients use the same MCP endpoint with a separate workspace authorization flow. The API key and tenant ID below belong in HTTP headers, not OAuth fields. Gemini web/mobile compatibility remains unverified.

Contains your API key — paste only into your own agent.

Loading…

Treat this block like a password. The key it contains carries full read/write access to your workspace. If it leaks, rotate it from the dashboard — the old key is revoked immediately.

Your workspace, usage, and per-agent controls live on the dashboard. Questions during the beta: [email protected].