Clawshow MCP Server

Instant Backend for SMBs: pages, payments, notifications, orders, inventory, reports

Remote serverstreamable-http

What is the Clawshow MCP server?

Connect Clawshow to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Instant Backend for SMBs: pages, payments, notifications, orders, inventory, reports. The clawshow mcp server is what makes that connection.

What the server does

Call any tool without a namespace to use demo data: - manage_orders(action="query") → sample orders - generate_payment(amount=10, currency="eur", provider="stancer", description="Demo", namespace="demo") → real test payment link - send_esign_request(template="enrollment_contract", signer_name="Demo User", signer_email="demo@test.com", fields={}, namespace="demo") → signing page URL

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

  • generate_business_page — generate_rental_website
  • generate_payment — verify_payment
  • send_notification — send_esign_request
  • generate_report — manage_inventory
  • manage_orders — manage_bookings
  • Payments — The Payments tool exposed by this server
  • Notifications — The Notifications tool exposed by this server
  • Engines — The Engines tool exposed by this server
  • Architecture — All Tools live in single clawshow-mcp-server. One MCP URL: mcp.clawshow.ai/sse Per decision: 决策 #2, #32 (unified architecture)

Installation

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

Where it fits

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Clawshow's toolset — generate_business_page, generate_payment, send_notification and 6 more — is a fair guide to whether it matches your workflow. It is maintained by jason2016; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Clawshow's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Worth knowing first

  • Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
  • With 9 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Clawshow.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
generate_business_pagegenerate_rental_website
generate_paymentverify_payment
send_notificationsend_esign_request
generate_reportmanage_inventory
manage_ordersmanage_bookings
PaymentsThe Payments tool exposed by this server.
NotificationsThe Notifications tool exposed by this server.
EnginesThe Engines tool exposed by this server.
ArchitectureAll Tools live in single clawshow-mcp-server. One MCP URL: mcp.clawshow.ai/sse Per decision: 决策 #2, #32 (unified architecture).

How to install the Clawshow MCP server

{
  "mcpServers": {
    "clawshow": {
      "url": "https://mcp.clawshow.ai/sse"
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Example prompts to try

  • Use Clawshow to generate business page.
  • Use Clawshow to generate payment.
  • Use Clawshow to send notification.

Frequently asked questions

It connects Clawshow to MCP-compatible AI assistants such as Claude and Cursor, exposing 9 tools (generate_business_page, generate_payment, send_notification, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Clawshow directly.