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.

Muse Code

Add Hark's address as a remote server, then sign in from the browser.

Muse Code connects the same way as Codex: add Hark as a remote server by its address, then sign in when your browser opens.

Server address
https://harkstudio.io/mcp

If Muse Code can't sign in through a browser, create an access key in Connections and send it as Authorization: Bearer <your key>.

Start every session by reading the project brief, and end it with a handoff note so the next tool picks up where you stopped.

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