MESA Docs
MESA Homepage
  • Welcome to MESA
    • Installing MESA
    • Dashboard
    • Core Concepts
    • Getting Help
  • Templates
    • Template Library
    • Installing & Editing
  • Workflow Builder
    • Triggers
    • Actions
    • Fields
      • Variables
      • Formatting Variables
      • Liquid Templating
    • Testing
  • Workflow Activity
    • Tasks
      • Troubleshooting
      • Replay
    • Logs
    • Time Travel
  • Best Practices
    • Set Titles & Descriptions
    • Track Time Saved
    • Enable Failure Notifications
    • Avoid Infinite Loops
  • Going Further
    • Plans & Billing
    • Notifications
    • Credentials
    • Understanding the Queue
    • Export & Import Workflows
    • Platform Thresholds & Limits
  • Built-in Tools
    • Activity Log
    • AI
    • API
    • Approval
    • MCP
    • Custom Code
      • Libraries
        • MESA SDK
        • Filter
        • Loop
        • Transform
        • oAuth
        • Shopify
        • ShopifyGraphql
      • FAQ
    • Data
    • Delay
    • Email
    • Filter
    • Form
      • Configure
      • Going Further
      • Technical Notes
    • FTP
    • Image
    • Loop
    • Package Tracking
    • Paths
    • Schedule
    • Scraper
    • SMS
    • Transform
    • Virtual Output
    • Weather
    • Web Request
    • Webhook
  • Apps
    • Airtable
    • Amazon S3
    • Asana
    • Blog Studio
    • ChannelApe
    • Claude
    • ChatGPT
    • Dall-E 2
    • Delighted
    • Digital Humani
    • Discord
    • DocuSign
    • Dropbox
    • Etsy
    • Facebook
    • Fera.ai
    • Gatsby
    • Gmail
      • Send Email
    • Google Analytics 4
    • Google Analytics UA
    • Google Calendar
    • Google Drive
    • Google Forms
    • Google Sheets
      • Add Row
      • Query Rows
      • Update Row
      • Row Created
      • Row Updated (Advanced)
      • Creating New Spreadsheets
      • Technical Notes
    • Gorgias
    • Govalo
    • Help Scout
    • Hubspot
    • Infinite Options
    • Intercom
    • IPDetective
    • Judge.me
    • Katana
    • Klaviyo
      • API Deprecation
    • Loop Returns
    • Loyalty Lion
    • Mailchimp
    • Mailgun
    • Mandrill
    • Mantle
    • Notion
    • Odoo
    • Omnisend
    • Page Studio
    • Pinterest
    • Printful
    • PrintNode
    • QuickBooks
    • Rebuy
    • Recharge
    • Remove.bg
    • Returnly
    • Rivo
    • Salesforce
    • Segment
    • Sendlane
    • Shippo
    • ShipStation
    • Shopify
      • Technical Notes
        • Configuring Your Payload
        • Modifying and Filtering Get Lists
        • Parameters
        • Error Codes
        • Accuracy of orders_count Variable
        • Accuracy of Count Products Action
        • Using the Gift Cards API
        • How to Find a Specific Record in the Testing Interface
        • Order, Customer, and Product Updated Trigger Frequency
    • Shopify Flow
    • Shopify Plus
    • Shopify Retail POS
    • Skio Subscriptions
    • Slack
    • Smartrr
    • Smile.io
    • Square
      • Updating Inventory
      • Frequently Asked Questions
    • Stamped.io
    • Stripe
    • Thanks.io
    • TikTok
    • Tracktor
    • Twilio
    • Uploadery
    • Wonderment
    • Xero
    • Yotpo
    • Yotpo Loyalty
  • For developers
    • Admin API
    • Command Line Interface
    • Embedding templates
  • Frequently asked questions
    • Why isn't the log search returning logs with the search I entered?
    • Is it possible to handle errors or retry steps?
    • How do I handle a failed task?
    • Does MESA auto-save workflows?
    • Can I Use Apps That Don't Have a MESA Connector?
    • Why is my workflow action adding the same data each time it occurs?
    • How do I cancel automations that are already in progress?
    • How do I cancel my MESA subscription or 7-day trial?
    • Can you import code from npm in custom code?
    • Do you have a Slack Community?
Powered by GitBook
On this page
  • Creating a MESA MCP workflow
  • Using MESA MCP with Claude
  • Get Claude Desktop
  • Ensure node is installed on your computer
  • Connect Claude to your MESA MCP server
  • Call MESA MCP workflows in Claude
  • Technical Notes
  • Common Issues

Was this helpful?

  1. Built-in Tools

MCP

PreviousApprovalNextCustom Code

Last updated 21 days ago

Was this helpful?

MESA MCP lets you supercharge your AI prompts by calling MESA workflows to fetch information and even take action.

Get started by creating a workflow in MESA with an MPC trigger. Then, let your AI app know about MESA MCP and start chatting. In the steps below, we use Claude Desktop, but MESA MCP also supports Cursor and many other AI apps.

Creating a MESA MCP workflow

  1. Create a new workflow in MESA. Search for and select MCP to add a MCP trigger.

  2. Configure the MCP step with any "parameters" your MCP workflow will need. If you want to search Shopify Orders, for instance, you might want to add parameters like status, created_at_min, created_at_max that will match the types of queries you will want to make. Make sure to give these parameters useful, explicit descriptions for the AI tools to interpret.

  3. Add any additional steps you would like your workflow to perform. Make sure to use any parameters you created to outfit your step(s) with the information they need to perform actions for your AI tool.

  4. Name the workflow something AI tools can understand, eg, "List Shopify Orders with Query". Be as explicit as possible to help AI tools determine which of your workflows to use. For instance, if you also wanted to provide your AI tool with Shopify orders by a single customer, you could create a new workflow "List Shopify Orders by Customer Email".

  5. Give the workflow as descriptive of a description as possible. If you have similar "sounding" workflows, the description can provide context to the AI tool about how to decide which workflows(s) to choose.

  6. Enable the workflow.

  7. Copy the connection information provided by the MCP trigger step.

    Note: you only need to configure Claude or other AI tools to connect to your MESA MCP server once.

Using MESA MCP with Claude

Get Claude Desktop

Ensure node is installed on your computer

node --version
  1. If you see any version less than 20.1.0 it means you will need to update your system's node version to at least 20.1.0.

Connect Claude to your MESA MCP server

  1. Click on “Developer” in the left-hand bar of the Settings pane, and then click on “Edit Config”.

  2. This will create a configuration file at:

    • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

    • Windows: %APPDATA%\Claude\claude_desktop_config.json

  3. Edit the claude_desktop_config.json file with the connection info provided by the Skill trigger. It will look something like this, though your information will be inserted where ID and KEY are below:

    {
      "mcpServers": {
        "mesa": {
          "command": "npx",
          "args": [
            "mcp-remote",
            "https://mcp-server.getmesa.com/sse/ID/KEY"
          ],
          "env": {}
        }
      }
    }
  4. Save the file and restart Claude Desktop.

    Note: you only need to configure Claude or other AI tools to connect to your MESA MCP server once.

Call MESA MCP workflows in Claude

Upon restarting, you should see a hammer icon in or near the input box. Clicking that hammer will show your Available MESA MCP workflows!

Try asking Claude something that would require information provided by your workflow eg. "Find Shopify Orders from March 2025". If Claude decides that it needs to run your workflow, you will be prompted for your approval to use the tool.

Technical Notes

  • Treat your MCP Configuration JSON like a password. It can be used to access and update your data.

Common Issues

Getting Claude Desktop running can be difficult, and the error messages can be unhelpful. Here are some solutions to common issues we have encountered.

Claude's "response was interrupted"

Some strategies:

  1. Start a new chat. Sometimes this can help, but if you're requesting a lot of data on every run, it may not do the trick.

  2. Upgrade your plan. Claude Pro includes a much larger context window than the free version.

  3. Reduce the size of your workflow's response. Depending on the app you may be able to configure your steps to return less information. This could be in the form of "only return these fields" or simply "limit number of responses". You could also use Loops or Custom Code to reduce the size of the information you respond with.

Claude still can't access my MESA MCP workflows

If you are a more technical user and have a node "version utility" like nvm installed. It's possible that Claude is getting confused with node versions as npx runs.

The mcp-server-mesa.log file may have things in it like:

npx: installed 120 in 8.27s
Unexpected token {
}

If that is the case, you may need to provide Claude with more information to function properly. These steps are only valid for Mac users but something similar should be possible for Windows:

  1. Open your terminal application and run:

    which npx
  2. Replace npx in the "command": "npx", of the Claude configuration file with the full path, eg. "command": "/Users/full/path/node/22.14.0/bin/npx",.

  3. In your terminal application run:

    echo $PATH
  4. Add the PATH "env" variable to the Claude configuration file for your MESA MCP server, and paste in the response from echo $PATH eg.

    {
      "mcpServers": {
        "mesa": {
          "command": "/Users/full/path/node/22.14.0/bin/npx",
          "args": [
            "mcp-remote",
            "https://mcp-server.getmesa.com/sse/ID/KEY"
          ],
          "env": {
            "PATH": "/The/Path/Returned/By/Your/Terminal"
          }
        }
      }
    }
  5. Restart Claude Desktop.

I saw my Skills, but they went away after I restarted Claude Desktop

You might need to kill the mcp-remote process running on your computer. In your terminal application run:

pkill -f mcp-remote

Currently, Claude can only talk to MESA's MCP workflows with , so make sure that application is installed on your computer. This article on has other potentially useful information.

Next, you will need to make sure that is installed on your computer. To check if it is installed, open your "terminal" program on your computer and run this command:

If you see command not found: node it means you will have to install .

Not seeing the hammer icon? Take a look at .

The maximum request time is limited based on the limit of your plan. There is also a limit of 60 seconds per request, even if your plan allows longer requests. Requests that take more time to execute will be timed out, and no response will be returned.

Requests are rate-limited based on the of your plan.

Usually, this means that too much information in the chat has already been processed, and Claude is running into issues with the "" size.

As noted above, you need a version of newer than 20.1.0 to access MESA's Skills.

Next a look at for anything you might have missed or misconfigured.

Claude Desktop
MCP for Claude Desktop
Node
Node
Claude's MCP troubleshooting section
context window
Node
Claude's MCP troubleshooting section
Task compute
Incoming rate limit