Webex + Muse

Connect Webex to Muse Prepare a grounded team update briefing

Read space messages with Muse and Agent200. Prepare a team update briefing using the connected user’s own Webex account.

On this page
  1. Overview
  2. Before you start
  3. Setup steps
  4. Test your connection
  5. Instructions for AI agents
  6. Webex tools
  7. How it works
  8. Troubleshooting
  9. FAQ

Overview

Use Muse to prepare a short team update briefing for review. Put the Agent200 key in Muse’s secure credential interface, then inspect the source before sharing the result.

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
Muse · Agent app, through MCP
Authentication
Managed OAuth, per end user
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.
  • Muse, with custom MCP servers allowed. Muse creates custom connectors from a chat, and your key goes into its secure credentials sheet, never into the chat. Muse Code reads servers from its settings file.

Connect Webex to Muse

  1. 1

    Step 1: Create your Agent200 API key

    Create a key on the API keys page and store it securely.

    .env
    Conceptual example
    Store the Agent200 API key as an environment variable
    # Keep the key out of your code, prompts and chats.
    export AGENT200_API_KEY="paste-your-key-here"
  2. 2

    Step 2: Create the custom connector

    Connect to https://api.agent200.com/mcp/ over Streamable HTTP with an Authorization: Bearer header. Enter the key in Muse’s secure credential interface.

    Muse chat
    MCP: message that asks Muse to create the custom connector
    Create a Custom Connector for the Agent200 remote MCP server and connect to it:
    Name: Agent200
    Transport: remote streamable HTTP
    URL: https://api.agent200.com/mcp/
    Auth: API key sent in the Authorization header as "Bearer <key>"
    Open the secure credentials store so I can enter the API key there, not in this chat.
    Then list its tools to confirm the connection works.
  3. 3

    Step 3: Inspect read tools

    Confirm the Webex operations and schemas advertised by the connection.

  4. 4

    Step 4: Authorize Webex

    Connect the intended user and test one accessible space message.

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.

Read the SDK docs

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 Muse.

Agent brief
Goal: connect Webex to Muse with Agent200, through its MCP server.
Guide: https://www.agent200.com/connectors/webex/framework/muse/

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 Muse'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 Muse: 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 Muse'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/muse.md

Webex tools Muse can call

  • List spaces

    Read
    webex_list_spaces

    Find the spaces available to the connected user.

  • Read a space

    Read
    webex_get_space

    Retrieve details of one identified space.

  • List messages

    Read
    webex_list_messages

    Read messages in a selected space within an explicit result scope.

  • Read a message

    Read
    webex_get_message

    Retrieve one identified message and its available details.

How it works

  1. 01

    You ask Muse

    In your own words, for something in Webex.

  2. 02

    Muse picks a tool

    It sees the Webex tools on the Agent200 MCP server and calls the one the request needs.

  3. 03

    Agent200 runs the call

    With your own Webex connection, within the tools and scopes your project allows.

  4. 04

    Muse 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.

Use Webex with another framework

200 OK

Webex, connected to Muse.
One SDK. One API key.

Agent200 handles the OAuth, the tokens and every tool call. You keep your agent, your model and your code.

Book a demo.
See it in action.

Tell us who you are, then pick a time for a 1:1 session with an expert from our team.

We use your details only to email you about Agent200. See the Privacy Policy.

Pick a time. We'll take it from there.

A 1:1 session with an expert from our team, about what you are building.

Open in Calendly (opens in a new tab)