# Connect Hark — Meta Muse (Custom Connector)

Muse connects to Hark over its web API. You give Muse a Hark access key and the address of Hark's API description; Muse works out the rest.

1. In Hark, open Connections and create an access key. Start with a read-only key; switch to read + write once you trust it.
2. In Muse, add a Custom Connector. Store the Hark access key in Muse's Secure Credentials Store, sent as the header Authorization: Bearer <your key>.
3. Point the connector at Hark's API description (the address below).
4. Test it: ask Muse "read my project brief for V-032" (use one of your project codes).

API description:

```
https://harkstudio.io/api/v1/openapi.json
```

> Anything Muse writes — decisions, notes, Current state changes — arrives in Needs you as a suggestion, labelled "via Muse". Nothing is agreed until you accept it.

[Read the API reference](/api)

## 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.