Skip to content

Try the Demo

We run a public ToolMesh demo at demo.toolmesh.io — a single MCP endpoint, two HN backends, zero API keys. Just enough to experience the complete ToolMesh flow: OAuth login, tool discovery, credential injection, execution, and audit.

Once connected, try these prompts. Start with “Use ToolMesh to” to ensure your AI assistant uses the MCP tools instead of its built-in web search:

  • “Use ToolMesh to get the top 5 stories on Hacker News with their scores and comment counts.” — live data via the Firebase API
  • “Use ToolMesh to search HN for stories about ‘credential isolation’ — are there any recent discussions?” — full-text search via Algolia, filtered by recency
  • “Use ToolMesh to compare the karma of HN users ‘dang’ and ‘pg’ — who has more?” — two API calls, structured comparison

Try combining both backends in a single prompt:

“Use ToolMesh to search HN for recent articles about AI agents, then get the full comment thread for the most discussed one.”

  1. Open a new chat and click the + button in the input area
  2. Click Connectors
  3. Click Manage Connectors
  4. Click + (top right)
  5. Click Add custom connector
  6. Enter the URL: https://demo.toolmesh.io/mcp
  7. Click Add

Claude Desktop opens a browser window for OAuth login. Log in with dadl / toolmesh.

Add to your config file (~/Library/Application Support/Claude/claude_desktop_config.json on macOS, %APPDATA%\Claude\claude_desktop_config.json on Windows):

{
"mcpServers": {
"toolmesh-demo": {
"url": "https://demo.toolmesh.io/mcp"
}
}
}

Restart Claude Desktop after editing.

BackendToolsWhat it does
Hacker News (Firebase API)10Browse stories, items, users, polls, and live feeds
Algolia HN Search4Full-text search across stories and comments

The built-in echo tools are always available — useful for verifying your connection:

ToolWhat it does
echo_echo(message)Returns whatever you send it
echo_add(a, b)Adds two numbers
echo_time()Returns the current UTC time

All tool calls run through the full ToolMesh pipeline: authentication, credential injection, execution, and audit logging.

This demo is intentionally narrow: one public MCP endpoint, two read-only HN backends, no custom APIs — just enough to experience the complete ToolMesh flow without any setup overhead. It is a shared instance with no SLA.

The DADL registry has definitions for 14 APIs with 1,100+ tools. To connect your own APIs, run your own instance: