How to connect SharePoint to Grok Bot
Connect SharePoint to Grok Bot with ClawLink in one click — 86 tools your AI agent can call from chat via hosted OAuth. No API keys, no manual setup.
SharePointOAUTH2MCPBrowse sites, lists, and files in SharePoint. Once connected, Grok Bot can read and act on SharePoint from chat — pairing, token refresh, and tool wiring handled for you.
Grok Bot runs on its own cloud computer, so most SharePoint guides send you to register an OAuth app and paste keys into a sandbox that resets. ClawLink gives Grok Bot a more practical SharePoint setup: it runs one CLI command, you approve once in the browser, and Grok Bot can call real SharePoint actions from chat with no auth, token refresh, or tool wiring to build yourself.
Copy this prompt into Grok Bot. It runs the ClawLink CLI in its own terminal and pairs your account.
Set up ClawLink for me and tell me when it's ready.
1. Pair this machine. It prints an approval link, so show me the link and stop, don't wait:
npx -y @useclawlink/cli login
2. I'll approve it in my browser, then reply "approved".
3. When I say approved, connect the app:
npx -y @useclawlink/cli connect sharepoint
4. Then run `npx -y @useclawlink/cli whoami` and tell me whether ClawLink is ready.Setup
It takes three steps to connect Grok Bot to SharePoint.
1Pair from the terminal
Ask Grok Bot to run the ClawLink CLI. It prints a link you approve once in your browser:
npx -y @useclawlink/cli login- 2
Connect SharePoint
One-click OAuth in the dashboard.
- 3
Use it from chat
Ask Grok Bot: "What can you do with SharePoint?"
Install by command
The prompt above does all of this. By hand, it is two commands Grok Bot runs in its own terminal, and one browser approval:
npx -y @useclawlink/cli login # prints an approval link, approve it in your browser
npx -y @useclawlink/cli connect sharepointPair once and it sticks: the key is written to ~/.clawlink/credentials.json inside Grok Bot's sandbox, so it survives between sessions. Prefer native tools over shell commands? Add https://claw-link.dev/api/mcp as a custom connector at grok.com/connectors and approve the ClawLink sign-in. Same account, no CLI.
Verify the connection by asking Grok Bot:
Use SharePoint to share point add attachment to list item and walk me through the result in plain English.
Using a different agent?
The CLI above is not specific to Grok Bot. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account the same way:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once SharePoint is connected in the dashboard, that agent calls the same 86 SharePoint tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
SharePoint MCP for Grok Bot
Looking for a SharePoint MCP server for Grok Bot? ClawLink connects SharePoint to Grok Bot and exposes 86 SharePoint tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using a different agent? The OpenClaw SharePoint integration and the Hermes SharePoint integration connect the same ClawLink account the same way.
What the Grok Bot SharePoint integration can do
86 SharePoint tools are ready for Grok Bot once the account is connected. The 30 below are the ones people reach for most; your agent can call all 86.
30 of 86 SharePoint tools for Grok Bot
| Tool | What it does |
|---|---|
Share point add attachment to list item share_point_add_attachment_to_list_item | Tool to add an attachment to a SharePoint list item. Use when you need to upload a binary file as an attachment to a specified list item. |
Share point add field link to content type share_point_add_field_link_to_content_type | Tool to add a field link to a list content type. Use when you want to associate an existing list field with a content type. |
Share point add role assignment to item share_point_add_role_assignment_to_item | Tool to add a role assignment to a list item. Use when granting specific permissions to a user or group after breaking inheritance if needed. |
Share point add role assignment to list share_point_add_role_assignment_to_list | Tool to add a role assignment to a SharePoint list. |
Share point break role inheritance on item share_point_break_role_inheritance_on_item | Tool to break permission inheritance on a list item. |
Share point break role inheritance on list share_point_break_role_inheritance_on_list | Breaks permission inheritance on a SharePoint list, allowing you to set unique permissions. |
Share point check in file share_point_check_in_file | Tool to check in a file. Use after uploading or editing a document and you're ready to finalize changes. |
Share point create content type share_point_create_content_type | Tool to create a new content type in SharePoint. Use when you need to define a custom content type with specific metadata structure for lists or libraries. |
Share point create drive item sharing link share_point_create_drive_item_sharing_link | Tool to create a sharing link for a drive item in SharePoint or OneDrive. |
Share point create list field share_point_create_list_field | Tool to create a new field (column) in a SharePoint list. Use when you need to programmatically add a column after confirming the list GUID. |
Share point create list item by ID share_point_create_list_item_by_id | Tool to create a new item in a SharePoint list using the list's GUID. Use when you have the list GUID rather than the list title. |
Share point create list item in folder share_point_create_list_item_in_folder | Tool to create a list item in a specific folder within a SharePoint list. IMPORTANT: This action works ONLY with SharePoint lists (not document libraries). |
Share point download file by server relative URL share_point_download_file_by_server_relative_url | Download a file by server-relative URL |
Share point get all folders share_point_get_all_folders | Retrieve all folders in the SharePoint web |
Share point get changes share_point_get_changes | Retrieve changes from SharePoint list change log |
Share point get content type share_point_get_content_type | Retrieve a single SharePoint content type by its ID |
Share point get content types share_point_get_content_types | Retrieves all content types from the current SharePoint site |
Share point get content types for list share_point_get_content_types_for_list | Retrieve all content types for a specific SharePoint list by GUID |
Share point get context info share_point_get_context_info | Retrieve SharePoint context information including the form digest value |
Share point get current user share_point_get_current_user | Retrieve the current user for the site |
Share point get drive item analytics share_point_get_drive_item_analytics | Get analytics for a SharePoint drive item |
Share point get group users share_point_get_group_users | Retrieves all users who are members of a specified SharePoint group |
Share point get group users by ID share_point_get_group_users_by_id | Retrieve all users in a specific SharePoint site group by group ID |
Share point get item attachment content share_point_get_item_attachment_content | Download an attachment from a SharePoint list item |
Share point get list by guid share_point_get_list_by_guid | Retrieve a SharePoint list by its GUID |
Share point get list by title share_point_get_list_by_title | Retrieve a SharePoint list by its title |
Share point get list content type by ID share_point_get_list_content_type_by_id | Retrieve a specific content type from a SharePoint list by its ID |
Share point get list item by ID share_point_get_list_item_by_id | Retrieve a SharePoint list item by ID |
Share point get list item version share_point_get_list_item_version | Retrieve a specific version of a SharePoint list item |
Share point get list items share_point_get_list_items | Retrieve items from a SharePoint list |
Try it: find the SharePoint tool you need
Browse the 30 SharePoint tools
Click any tool to see exactly what Grok Bot can do and copy a ready-to-use prompt.
Example prompts
ClawLink vs. building it yourself
The alternative to ClawLink is usually manual OAuth app setup plus your own token handling, permission troubleshooting, and tool plumbing for Grok Bot. That is fine if you want to build and maintain the integration yourself. Most teams just want SharePoint working from chat.
| Manual | ClawLink | |
|---|---|---|
| Connection flow | Register a SharePoint app, configure redirect URLs, manage consent details, and reconnect users when auth settings drift. | Users connect SharePoint through the hosted browser flow and ClawLink keeps the token lifecycle out of your app code. |
| Ongoing maintenance | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for SharePoint. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. |
| Agent usability | You still need to expose the right SharePoint actions to the runtime in a format your agent can reliably use. | 86 tools for SharePoint are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes SharePoint to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for Grok Bot users instead. You install the plugin once, connect SharePoint in the browser, and the 86 tools above work from chat. There is no SDK, no config file, and no API key handling. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
Grok Bot says it cannot add ClawLink as an MCP server
Grok Bot only attaches MCP servers that are reachable over the public internet, so a local stdio server is refused. You do not need one. Ask Grok Bot to run npx -y @useclawlink/cli login in its terminal instead. The CLI is a shell command, not an MCP server. If you would rather have native tools, add https://claw-link.dev/api/mcp as a custom connector at grok.com/connectors and approve the ClawLink sign-in.
Connection succeeds but no tools appear
Reconnect SharePoint from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.
"Tool schema not loaded yet" error when calling SharePoint tools
SharePoint tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every SharePoint call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again.
SharePoint returns 403 or "permission denied" on one action while others work
Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs.
OAuth finished in the browser but the account is still missing
Try reconnecting SharePoint and complete the consent flow in the same browser session. Partial OAuth approvals or switching accounts mid-flow can leave the connection incomplete.
FAQ
Is there a Grok Bot SharePoint integration?
Yes. ClawLink is the fastest way to connect Grok Bot to SharePoint: link your SharePoint account once in the browser and Grok Bot can call the SharePoint API through 86 ready-made tools — no custom code or token handling.
How do I connect SharePoint to Grok Bot with ClawLink?
Ask Grok Bot to run npx -y @useclawlink/cli login in its terminal and approve the link it prints, then npx -y @useclawlink/cli connect sharepoint to authorize SharePoint. Grok Bot calls the tools from the next message, and the pairing persists in its sandbox, so this is a one-time step: no config files or API keys to manage.
How long does it take to connect SharePoint to Grok Bot?
About two minutes. Sign in, click Connect next to SharePoint in the dashboard, authenticate, and Grok Bot can use it from the next chat message.
Why use ClawLink instead of wiring SharePoint up myself?
The alternative to ClawLink is usually manual OAuth app setup plus your own token handling, permission troubleshooting, and tool plumbing for Grok Bot. That is fine if you want to build and maintain the integration yourself. Most teams just want SharePoint working from chat.
Grok Bot says it cannot add ClawLink as an MCP server
Grok Bot only attaches MCP servers that are reachable over the public internet, so a local stdio server is refused. You do not need one. Ask Grok Bot to run npx -y @useclawlink/cli login in its terminal instead. The CLI is a shell command, not an MCP server. If you would rather have native tools, add https://claw-link.dev/api/mcp as a custom connector at grok.com/connectors and approve the ClawLink sign-in.
