Webex + Grok Bot
Connect Webex to Grok Bot
Prepare a grounded team update briefing
Read space messages with Grok Bot and Agent200. Prepare a team update briefing using the connected user’s own Webex account.
On this page
Overview
Identify the selected space message and ask Grok Bot to use the Agent200 connection. Inspect tool activity so browser context or another app does not replace the requested read.
Start with one identified space message. Preserve returned space, sender, message text and time; report missing data and keep the workflow read-only.
Provider reference: Webex API.
- Connector
- Webex
- Works with
- Grok Bot · Agent app, through MCP
- Authentication
- Managed OAuth, per end user
- You need
- An Agent200 API key
- Tools
- 4 tools
- MCP server
https://api.agent200.com/mcp/
Before you start
- An Agent200 API key. Create one on the API keys page of the dashboard.
- Webex enabled for your project. In the dashboard's Connectors settings, with the endpoints and scopes your agent needs.
- An end user with a Webex account. They approve access once, on Webex's own page.
- Grok Bot, with custom MCP servers allowed. Grok Bot comes with SuperGrok, Grok Business seats and paid Cursor plans. On a team, the admin's connector policy must allow the Agent200 server.
Connect Webex to Grok Bot
-
1
Step 1: Create your Agent200 API key
Open the API keys page in the Agent200 dashboard and choose Create an API key. You add it to Grok Bot in the next step, as "Authorization: Bearer <your key>". One key covers Webex and every other connector enabled for your project. Keep it out of chats and source control.
-
2
Step 2: Open the custom connector form
In Grok Bot, open Connect apps from the sidebar and choose Add a custom connector at the bottom.
-
3
Step 3: Fill in the server and your key
Enter the name Agent200, pick Type Remote HTTPS, enter the server URL and add one HTTP header:
Authorizationwith the valueBearerfollowed by your key. Leave Client ID empty, then choose Add plugin.Add a custom connectorMCP: Grok Bot custom connector form Name: Agent200 Type: Remote HTTPS Server URL: https://api.agent200.com/mcp/ HTTP headers: Authorization: Bearer YOUR_AGENT200_API_KEY -
4
Step 4: Attach Agent200 in a chat
In a Bot chat, type
@and attach Agent200 to the task. Custom servers are account-wide, so every Bot on the account can use it. -
5
Step 5: Connect your Webex account
The first time you ask Grok Bot for something in Webex, Agent200 returns an authorization link. Open it and approve access on Webex's own page. Agent200 stores the connection and keeps it working; your password never reaches Grok Bot or Agent200.
Test your connection
Run one request to check everything is wired up.
Ask
Read recent messages from the Webex space I identify. Summarize the decisions and open questions from returned messages, naming the space and source messages. Ask if the space is ambiguous. Do not post or modify anything.
What should come back
- The selected space message is identified.
- Only returned space, sender, message text and time are reported.
- Access gaps and missing context are explicit; no source data is changed.
Check the selected space ID, connected user membership, read permissions and page scope. Report access errors or missing messages without inventing a conversation.
Get your API key
Create a key in the Agent200 dashboard. It reaches Webex and every other connector enabled for your project.
Instructions for AI agents
Using a coding agent? Paste this brief into it, or give it the address of this page. It lists what to do, in order, to connect Webex to Grok Bot.
Goal: connect Webex to Grok Bot with Agent200, through its MCP server. Guide: https://www.agent200.com/connectors/webex/framework/grok-bot/ 1. The user needs an Agent200 API key. If they have none, send them to https://agent200.com/platform/apikeys/ to choose "Create an API key". They paste it into Grok Bot's settings themselves: never ask for it in chat and never write it into files you share. 2. Make sure Webex is enabled for their project in the Agent200 dashboard (Connectors), with the tools the task needs. 3. Add Agent200's MCP server to Grok Bot: URL https://api.agent200.com/mcp/, transport streamable HTTP, header "Authorization: Bearer <the user's Agent200 API key>". Follow the setup steps on the guide page for Grok Bot's exact menus or commands. 4. The first Webex request returns an authorization link if the user has not connected Webex yet: show it to them and continue once they have approved access on Webex's own page. 5. Check it works with this request: "Read recent messages from the Webex space I identify. Summarize the decisions and open questions from returned messages, naming the space and source messages. Ask if the space is ambiguous. Do not post or modify anything." What should come back: - The selected space message is identified. - Only returned space, sender, message text and time are reported. - Access gaps and missing context are explicit; no source data is changed. 6. If a tool is missing or a call is refused, check the project's Connectors settings in the dashboard and the access the user granted in Webex, then retry.
The whole guide is also available as Markdown, for agents and LLMs: /connectors/webex/framework/grok-bot.md
Webex tools Grok Bot can call
-
List spaces
Readwebex_list_spacesFind the spaces available to the connected user.
-
Read a space
Readwebex_get_spaceRetrieve details of one identified space.
-
List messages
Readwebex_list_messagesRead messages in a selected space within an explicit result scope.
-
Read a message
Readwebex_get_messageRetrieve one identified message and its available details.
No tool matches that search.
How it works
-
01
You ask Grok Bot
In your own words, for something in Webex.
-
02
Grok Bot picks a tool
It sees the Webex tools on the Agent200 MCP server and calls the one the request needs.
-
03
Agent200 runs the call
With your own Webex connection, within the tools and scopes your project allows.
-
04
Grok Bot answers
It gets the result back from the MCP server and uses it in its reply or its next step.
Each user's own connection. Connections belong to individual end users. A request for one user never reaches another user's Webex account.
Permissions at every level. Your project settings decide what the agent may request, the end user decides what they authorize, and Webex enforces what its API grants.
Troubleshooting
The source cannot be read
Check the selected space ID, connected user membership, read permissions and page scope. Report access errors or missing messages without inventing a conversation.
FAQ
How do I verify this result?
Compare the named space message and returned space, sender, message text and time with the source. Treat missing information as missing, not as a fact.
