Hark
HOW IT WORKSCONNECT YOUR TOOLS
Back to Connect
Connect

Connect Gemini CLI or any MCP client to Hark

Use Hark's MCP endpoint with Gemini CLI or any other MCP client so it reads your project brief and proposes notes for your approval.

MCP endpoint
https://harkstudio.io/mcp

Sign in to Hark to connect a client. Personal tokens and per-account details live inside the app.

Gemini CLI and other MCP clients

Any remote Streamable HTTP MCP client with OAuth works.

Any client that supports remote Streamable HTTP MCP with OAuth works: point it at https://harkstudio.io/mcp with OAuth enabled.

For Gemini CLI, add an entry under mcpServers in ~/.gemini/settings.json using the HTTP URL field. Check Gemini CLI's current docs for the exact key name before relying on it.

Endpoint
https://harkstudio.io/mcp

If a client cannot do OAuth, use a personal access token as a Bearer header instead — see the headless page.

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.

What Hark keeps clear

Evidence on every line

Every record shows Agreed / Observed / Proposed and a source you can open: where did this come from? Agreed means accepted, not independently verified. Observed is reserved for system evidence such as a merged pull request. An agent's claim is never shown as verified simply because it was accepted.

Learn more about Evidence on every line

Repo-native rules

Once linked and selected as the source, the repo's CLAUDE.md or AGENTS.md is authoritative. Hark mirrors it on pushes and retains history rather than authoring competing edits. Optional .hark/ export carries accepted handoff state and decisions into the repo. Repo activity suggests drafts with commit evidence. Agent briefs include mirrored instruction documents and linked repo metadata. Arbitrary repo-document browsing is not exposed by the current tools: Hark never serves source code. Automatic session hooks and compaction protection in the Hark mod are Claude Code-only; other tools follow their connection guide and explicit session tools.

Learn more about Repo-native rules

Scoped, expiring agent access

New agent keys default Propose: suggest changes, never approve them. An eight-character pairing code expires after 15 minutes and works once; no key is pasted into a setup chat. One-link agent approval asks you to sign in, choose permissions, projects and expiry, then approve. The agent still completes pairing. Keys normally expire after 90 days and can be revoked or rotated. The separate show-once Copy key path is for private storage, not chat.

Learn more about Scoped, expiring agent access
SIGN IN TO CONNECT