# How to integrate Mural MCP with Claude Code ```json { "title": "How to integrate Mural MCP with Claude Code", "toolkit": "Mural", "toolkit_slug": "mural", "framework": "Claude Code", "framework_slug": "claude-code", "url": "https://composio.dev/toolkits/mural/framework/claude-code", "markdown_url": "https://composio.dev/toolkits/mural/framework/claude-code.md", "updated_at": "2026-05-12T10:19:37.878Z" } ``` ## Introduction Manage your Mural directly from Claude Code with zero worries about OAuth hassles, API-breaking issues, or reliability and security concerns. You can do this in two different ways: - Via [Composio Connect](https://dashboard.composio.dev/login?utm_source=toolkits&utm_medium=framework_template&utm_campaign=claude-code&utm_content=composio_connect&next=%2F~%2Forg%2Fconnect%2Fclients%2Fclaude-code) - Direct and easiest approach - Via [Composio SDK](https://docs.composio.dev/docs?utm_source=toolkits&utm_medium=framework_template&utm_campaign=claude-code&utm_content=composio_sdk) - Programmatic approach with more control ## Also integrate Mural with - [OpenAI Agents SDK](https://composio.dev/toolkits/mural/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/mural/framework/claude-agents-sdk) - [Claude Cowork](https://composio.dev/toolkits/mural/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/mural/framework/codex) - [OpenClaw](https://composio.dev/toolkits/mural/framework/openclaw) - [Hermes](https://composio.dev/toolkits/mural/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/mural/framework/cli) - [Google ADK](https://composio.dev/toolkits/mural/framework/google-adk) - [LangChain](https://composio.dev/toolkits/mural/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/mural/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/mural/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/mural/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/mural/framework/crew-ai) ## TL;DR - Only one MCP URL to connect multiple apps with Claude Code with zero auth hassles. - Programmatic tool calling allows LLMs to write its code in a remote workbench to handle complex tool chaining. Reduces to-and-fro with LLMs for frequent tool calling. - Handling Large tool responses out of LLM context to minimize context rot. - Dynamic just-in-time access to 20,000 tools across 1000+ other Apps for cross-app workflows. It loads the tools you need, so LLMs aren't overwhelmed by tools you don't need. ## Connect Mural to Claude Code ### Connecting Mural to Claude Code using Composio 1. Add the Composio MCP to Claude ```bash claude mcp add --scope user --transport http composio https://connect.composio.dev/mcp ``` ## What is Claude Code? Claude Code is Anthropic's command line developer tool that lets you use Claude directly inside your terminal. Instead of switching between your editor, browser, and chat, you can stay in your project folder and ask Claude to help you build, debug, refactor, and understand code right where you're working. Key features include: - Terminal-Native Experience: Work with Claude directly in your command line without switching contexts - MCP Support: Built-in support for Model Context Protocol servers to extend Claude's capabilities - Project Context: Claude understands your project structure and can read, write, and modify files - Interactive Development: Ask questions, debug code, and get help in real-time while coding - Multi-Platform: Works on macOS, Linux, WSL, and Windows ## What is the Mural MCP server, and what's possible with it? The Mural MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Mural account. It provides structured and secure access to your digital whiteboards, so your agent can perform actions like creating sticky notes, retrieving board widgets, managing files, and accessing user info on your behalf. - Automated sticky note creation: Instantly add one or more sticky notes to any mural for fast brainstorming, idea capture, or task tracking via your agent. - Widget and content retrieval: Have your agent fetch all widgets within a specific mural, making it easy to analyze, summarize, or organize the board's contents programmatically. - File management on murals: Let your agent list all file attachments within a mural, so you can monitor, catalog, or process embedded documents and images effortlessly. - User information access: Retrieve details about the current authenticated user, enabling personalized actions and tailored workflows across your Mural workspace. - Seamless OAuth authorization: Easily initiate secure, managed authentication flows so your agent can access and act on your behalf without manual credential handling. ## Supported Tools | Tool slug | Name | Description | |---|---|---| | `MURAL_AUTHORIZATION_REQUEST` | MURAL Authorization Request | Tool to initiate the OAuth 2.0 authorization process. Use when you need to redirect a user to Mural to obtain an authorization code. | | `MURAL_CREATE_STICKY_NOTE` | Create sticky note | Create one or more sticky note widgets on a mural. Each sticky note must be a properly structured object with required x and y coordinates. Pass the 'stickies' parameter as a direct array of objects - NOT strings, NOT nested objects. Example usage: { "muralId": "mural-id-here", "stickies": [ {"x": 100, "y": 200, "text": "First note"}, {"x": 300, "y": 400, "text": "Second note", "shape": "circle"} ] } | | `MURAL_GET_CURRENT_USER` | Get current user | Tool to retrieve information about the currently authenticated user. Use when you need current user details after authentication. | | `MURAL_GET_FILES_FOR_MURAL` | Get files for a mural | Tool to retrieve a list of file widgets in a mural. Use after confirming the mural ID when listing file attachments. | | `MURAL_GET_MURAL_WIDGETS` | Get Mural Widgets | Tool to retrieve all widgets within a specified mural. Widgets include sticky notes, text boxes, shapes, images, areas, arrows, icons, files, and comments. Use this after obtaining a valid mural ID from workspace murals or other mural-related actions. Supports filtering by widget type, parent container, and pagination for large result sets. | | `MURAL_GET_ROOM` | Get room by ID | Tool to retrieve information about a specific room by its ID. Use when you need details about a particular room that the authenticated user has read access to. | | `MURAL_GET_WORKSPACE` | Get workspace by ID | Tool to retrieve information about a specific workspace by its ID. Use when you need details about a particular workspace that the authenticated user has read access to. | | `MURAL_GET_WORKSPACES` | Get workspaces | Tool to retrieve all workspaces the authenticated user is a member of. Use to list available workspaces before accessing rooms or murals. | | `MURAL_LIST_FOLDERS` | List folders in room | Tool to list all folders within a room that the authenticated user has access to. Use after MURAL_LIST_ROOMS to navigate folders within a specific room. | | `MURAL_LIST_OPEN_ROOMS` | List open rooms in workspace | Tool to list all discoverable open rooms within a workspace. Use when you need to access publicly available rooms in a workspace that don't require specific membership. | | `MURAL_LIST_RECENT_MURALS` | List recent murals in workspace | Tool to list recently opened active murals for the authenticated user in a workspace. Use after MURAL_LIST_WORKSPACES to view recent murals before opening or editing them. | | `MURAL_LIST_RECENT_TEMPLATES` | List recent templates | Tool to retrieve recent templates used by a user for a workspace. Use when you need to access recently used templates for creating new murals. | | `MURAL_LIST_ROOM_MURALS` | List murals in room | Tool to list all murals for a room that the authenticated user has read access to. Use after getting a room ID to retrieve murals within that room. | | `MURAL_LIST_ROOMS` | List rooms in workspace | Tool to list all rooms within a workspace. Use after MURAL_LIST_WORKSPACES to navigate rooms and before MURAL_CREATE_MURAL, since murals are created within rooms. | | `MURAL_LIST_ROOM_USERS` | List users in room | Tool to list all members and guests for a room. Returns users that the authenticated user has access to view. Use after LIST_ROOMS to get room membership details. | | `MURAL_LIST_TAGS` | List tags in a mural | Tool to retrieve all tags in a mural. Use when you need to list or view tags associated with a specific mural. | | `MURAL_LIST_TEMPLATES` | List default templates | Tool to retrieve all default templates available in Mural. Use when you need to browse or select from standard Mural templates. | | `MURAL_LIST_WORKSPACE_MURALS` | List workspace murals | Tool to list all murals in a workspace that the authenticated user owns or is a member of. Use after getting a workspace ID to browse available murals. | | `MURAL_LIST_WORKSPACE_TEMPLATES` | List workspace templates | Tool to get default and custom templates for a workspace. Use when you need to list available templates after authentication. | | `MURAL_SEARCH_MURALS` | Search murals in workspace | Tool to search for murals within a workspace. Returns all murals that the authenticated user owns or is a member of for the specified workspace. Use when searching for specific murals by query text. | | `MURAL_SEARCH_ROOMS` | Search rooms in workspace | Tool to search for rooms within a workspace by name or description. Returns all rooms that the authenticated user owns or is a member of matching the query. Use when you need to find specific rooms by search text. | | `MURAL_SEARCH_TEMPLATES` | Search templates in workspace | Tool to search templates within a workspace that the authenticated user owns or has access to. Use when you need to find specific templates by name or keyword. | ## Supported Triggers None listed. ## Creating MCP Server - Stand-alone vs Composio SDK The Mural MCP server is an implementation of the Model Context Protocol that connects Claude Code (and other AI assistants like Claude and Cursor) directly to your Mural account. It provides structured and secure access so Claude can perform Mural operations on your behalf. With Composio's managed implementation, you don't have to create your own developer app. For production, if you're building an end product, we recommend using your own credentials. The managed server helps you prototype fast and go from 0-1 faster. ## Step-by-step Guide ### 1. Prerequisites Before starting, make sure you have: - Claude Pro, Max, or API billing enabled Anthropic account - Composio API Key - A Mural account - Basic knowledge of Python or TypeScript ### 1. Install Claude Code To install Claude Code, use one of the following methods based on your operating system: ```bash # macOS, Linux, WSL curl -fsSL https://claude.ai/install.sh | bash # Windows PowerShell irm https://claude.ai/install.ps1 | iex # Windows CMD curl -fsSL https://claude.ai/install.cmd -o install.cmd && install.cmd && del install.cmd ``` ### 2. Set up Claude Code Open a terminal, go to your project folder, and start Claude Code: - Claude Code will open in your terminal - Follow the prompts to sign in with your Anthropic account - Complete the authentication flow - Once authenticated, you can start using Claude Code ```bash cd your-project-folder claude ``` ### 3. Set up environment variables Create a .env file in your project root with the following variables: - COMPOSIO_API_KEY authenticates with Composio (get it from [Composio dashboard](https://dashboard.composio.dev/login?utm_source=toolkits&utm_medium=framework_template&utm_campaign=claude-code&utm_content=api_key&next=%2F~%2Forg%2Fconnect%2Fclients%2Fclaude-code)) - USER_ID identifies the user for session management (use any unique identifier) ```bash COMPOSIO_API_KEY=your_composio_api_key_here USER_ID=your_user_id_here ``` ### 4. Install Composio library No description provided. ```python pip install composio-core python-dotenv ``` ```typescript npm install @composio/core dotenv ``` ### 5. Generate Composio MCP URL No description provided. ```python import os from composio import Composio from dotenv import load_dotenv load_dotenv() COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY") USER_ID = os.getenv("USER_ID") composio_client = Composio(api_key=COMPOSIO_API_KEY) composio_session = composio_client.create( user_id=USER_ID, toolkits=["mural"], ) COMPOSIO_MCP_URL = composio_session.mcp.url print(f"MCP URL: {COMPOSIO_MCP_URL}") print(f"\nUse this command to add to Claude Code:") print(f'claude mcp add --transport http mural-composio "{COMPOSIO_MCP_URL}" --headers "X-API-Key:{COMPOSIO_API_KEY}"') ``` ```typescript import 'dotenv/config'; import { Composio } from '@composio/core'; const { COMPOSIO_API_KEY, USER_ID } = process.env; if (!COMPOSIO_API_KEY || !USER_ID) { throw new Error('COMPOSIO_API_KEY and USER_ID required in .env'); } const composioClient = new Composio({ apiKey: COMPOSIO_API_KEY }); const composioSession = await composioClient.create(USER_ID, { toolkits: ['mural'], }); const composioMcpUrl = composioSession?.mcp.url; console.log(`MCP URL: ${composioMcpUrl}`); console.log(`\nUse this command to add to Claude Code:`); console.log(`claude mcp add --transport http mural-composio "${composioMcpUrl}" --headers "X-API-Key:${COMPOSIO_API_KEY}"`); ``` ### 6. Run the script and copy the MCP URL No description provided. ```python python generate_mcp_url.py ``` ```typescript node --loader ts-node/esm generate_mcp_url.ts # or if using tsx tsx generate_mcp_url.ts ``` ### 7. Add Mural MCP to Claude Code In your terminal, add the MCP server using the command from the previous step. The command format is: - claude mcp add registers a new MCP server with Claude Code - --transport http specifies that this is an HTTP-based MCP server - The server name (mural-composio) is how you'll reference it - The URL points to your Composio Tool Router session - --headers includes your Composio API key for authentication After running the command, close the current Claude Code session and start a new one for the changes to take effect. ```bash claude mcp add --transport http mural-composio "YOUR_MCP_URL_HERE" --headers "X-API-Key:YOUR_COMPOSIO_API_KEY" # Then restart Claude Code exit claude ``` ### 8. Verify the installation Check that your Mural MCP server is properly configured. - This command lists all MCP servers registered with Claude Code - You should see your mural-composio entry in the list - This confirms that Claude Code can now access Mural tools If everything is wired up, you should see your mural-composio entry listed: ```bash claude mcp list ``` ### 9. Authenticate Mural The first time you try to use Mural tools, you'll be prompted to authenticate. - Claude Code will detect that you need to authenticate with Mural - It will show you an authentication link - Open the link in your browser (or copy/paste it) - Complete the Mural authorization flow - Return to the terminal and start using Mural through Claude Code Once authenticated, you can ask Claude Code to perform Mural operations in natural language. For example: - "Add sticky notes summarizing team feedback" - "List all image files on project mural" - "Show all widgets in today's brainstorming board" ## Complete Code ```python import os from composio import Composio from dotenv import load_dotenv load_dotenv() COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY") USER_ID = os.getenv("USER_ID") composio_client = Composio(api_key=COMPOSIO_API_KEY) composio_session = composio_client.create( user_id=USER_ID, toolkits=["mural"], ) COMPOSIO_MCP_URL = composio_session.mcp.url print(f"MCP URL: {COMPOSIO_MCP_URL}") print(f"\nUse this command to add to Claude Code:") print(f'claude mcp add --transport http mural-composio "{COMPOSIO_MCP_URL}" --headers "X-API-Key:{COMPOSIO_API_KEY}"') ``` ```typescript import 'dotenv/config'; import { Composio } from '@composio/core'; const { COMPOSIO_API_KEY, USER_ID } = process.env; if (!COMPOSIO_API_KEY || !USER_ID) { throw new Error('COMPOSIO_API_KEY and USER_ID required in .env'); } const composioClient = new Composio({ apiKey: COMPOSIO_API_KEY }); const composioSession = await composioClient.create(USER_ID, { toolkits: ['mural'], }); const composioMcpUrl = composioSession?.mcp.url; console.log(`MCP URL: ${composioMcpUrl}`); console.log(`\nUse this command to add to Claude Code:`); console.log(`claude mcp add --transport http mural-composio "${composioMcpUrl}" --headers "X-API-Key:${COMPOSIO_API_KEY}"`); ``` ## Conclusion You've successfully integrated Mural with Claude Code using Composio's MCP server. Now you can interact with Mural directly from your terminal using natural language commands. Key features of this setup: - Terminal-native experience without switching contexts - Natural language commands for Mural operations - Secure authentication through Composio's managed MCP - Tool Router for dynamic tool discovery and execution Next steps: - Try asking Claude Code to perform various Mural operations - Add more toolkits to your Tool Router session for multi-app workflows - Integrate this setup into your development workflow for increased productivity You can extend this by adding more toolkits, implementing custom workflows, or building automation scripts that leverage Claude Code's capabilities. ## How to build Mural MCP Agent with another framework - [OpenAI Agents SDK](https://composio.dev/toolkits/mural/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/mural/framework/claude-agents-sdk) - [Claude Cowork](https://composio.dev/toolkits/mural/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/mural/framework/codex) - [OpenClaw](https://composio.dev/toolkits/mural/framework/openclaw) - [Hermes](https://composio.dev/toolkits/mural/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/mural/framework/cli) - [Google ADK](https://composio.dev/toolkits/mural/framework/google-adk) - [LangChain](https://composio.dev/toolkits/mural/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/mural/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/mural/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/mural/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/mural/framework/crew-ai) ## Related Toolkits - [Figma](https://composio.dev/toolkits/figma) - Figma is a collaborative interface design tool for teams and individuals. It streamlines design workflows with real-time collaboration and easy sharing. - [Abyssale](https://composio.dev/toolkits/abyssale) - Abyssale is a creative automation platform for generating images, videos, GIFs, PDFs, and HTML5 content programmatically. It streamlines and scales visual content production for marketing, design, and operations teams. - [Alttext ai](https://composio.dev/toolkits/alttext_ai) - AltText.ai is a service that generates alt text for images automatically. It helps boost accessibility and SEO for your visual content. - [Bannerbear](https://composio.dev/toolkits/bannerbear) - Bannerbear is an API-driven platform for generating images and videos automatically at scale. It helps businesses create custom graphics, social visuals, and marketing assets using powerful templates. - [Canva](https://composio.dev/toolkits/canva) - Canva is a drag-and-drop design suite for creating professional graphics, presentations, and marketing materials. It makes it easy for anyone to design with beautiful templates and a vast library of elements. - [Claid ai](https://composio.dev/toolkits/claid_ai) - Claid.ai delivers AI-driven image editing APIs for tasks like background removal, upscaling, and color correction. It helps automate and enhance image workflows with powerful, developer-friendly tools. - [Cloudinary](https://composio.dev/toolkits/cloudinary) - Cloudinary is a cloud-based platform for managing, uploading, and transforming images and videos. It streamlines media workflows and delivers optimized assets globally. - [Cults](https://composio.dev/toolkits/cults) - Cults is a digital marketplace for 3D printing models, connecting designers and makers. It lets creators share, sell, and discover a huge variety of printable designs easily. - [DeepImage](https://composio.dev/toolkits/deepimage) - DeepImage is an AI-powered image enhancer and upscaler. Get higher-quality images with just a few clicks. - [Dreamstudio](https://composio.dev/toolkits/dreamstudio) - DreamStudio is Stability AI’s platform for generating and editing images with AI. It lets you easily turn ideas into stunning visuals, fast. - [Dynapictures](https://composio.dev/toolkits/dynapictures) - Dynapictures is a cloud-based platform for generating personalized images at scale. Instantly create hundreds of custom visuals using your data sources, like Google Sheets. - [Fal.ai](https://composio.dev/toolkits/fal_ai) - Fal.ai is a generative media platform offering 600+ AI models for images, video, voice, and audio. Developers use Fal.ai for fast, scalable access to cutting-edge generative AI tools. - [Gamma](https://composio.dev/toolkits/gamma) - Gamma is an AI-powered platform for making beautiful, interactive presentations and documents. It lets anyone create and share engaging decks with minimal effort. - [Html to image](https://composio.dev/toolkits/html_to_image) - Html to image converts HTML and CSS into images or captures web page screenshots. Instantly generate visuals from code or web content—no manual screenshots needed. - [Imagior](https://composio.dev/toolkits/imagior) - Imagior is an AI-powered image generation platform that lets you create and customize images using dynamic templates and APIs. Perfect for businesses and creators needing fast, scalable visuals without design hassle. - [Imejis io](https://composio.dev/toolkits/imejis_io) - Imejis io is an API-based image generation platform with powerful customization and template support. It lets you create and modify images in seconds, no manual design work required. - [Imgix](https://composio.dev/toolkits/imgix) - Imgix is a real-time image processing and delivery service for developers. It helps you optimize, transform, and deliver images efficiently at any scale. - [Kraken io](https://composio.dev/toolkits/kraken_io) - Kraken.io is an image optimization and compression platform. It helps you shrink image file sizes while keeping visual quality intact. - [Logo dev](https://composio.dev/toolkits/logo_dev) - Logo.dev is an API and database for high-resolution company logos and brand metadata. Instantly fetch official logos from any domain without scraping or manual searching. - [Miro](https://composio.dev/toolkits/miro) - Miro is a collaborative online whiteboard platform for teams to brainstorm, design, and manage projects visually. It streamlines teamwork by enabling real-time idea sharing, diagramming, and workflow planning in a single space. ## Frequently Asked Questions ### What are the differences in Tool Router MCP and Mural MCP? With a standalone Mural MCP server, the agents and LLMs can only access a fixed set of Mural tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Mural and many other apps based on the task at hand, all through a single MCP endpoint. ### Can I use Tool Router MCP with Claude Code? Yes, you can. Claude Code fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Mural tools. ### Can I manage the permissions and scopes for Mural while using Tool Router? Yes, absolutely. You can configure which Mural scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do. ### How safe is my data with Composio Tool Router? All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Mural data and credentials are handled as safely as possible. --- [See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)