# Connect Mural to Grok Bot Prepare a grounded workshop recap

> Read murals with Grok Bot and Agent200. Prepare a workshop recap using the connected user’s own Mural account.

- Page: https://www.agent200.com/connectors/mural/framework/grok-bot/
- Connector: [Mural](https://www.agent200.com/connectors/mural.md)
- Framework: Grok Bot
- Updated: 2026-11-17

## Instructions for AI agents

Goal: connect Mural to Grok Bot with Agent200, through its MCP server.
Guide: https://www.agent200.com/connectors/mural/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 Mural 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 Mural request returns an authorization link if the user has not connected Mural yet: show it to them and continue once they have approved access on Mural's own page.
5. Check it works with this request: "Read the Mural board I identify in its workspace and room. Summarize the returned widgets into themes and open questions. Name the board and disclose any content types not returned. Do not change the mural."
   What should come back:
   - The selected mural is identified.
   - Only returned workspace, room, mural identity and returned widget content 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 Mural, then retry.

## Overview

Identify the selected mural 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 mural. Preserve returned workspace, room, mural identity and returned widget content; report missing data and keep the workflow read-only.

Provider reference: [Mural API](https://developers.mural.co/public/reference/getmuralwidgets).

- **Connector:** [Mural](https://www.agent200.com/connectors/mural/)
- **Works with:** Grok Bot · Agent app, through MCP
- **Authentication:** Managed OAuth, per end user
- **You need:** [An Agent200 API key](https://agent200.com/platform/apikeys/)
- **Tools:** [6 tools](https://www.agent200.com/connectors/mural/framework/grok-bot/#tools)
- **MCP server:** `https://api.agent200.com/mcp/`

## Before you start

- **An Agent200 API key.** Create one on the [API keys page](https://agent200.com/platform/apikeys/) of the dashboard.
- **Mural enabled for your project.** In the dashboard's Connectors settings, with the endpoints and scopes your agent needs.
- **An end user with a Mural account.** They approve access once, on Mural'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 Mural to Grok Bot

### 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 Mural and every other connector enabled for your project. Keep it out of chats and source control.

Create an API key: https://agent200.com/platform/apikeys/

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

### 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: `Authorization` with the value `Bearer` followed by your key. Leave Client ID empty, then choose **Add plugin**.

File `Add a custom connector`:

```text
Name:          Agent200
Type:          Remote HTTPS
Server URL:    https://api.agent200.com/mcp/
HTTP headers:  Authorization: Bearer YOUR_AGENT200_API_KEY
```

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

### Step 5: Connect your Mural account

The first time you ask Grok Bot for something in Mural, Agent200 returns an authorization link. Open it and approve access on Mural's own page. Agent200 stores the connection and keeps it working; your password never reaches Grok Bot or Agent200.

## Test your connection

Ask: "Read the Mural board I identify in its workspace and room. Summarize the returned widgets into themes and open questions. Name the board and disclose any content types not returned. Do not change the mural."

What should come back:

- The selected mural is identified.
- Only returned workspace, room, mural identity and returned widget content are reported.
- Access gaps and missing context are explicit; no source data is changed.

Check workspace, room and mural IDs, connected-user access, read scopes and pagination. Do not infer a blank board from an incomplete response.

## Mural tools Grok Bot can call

- **List workspaces** (`mural_list_workspaces`, read): Find workspaces available to the connected user.
- **List rooms** (`mural_list_rooms`, read): Find accessible rooms in a selected workspace.
- **List murals** (`mural_list_murals`, read): Find murals in a selected room.
- **Search murals** (`mural_search_murals`, read): Find candidate murals by title within an accessible workspace.
- **Read a mural** (`mural_get_mural`, read): Retrieve details of one identified mural.
- **List mural widgets** (`mural_list_widgets`, read): Read supported widgets from a selected mural with pagination.

## How it works

1. **You ask Grok Bot.** In your own words, for something in Mural.
2. **Grok Bot picks a tool.** It sees the Mural tools on the Agent200 MCP server and calls the one the request needs.
3. **Agent200 runs the call.** With your own Mural connection, within the tools and scopes your project allows.
4. **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 Mural account.

**Permissions at every level.** Your project settings decide what the agent may request, the end user decides what they authorize, and Mural enforces what its API grants.

## Troubleshooting

### The source cannot be read

Check workspace, room and mural IDs, connected-user access, read scopes and pagination. Do not infer a blank board from an incomplete response.

## FAQ

### How do I verify this result?

Compare the named mural and returned workspace, room, mural identity and returned widget content with the source. Treat missing information as missing, not as a fact.

## Use Mural with another framework

- [Mural + Claude](https://www.agent200.com/connectors/mural/framework/claude.md)
- [Mural + ChatGPT](https://www.agent200.com/connectors/mural/framework/chatgpt.md)
- [Mural + Claude Code](https://www.agent200.com/connectors/mural/framework/claude-code.md)
- [Mural + Muse](https://www.agent200.com/connectors/mural/framework/muse.md)
- [Mural + OpenAI Dots](https://www.agent200.com/connectors/mural/framework/openai-dots.md)
- [Mural + Claude Duet](https://www.agent200.com/connectors/mural/framework/claude-duet.md)
- [Mural + Hermes Agent](https://www.agent200.com/connectors/mural/framework/hermes-agent.md)
- [Mural + OpenClaw](https://www.agent200.com/connectors/mural/framework/openclaw.md)

---

Agent200: https://www.agent200.com/ · API keys: https://agent200.com/platform/apikeys/ · Docs: https://docs.igpt.ai/
