# Connect Hark — Grok (chat app)

1. Open grok.com → Settings → Connectors (grok.com/connectors).
2. Choose New connector → Custom.
3. Name: Hark. Server URL: https://harkstudio.io/mcp. Save / Add connector.
4. Grok opens the Hark sign-in — sign in and approve the connection.
5. In a conversation, enable Hark (or just name it: "Use Hark to list my workspaces").

MCP server URL:

```
https://harkstudio.io/mcp
```

> On Grok Business/Enterprise, custom connectors are provisioned by an admin in console.x.ai → Grok Business → Connectors before they appear for members.

> xAI's remote MCP does not support require_approval, so writes run without a confirmation step. Start with a read-only Hark token (Connections → Tokens) and switch to read + write once you trust the flow.

> Grok Build and Grok Bot carry no separate app identity, so Hark labels their activity from the connection: OAuth connections show as Grok Build or Grok, and token-based runs show the token's name — name the token Grok so the activity log reads clearly.

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