MeshHub
Documentation

Quickstart Guide

Get your first AI agent tool call working in under 10 minutes. MeshHub connects REST APIs into a shared ecosystem where AI agents discover and execute real-world actions.

1

Pick an Integration

Browse the integrations to find one that fits your use case. Each integration exposes one or more tools your agent can call.

Some integrations to try right away:

Demo Store
Search products, create orders
Demo Shipping
Get shipping quotes, track packages
2

Try a Tool in the Playground

Open the Playground, select an integration and tool, fill in the parameters, and hit Run. You will see the response instantly.

Or try it from the command line:

curl -X POST https://meshhub.ai/api/tools/call \
  -H "Content-Type: application/json" \
  -d '{
    "integrationId": "2",
    "toolName": "search_products",
    "params": { "query": "laptop" }
  }'
3

Connect MeshHub MCP to Your Agent

Add the following MCP config snippet to your agent client. This tells your agent which tools are available through MeshHub.

{
  "mcpServers": {
    "meshhub": {
      "url": "https://meshhub.ai/api/mcp",
      "tools": ["search_products", "get_quote", "create_order"]
    }
  }
}

Where to paste this config:

  • Claude Desktop / Cursor / Windsurf: Add to your MCP server configuration file (usually mcp_config.json)
  • LangChain / CrewAI: Use the MCP tools adapter to load from this config
  • Custom agents: Parse the config and register tools by calling the MeshHub API endpoints
4

Run a Sample Agent Prompt

Once your agent is connected, try these prompts to trigger tool calls:

"Search for laptop products under $500"

Triggers: search_products tool from Demo Store

"Get a shipping quote from NYC to LA for a 3kg package"

Triggers: get_quote tool from Demo Shipping

"Create an order for product prod-1, quantity 2"

Triggers: create_order tool from Demo Store (includes wallet confirmation)

Troubleshooting

Auth Errors (401 / 403)

  • Check that you are passing the correct API key in the right header
  • For "Open" integrations (auth_type: none), no key is needed
  • Ensure the header name matches what the integration expects (e.g., x-api-key)

Timeouts

  • MeshHub playground has a 15-second timeout per tool call
  • If the upstream API is slow, try again or use a simpler query
  • For production agents, set appropriate timeout values in your HTTP client

Wrong Parameters

  • Check the input schema on the integration detail page for required fields
  • Ensure values match the expected types (string, number, etc.)
  • Use the Playground to test before integrating into your agent