Connect Covia to Claude

Give Claude a working seat at your Covia venue: it can run operations, create and task your agents, read your workspace, and answer approvals - every action signed under a grant you approve, and recorded as a job on your venue.

Setup time ≈ 5 minutes

Every screen below is a clean recreation of the interface - not a screenshot - so nothing here contains real account content.

Add the connector in Claude

In claude.ai open Settings → Customize → Connectors. Click Add → custom connector and enter:

https://connector.covia.ai/mcp

If Covia Labs is already listed (perhaps with a warning icon), click Reconnect instead - same flow.

claude.ai → Settings → Customize → Connectors

Covia Labs Web · CustomReconnect

Or: Add ▾ → Custom connector → paste the URL aboveAdd

The consent page opens - check the identity first

Claude sends you to the connector's consent page. Under 2 · Your identity it may already show a key stored by your browser. This is where mistakes happen: if the DID shown doesn't match your Covia dashboard identity, Claude will operate a different, empty account.

If it shows nothing, or a DID you don't recognise: click Forget, and get your real key in step 3.

connector.covia.ai/authorize?…

The key is stored only in your browser and signs the grant locally - it never reaches the connector.

Copy your device key from the dashboard

In another tab, open app.covia.ai → Profile. The Identity panel shows your DID and a masked private key. Click the copy button - the key goes to your clipboard without being displayed.

app.covia.ai/profile

Your Identity on your venue

DID did:key:z6Mk…<your identity - remember the last few characters>

Private key

••••••••••••••••••••••••••••••••👁⧉ copy

Anyone with this key can act as you. Never share it.

Treat the key like a password. Paste it only into the consent page. Don't put it in a chat, a note, or a screenshot - and store a copy in your password manager, because it otherwise lives only in this browser.

Import it and verify the DID matches

Back on the consent page: paste into the key field, click Import, and confirm the line now reads You are did:key:… with the same ending as your Profile page. Same string, same identity - your workspace, agents, and secrets now travel with the connection.

Paste the key, not the DID. Two different things live on your Profile page: the DID (starts with did:key:z6Mk…, public, safe to share) and the private key (64 characters of 0-9 a-f, masked, secret). Import wants the private key - use the copy button next to it. If you paste the DID, the page now tells you exactly that.

Choose what Claude may do, and for how long

Each row is a capability in the signed grant - the venue enforces exactly these, nothing more. Defaults are sensible; the two off-by-default rows are the more consequential ones. Pick a duration (the grant expires by itself; reconnecting renews it) and click Approve. Your browser signs the grant and returns you to Claude.

connector.covia.ai/authorize?… · 3 · What Claude may do

Connected - Claude asks before each tool the first time

Claude confirms “Connected to Covia Labs” and lists the tools with per-tool permission controls. In a chat, the first use of each tool shows a prompt - Allow once keeps you in the loop; Always allow suits read-only tools you trust.

claude.ai - in a conversation

Claude wants to use Create an agent from Covia Labs

DenyAlways allowAllow once

Try it: create an agent

Say: “Create an agent called bob on my Covia venue, then list my agents to confirm.” The reply names bob's address under your DID, and the job receipt link opens the signed record on your venue - your audit trail, on your infrastructure.

claude.ai - Claude's reply

bob is created and confirmed - it's the only agent on the venue.

Address: did:key:z6Mk…<you>/g/bob
Status: SLEEPING
Job receipt: 0x01a03d22…4033

And in your dashboard, under Agents:

app.covia.ai/agents

bob
SLEEPING · 0 tasks

Optional: let agents think - add your model key

Chatting with agents runs on your model account. At app.covia.ai → Secrets (signed in with the same device key), add your provider key under its conventional name - the connector never sees it:

Provider	Secret name
Anthropic (Claude models)	`ANTHROPIC_API_KEY`
OpenAI	`OPENAI_API_KEY`
Google	`GOOGLE_API_KEY`

If something looks wrong

Symptom	Cause & fix
Workspace or agent list is empty, but the dashboard isn't	Claude is connected as a different identity. Redo steps 2–4: Forget, then Import your dashboard key. The DIDs must match exactly.
“Not permitted … reconnect and tick the capability”	The grant doesn't include that capability. Disconnect and reconnect, ticking the named row - a signed grant can't be edited, only replaced.
Agent chat returns a provider or API-key error	No model key stored for this identity. Do step 8 - with the same device key.
Everything stopped working after some days	The grant expired (by design). Reconnect; pick a longer duration if that suits you.
Clicking Import shows a red message (or used to do nothing)	You pasted the DID or an incomplete string. Import needs the 64-character private key - Profile → Private Key → copy button (step 3).
Not sure what Claude can do	Ask Claude: “use covia_help” - the connector answers setup and troubleshooting questions itself.

The connector (connector.covia.ai) holds no user keys, venue secrets, or files. It acts under the grant you signed; the venue checks every call; receipts link to immutable job records on your venue. Disconnect in Claude's settings - or let the grant expire - and the connection is powerless.