Mural + Claude
Connect Mural to Claude
Prepare a grounded workshop recap
Read murals with Claude and Agent200. Prepare a workshop recap using the connected user’s own Mural account.
On this page
Overview
Ask Claude for a focused workshop recap from one selected mural. Compare its answer with the retrieved source and separate suggestions from recorded facts.
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.
- Connector
- Mural
- Works with
- Claude · Agent app, through MCP
- Authentication
- Managed OAuth, per end user
- You need
- An Agent200 API key
- Tools
- 6 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.
- 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.
- Claude, with custom MCP servers allowed. Custom connectors are on every Claude plan (Free: one). Sending an API key uses the Request headers option, a beta that only some accounts have; on Team and Enterprise an Owner adds the connector for everyone.
Connect Mural to Claude
-
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 Claude 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.
-
2
Step 2: Open Connectors in Claude
On a Free, Pro, Max or Ultra plan, go to Customize > Connectors. On Team or Enterprise, an Owner goes to Organization settings > Connectors; members then find the connector under Customize > Connectors.
-
3
Step 3: Add a custom connector
Select Add, then Add custom connector. Enter a name, Agent200, and the remote MCP server URL, then choose Continue.
-
4
Step 4: Send your key as a request header
Under Authentication choose No sign-in. Open Request headers, pick
authorization, enterBearerfollowed by a space and your key, mark it Required and choose Add. Claude sends the value exactly as typed.Add custom connectorMCP: Claude custom connector (URL and request header) Remote MCP server URL: https://api.agent200.com/mcp/ Authentication: No sign-in Request header name: authorization Value: Bearer YOUR_AGENT200_API_KEY -
5
Step 5: Turn it on in a chat
In a chat, select + > Connectors and turn Agent200 on. Ask Claude to list the Agent200 tools to check the connection; Claude asks before a tool runs the first time.
-
6
Step 6: Connect your Mural account
The first time you ask Claude 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 Claude or Agent200.
Test your connection
Run one request to check everything is wired up.
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.
Get your API key
Create a key in the Agent200 dashboard. It reaches Mural 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 Mural to Claude.
Goal: connect Mural to Claude with Agent200, through its MCP server. Guide: https://www.agent200.com/connectors/mural/framework/claude/ 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 Claude'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 Claude: 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 Claude'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.
The whole guide is also available as Markdown, for agents and LLMs: /connectors/mural/framework/claude.md
Mural tools Claude can call
-
List workspaces
Readmural_list_workspacesFind workspaces available to the connected user.
-
List rooms
Readmural_list_roomsFind accessible rooms in a selected workspace.
-
List murals
Readmural_list_muralsFind murals in a selected room.
-
Search murals
Readmural_search_muralsFind candidate murals by title within an accessible workspace.
-
Read a mural
Readmural_get_muralRetrieve details of one identified mural.
-
List mural widgets
Readmural_list_widgetsRead supported widgets from a selected mural with pagination.
No tool matches that search.
How it works
-
01
You ask Claude
In your own words, for something in Mural.
-
02
Claude picks a tool
It sees the Mural tools on the Agent200 MCP server and calls the one the request needs.
-
03
Agent200 runs the call
With your own Mural connection, within the tools and scopes your project allows.
-
04
Claude 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.
