How do you connect Grok to your company's own documents and tools?

Short answer

In grok.com you use connectors: built-in ones for Google Drive, Gmail, OneDrive, SharePoint, Outlook, Teams and Salesforce, catalog ones like GitHub and Notion, or your own MCP server. On Grok Business and Enterprise an admin must provision each connector first. Developers use the API instead: Collections for searchable document stores and Remote MCP for live tools.

Three routes, depending on who uses it

Route For whom What it connects Set up by
Built-in and catalog connectors Everyone in grok.com Mail, calendar, drives, CRM, code, notes Team admin, then each user signs in
Custom MCP connector Everyone in grok.com Any system you expose as an MCP server Added under Connectors; check workspace policy. Server must be public
Collections, file attachments, Remote MCP Developers on the API Your own document store and tools in your own agents Developer

Route 1: connectors in grok.com

xAI maintains built-in connectors with OAuth sign-in for Gmail and Google Calendar, Google Drive, OneDrive, Outlook Mail and Calendar, Microsoft Teams, SharePoint and Salesforce. The catalog adds pre-configured ones for Box, Canva, Gamma, GitHub, Linear, Meltwater (needs a Meltwater subscription), Notion, S&P Global and Vercel.

On Grok Business and Enterprise there is one extra step: a team admin must first provision a connector in the cloud console. Until then, members do not see it.

  1. Admin opens the cloud console and provisions the connector for the organization.
  2. Each member opens grok.com/connectors and signs in to the service with their own account.
  3. Grok then answers from that source within the member’s own access rights.

Google Drive search respects existing file permissions and answers with citations, so a person never gets an answer from a file they could not open themselves.

Route 2: bring your own MCP server

For a system that is not in the catalog, such as your ERP, ticketing tool or an internal database, you build or install an MCP server (Model Context Protocol, the open standard AI tools use to call outside systems).

  1. Open grok.com/connectors.
  2. Choose New Connector, then Custom.
  3. Enter the MCP server URL and complete the authentication.
  4. Grok discovers the server’s tools and makes them available in chats.

The server must be reachable over the public internet. For something running inside your network, xAI points to a tunneling service. Whether the admin provisioning step also applies to custom connectors is not stated in the docs; check it in your console.

Route 3: the API, for your own agents

Developers building on the Grok API have two document options and one tool option:

  • Collections is persistent document storage with semantic search, for retrieval (RAG) over larger sets. Files up to 100 MB each, in formats including PDF, Word, Excel, PowerPoint, HTML, CSV, Markdown and code. A file can sit in several collections and you can search several at once. You need credits on the account to upload.
  • File attachments on a single request, up to 512 MB per file. Grok searches them with the attachment_search tool, as often as it needs, and only agentic models such as grok-4.20 and grok-4.7 support it.
  • Remote MCP lets an API request call tools on your MCP servers: set type to mcp with a server_url and server_label, and optionally allowed_tools, authorization and headers. Only Streaming HTTP and SSE transports work. Without allowed_tools, every tool on the server lands in the context, which costs tokens.

Files and Collections require server-side storage and are unavailable while API Zero Data Retention is enabled. If personal data is involved, read is Grok safe for company data first.

Prices for search calls and storage are on what the Grok API costs.

The common misunderstanding

Connecting a source is not the same as Grok knowing your company. A connector lets Grok search a document when someone asks. A connector can retrieve facts like the current price list or a customer’s special payment term if they are recorded in an accessible source; connecting a source does not guarantee that Grok retrieves the current version or applies the right rule. Much of that knowledge lives in people’s heads and in corrections they make in chat, and a correction in a personal chat does not become a shared team rule.

What this means for a team

You end up wiring the same sources several times: once for Grok, again for Claude or ChatGPT, again for Copilot, again for each in-house agent. Separately configured connections do not automatically share corrections and working rules, although several tools can use the same source or MCP server. The background on giving agents company context is in how to give AI agents your company context.

Where Bombos fits

Bombos connects your mail, documents and repos once and gives every AI tool your team uses, Grok included, the same shared memory on top: team knowledge and the rules your team has learned, with a trace of what each answer rests on. It runs in our cloud or on your own server, and one person can try it first with their own agents.

Related questions

Does Grok connect to Slack?

The connector reference does not list Slack, but xAI's business page advertises a Slack integration. Check its availability in your workspace; a custom MCP connector is another route.

Can Grok reach a server inside our network?

Not directly. A custom MCP connector must be reachable over the public internet; for a local server xAI points to a tunneling service.

Does Grok respect file permissions in Google Drive?

Yes. The Google Drive integration searches at document level and respects existing file permissions, so people only get answers from files they can open.

Are documents in Collections used for training?

No. xAI's Collections documentation says user data stored in Collections is not used for model training.

Sources

  1. xAI docs: Connectors
  2. xAI docs: Using Collections
  3. xAI docs: Remote MCP tools
  4. xAI docs: Files
  5. xAI: Grok for Business
  6. xAI docs: API security
The first half hour · free

What does your AI forget?

  1. 01You tell us which AI you use and where it keeps starting over.
  2. 02We show what a shared memory changes there, on your own examples.
  3. 03You keep the plan, with or without Bombos.
Piet Baudoin
Piet BaudoinYou talk to Piet, from the Bombos teamDutch team from Utrecht and Nijmegen · data in Europe
We reply the same working day.