xAI shipped Grok Connectors on May 6, 2026 across web, iOS, and Android. Seven first-party integrations launched on day one, plus a feature that matters more than any of them individually: Bring Your Own MCP.
That second one is the headline. xAI joining the Model Context Protocol ecosystem brings them to feature parity with Claude (which created MCP) and ChatGPT (which adopted it). For anyone evaluating which AI assistant to standardize on, the agentic-tooling gap just closed.
The Seven Launch Connectors
| Connector | What Grok Can Do |
|---|---|
| SharePoint | Search, read, synthesize files/lists/pages. With write permissions, create and edit documents (advanced editing powered by Grok 4.3) |
| Outlook | Search inbox, calendar, meetings; draft and send email; create invites; triage |
| OneDrive | Read and analyze spreadsheets, presentations, reports |
| Google Workspace | One integration covers Gmail, Drive, Docs, Sheets, Calendar (read + write) |
| Notion | Search and edit pages, databases, wikis |
| GitHub | Search code, summarize PRs, review changes, work with issues |
| Linear | Search backlog, summarize sprints, draft updates, create issues |
The Microsoft trio (SharePoint, Outlook, OneDrive) is shipping at the same time as the Google trio (Workspace's Gmail/Drive/Docs/Sheets/Calendar bundle). That is notable. Most AI products force you to pick a side because they ship one ecosystem before the other. Grok shipping both on day one is a real signal that they are going after enterprise users who are mixed-stack by reality, not preference.
The dev-tooling pair (GitHub + Linear) is the other interesting combination. That is the stack a software team actually uses, and Grok shipping both suggests they want the engineering buyer specifically.
The Bring Your Own MCP Angle
"Connect any custom Model Context Protocol server to Grok. No matter what your team uses, a homegrown knowledge base, proprietary APIs, or an internal MCP gateway, Grok can plug straight into your own tools and workflows."
This is the line that moves xAI from "third major chatbot" to "third major agent platform." MCP is the standard Anthropic introduced to let LLMs talk to external systems through a protocol rather than per-vendor plugins. By supporting BYO MCP, Grok can immediately consume any of the hundreds of MCP servers people have built for Claude over the past year.
That includes:
- ●Internal company knowledge bases wrapped in MCP
- ●Database adapters (Postgres, Snowflake, etc.)
- ●Niche tooling (Figma, Sentry, PagerDuty, internal ticketing)
- ●The growing ecosystem of community MCP servers on GitHub
If your engineering team has already built or installed MCP servers for Claude Code or ChatGPT, those servers work in Grok now too. No rewrites.
How to Enable
Web: Sign in, click the + button, select Connectors, then + Add connector.
iOS / Android: Settings → Connectors.
Get the Weekly IT + AI Roundup
What changed this week in NinjaOne, ServiceNow, CrowdStrike, and AI. One email, every Monday.
No spam, unsubscribe anytime. Privacy Policy
Authentication is per-connector. You will OAuth into each service the first time, then Grok holds the credentials for that connector going forward. Permissions are scoped per connector, so you can grant Outlook read-only and SharePoint full write access independently.
What This Means Strategically
Grok was the late entrant on agentic tooling. Claude shipped MCP in late 2024. ChatGPT followed in mid-2025. Grok shipping both first-party Connectors and BYO MCP in May 2026 puts them in the same conversation, even if a year behind on rollout.
The implications for buyers:
1. Vendor lock-in just got cheaper. If you have built MCP servers for one assistant, you can swap to another without rewriting the integration layer. That is healthy for buyers, less healthy for vendor margins.
2. The chatbot is no longer the product. The product is the agent plus connectors. Pick whichever LLM you prefer for raw quality, then bring your own toolkit via MCP. The differentiation moves to model quality, latency, price, and the small set of native connectors a vendor has actually polished.
3. Grok's strongest pitch is now stack consistency. If you are already on X for distribution, evaluating Grok Voice for support, looking at Grok Imagine for marketing creative, Connectors closes the productivity loop. One vendor, one billing relationship, one set of credentials.
4. The Microsoft + Google parity is rare. Most AI tools force a stack choice. Grok shipping both ecosystems on day one is an enterprise-friendly move worth noting if you are a mixed-stack org.
What's Still Missing
A few gaps worth flagging:
- ●No CRM connectors yet. No Salesforce, HubSpot, Pipedrive on the launch list. That is the obvious second wave.
- ●No Slack or Teams connector. Strange omission for enterprise readiness.
- ●No vertical SaaS. No Jira, no Asana, no Monday, no ServiceNow.
- ●API exposure unclear. The launch is on web/iOS/Android (the consumer Grok app). Whether Connectors are also exposed through the Grok API for building your own agents is not explicit in the announcement.
The BYO MCP support partially fills these gaps for any service that already has a community MCP server. But for first-party polish on the missing items, you are waiting on xAI's roadmap.
Bottom Line
Connectors makes Grok useful for actual work, not just chat. The Microsoft + Google ecosystem coverage on day one is genuinely strong. The BYO MCP support is the bigger story because it lets Grok inherit the entire MCP server ecosystem that the rest of the industry has been building for the past year.
If you have been holding off on Grok because "it does not connect to my tools" was the blocker, that excuse just expired. The remaining differentiators between Grok, Claude, and ChatGPT are model quality, pricing, and which native connectors each one has polished. The integration layer itself is becoming a commodity.
That is a healthier market for buyers, and a tougher one for any vendor still hoping integrations would be their moat.