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.
https://harkstudio.io/mcp
Sign in to Hark to connect a client. Personal tokens and per-account details live inside the app.
Paste the URL into Connectors, sign in, approve.
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.
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.