Connect your tools to Hark

1. If the agent can add a remote server by address, use https://harkstudio.io/mcp and sign in.
2. Otherwise, give it Hark's web API: base address https://harkstudio.io/api/v1, the API description at https://harkstudio.io/api/v1/openapi.json, and an access key sent as Authorization: Bearer <your key>.
3. Start with a read-only key. Always-on agents can read briefs, projects, decisions and what needs you all day without hitting limits; writes are refused until you switch to a read + write key.

The session flow

• Before working on a project, read its brief (GET /projects/{code}/brief, or start a session).
• Record decisions in Hark as suggestions; a person accepts them.
• Never mark work done without evidence.
• End with a handoff note (POST /projects/{code}/sessions/end). Send the same X-Hark-Conversation header on every call so they share one session.

Verify it works

Ask your client: "List my Hark workspaces." Expected: your workspace names.

Then: "Create a project called Connection test in <workspace>." Expected: a new V-### appears in the app and the activity log shows the source ("via Claude Code", "via Codex", etc.). Delete the test venture afterward.

Troubleshooting

• "Unauthorized request origin" — the client origin isn't allowlisted; retry from the latest app version, or email hello@harkstudio.io.
• Consent screen loops / stale token — remove the connector in the client, sign out of Hark, sign back in, re-add the connector.
• Tools list is empty — the connector isn't enabled for this chat (Claude and ChatGPT require enabling it per conversation).
• Plan cap error — you've hit the monthly agent-call cap for this workspace; see billing.
• Old endpoint — anything pointing at a lovable.app URL must be updated to harkstudio.io/mcp.