Give Grok a home for useful project work.

Connect from Grok’s web app

Open grok.com/connectors, choose New Connector → Custom, and enter https://workspace.clankercloud.ai/mcp. Complete browser authorization and review the permissions in Clanker. Organization administrators may need to provision the connector first.

Use the connection in the intended conversation. Ask for workspace_status before reading files, then confirm the available tools and permissions. A visible connector is only the start; check that this client can actually read an approved file.

Sources: Grok: custom MCP connectors · Workspace connection and permissions

Using Grok Bot or building with the API?

Grok Bot documents adding a custom MCP server by URL and completing app sign-in. Its own computer, routines and saved state remain separate from Clanker Workspace.

For builders, the Grok API documents remote MCP with a server URL and authorization token. That is a different integration from interactive browser OAuth; your application must handle approved authentication and enforce tool access. Do not assume a web-app connection automatically authorizes an API request.

Sources: Grok Bot: computers and connected apps · Grok API: remote MCP tools

Keep public research beside your own evidence

For a supplier review, put proposals and your criteria in a Project. Ask Grok to compare those files with dated public documentation when its research tools are available. Save research-brief.md and supplier-evidence.csv with a source, access date and unresolved question for each important claim.

Keep supplier statements, public findings and your own requirements separate. A public search result does not establish your contract terms, internal prices or project status. Ask for “not stated” when the supplied evidence leaves a gap.

Review the result in Clanker Cloud

Approve Edit only when you want saved files. Follow the current managed Session instructions before changes, then read back the saved files and open them in Workspace. Check the brief against the actual sources before making a decision.

Save handoff.md with the chosen criteria, current results and next question. A later authorized agent can read the handoff to draft an update or revisit the comparison; it does not inherit Grok’s private chat.

Sources: Live Workspace instructions for connected agents · Agent handoff starter

Start with one checked task

This guide describes documented client routes, not a completed Grok-to-Clanker business run or an official Grok listing. Verify browser sign-in, a source read and a saved-file readback on the client version you use.

Grok usage and Clanker-hosted work have separate costs and provider policies. Connected data is sent through the services involved in the task; keeping the result in Clanker does not make all processing local or sovereign.

Before you use the result.

• The chosen Grok surface is authenticated to the intended Clanker account.
• The brief distinguishes Project evidence from dated public research.
• Every claimed deliverable can be opened in Workspace.
• The handoff identifies the next step and missing information.