Hark
HOW IT WORKSCONNECT YOUR TOOLS
Connect

Connect your tools to Hark

Pick the AI tool you use below and follow the steps — usually a button or one line. Once connected, every tool reads the same current state and leaves a note when it's done, so the next one picks up where the last left off.

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.
SIGN IN TO CONNECT