# Give Grok a home for useful project work. Reviewed: 2026-11-04 Canonical: https://clankercloud.ai/learn/use-grok-with-clanker-workspace Use Grok with Clanker Cloud to turn research and approved Project sources into saved work your team can review. The Grok web app documents custom MCP connectors. Grok Bot and the Grok API have different setup paths; verify the route you use before sharing private data or saving results. ## What you are working toward A research brief, evidence table and next-step handoff saved in the Project. ## Start with - A Grok account with custom connectors available - A Clanker account and a Project with approved sources - A research question and the date the answer must reflect ## 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](https://docs.x.ai/grok/connectors) - [Workspace connection and permissions](https://clankercloud.ai/workspace-agents) ## 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](https://docs.x.ai/grok-bot/computer-and-apps) - [Grok API: remote MCP tools](https://docs.x.ai/developers/tools/remote-mcp) ## 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](https://workspace.clankercloud.ai/for-agents.md) - [Agent handoff starter](https://clankercloud.ai/templates/agent-handoff-pack) ## 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 using 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. ## Common questions ### Does Clanker host my Grok Bot? Connecting a Grok client through MCP does not move its process, computer or routines into Clanker. Workspace holds the sources and results saved through approved tools. Hosted agent execution is a separate setup. ### Can Grok automatically see all my company data? No. Use an authenticated connection, inspect the actual permissions and select sources appropriate to the task. Public web research and private Workspace access are different capabilities. ### Can another agent continue Grok’s work? Yes, by reading the saved sources, result and handoff through its own approved access. This transfers explicit work context, not the original private conversation or hidden reasoning. ## Sources - [Workspace connection and permissions](https://clankercloud.ai/workspace-agents) - [Live Workspace instructions for connected agents](https://workspace.clankercloud.ai/for-agents.md) - [Grok: custom MCP connectors](https://docs.x.ai/grok/connectors) - [Grok Bot: computers and connected apps](https://docs.x.ai/grok-bot/computer-and-apps) - [Grok API: remote MCP tools](https://docs.x.ai/developers/tools/remote-mcp) ## Related - [Your favorite agents. One home for the work.](https://clankercloud.ai/learn/ai-agent-integrations) - [A vendor decision with the evidence attached.](https://clankercloud.ai/templates/vendor-comparison) - [A small packet the next agent can verify.](https://clankercloud.ai/templates/agent-handoff-pack) - [Keep Claude. Give the work a cloud home.](https://clankercloud.ai/learn/use-claude-with-clanker-workspace) - [AI transformation starts with useful work.](https://clankercloud.ai/learn/ai-transformation) [Open Workspace](https://workspace.clankercloud.ai) [Current pricing and usage](https://clankercloud.ai/pricing)