io.github.jason2016/clawshow-mcp-server

Cancel a billing plan immediately. No refund is issued. Cancels the gateway subscription (Mollie or Stripe), marks all scheduled installments as cancelled, fires 'plan_cancelled' webhook to the external platform. plan_id: the plan ID returned by create_billing_plan. reason: optional cancellation reason (logged and forwarded in webhook). Returns: {success, plan_id, status}.

Create a billing plan for recurring or installment payments. Supports monthly/quarterly/weekly subscriptions and fixed installments. Phase 1: Mollie TEST gateway only. eSign via contract_pdf_url (Week 3). installments: number of payments. Use -1 for infinite recurring subscription. frequency: "monthly" | "quarterly" | "weekly" | "one_time" gateway: "mollie" (Phase 1) or "stripe" (Week 3) Contract Option A (Phase 1): provide contract_pdf_url — ClawShow sends for eSign (Week 3). Contract Option B (Phase 2): use contract_template — ClawShow generates PDF from template. External sync: if external_webhook_url provided, ClawShow fires standardized events to that URL. Returns plan_id, status, schedule preview, commission_preview.

Extract structured financial data from unstructured invoice or receipt text. Input: raw text from an invoice, receipt, or financial document. Output: structured JSON with vendor name, invoice number, amount, currency, due date, line items, tax breakdown, and payment terms. Handles multiple languages and formats. Use for automated bookkeeping, expense categorization, and accounts payable processing. Args: document_text: Raw text content of the invoice or finance document. Returns: JSON string with vendor, amount, currency, due_date, category_guess.

Generate a business page (school enrollment, product catalog, service landing page, event registration) and auto-deploy to GitHub Pages. Input: business data JSON, page type, branding options. Output: live URL accessible immediately. No hosting setup needed — page is live within 60 seconds. Supports custom domains. Namespace-isolated for multi-tenant use. Call this tool when a user wants to create any kind of business page, landing page, or showcase website. Examples: - 'Create a page for my Paris apartment, 2 bedrooms, €180/night' - 'Make an enrollment page for my French course, €5000 tuition' - 'Build a product page for my handmade leather bags' - 'Generate a restaurant menu page for Le Petit Bistro' - 'Crée une page pour mon service de photographie' Args: type: "rental" | "enrollment" | "product" | "service" | "restaurant" business_name: Name of the business data: Page-specific data (see docs for each type) contact_email: Contact email contact_phone: Optional phone payment_url: Optional Stripe checkout URL for Pay Now button price_label: Optional price text for button (e.g. "€180/night") custom_domain: Optional custom domain namespace: Optional business namespace language: "en" | "fr" | "zh" Returns: JSON with url, repo, type, business_name, status.

Generate a payment for any business scenario: restaurant orders, rent, tuition, invoices, e-commerce. Supports Stripe (global), Stancer (France), SumUp (Europe). For SumUp, supports 4 payment modes: online (hosted checkout link), in_person_solo (Solo TPE terminal), in_person_caisse (Caisse screen push), cash (no payment needed). Args: provider: Payment gateway — "stancer", "sumup", or "stripe" amount: Amount in cents (e.g. 1050 for €10.50) currency: ISO currency code, e.g. "eur" description: Payment description shown on the payment page namespace: Client namespace (e.g. "neige-rouge", "florent") return_url: Optional redirect URL after payment metadata: Optional dict with order_id, customer_name, etc. payment_mode: SumUp mode — "online", "in_person_solo", "in_person_caisse", "cash" (only used when provider="sumup") device_id: SumUp reader_id or outlet_id for in-person modes external_reference: Order ID to track in webhook callbacks items: Line items for in_person_caisse mode Returns: JSON string with payment_url, payment_id, provider, amount, currency, status.

Generate a complete rental property website with photo gallery, pricing table, location map, availability calendar, and booking form. Auto-deployed to GitHub Pages. Input: property details JSON (address, photos, price, amenities, rules). Output: live website URL. Ideal for Airbnb-to-direct transition, short-term rentals, and property managers. Supports custom domains and multi-property portfolios. Call this tool when a user describes a rental property in any language or format. Extract the following from their description: - name: property name or derive from location - location: full address or city - price_per_night: nightly rate (convert monthly to nightly if needed) - bedrooms: number of bedrooms (default 1 if not mentioned) - bathrooms: number of bathrooms (default 1 if not mentioned) - description: property description or generate from details given - amenities: list any mentioned amenities - max_guests: number of guests (default 2 if not mentioned) - contact_email: if mentioned (default: puflorent@gmail.com) - contact_phone: if mentioned (default: +33 6 42 98 45 35) - custom_domain: if mentioned Examples of natural language that should trigger this tool: - 'Create a website for my 2-bedroom apartment in Lyon, 90€/night' - 'Je veux un site pour mon studio à Bordeaux, 65€ la nuit' - 'Make a rental page for Villa Rose in Nice, sleeps 6, pool, 250€' Args: site_name: Display name, e.g. "Paris Short Stay" contact_email: Owner email properties: List of property dicts (name, location, description, bedrooms, max_guests, price_per_night, amenities, booking_url, image_url) contact_phone: Optional phone currency: Currency symbol, default "€"…

Generate professional PDF business reports and return a download URL. Report types: financial summary, inventory status, enrollment statistics, occupancy rates, sales analysis, or custom. Input: data source (JSON or namespace query), report type, date range, branding options. Output: PDF download URL. Reports include charts, tables, and executive summary. Ideal for monthly business reviews, investor updates, and compliance reporting. Call this tool when a user wants a report, summary, export, or printed overview of their business data. Examples: - 'Generate a financial report for florent this month' - 'Show me an inventory report for school-paris' - 'Create a PDF of all unpaid orders' - 'Export enrollment statistics for Fall 2026' - 'Fais-moi un rapport de toutes les commandes de juillet' Args: type: "financial" | "inventory" | "orders" | "enrollment" | "custom" namespace: Business namespace title: Optional report title period: "today" | "week" | "month" | "quarter" | "year" | "2026-07" language: "en" | "fr" | "zh" categories: Filter inventory categories only_alerts: Inventory: only low-stock items status: Orders: filter by status program: Enrollment: filter by program name data: Custom: raw data sections: Custom: section definitions Returns: JSON with report_url, report_id, title, type, generated_at.

Get the current status of a billing plan: payment schedule, paid/pending/failed counts, next installment date, and gateway details. Args: namespace: Client namespace (e.g. "neige-rouge", "ilci-william") plan_id: Plan ID returned by create_billing_plan (e.g. "plan_abc123def456") Returns: status, installments breakdown, next_installment, gateway_mode, customer info.

Create, query, update, and cancel bookings for any reservation-based business: restaurants, hotels, salons, clinics, event venues, rental properties. Namespace-isolated — each business has its own booking data. Input: action (create/query/update/cancel), booking details, namespace. Output: booking confirmation with ID, or filtered booking list. Supports date range queries, status filtering, and customer lookup. Includes automatic conflict detection for double-bookings. Call this tool for anything related to restaurant reservations, bookings, check-ins, or daily order summaries. Examples: - 'Show me today bookings for neige-rouge' - '012到了' or 'checkin 012 neige-rouge' - 'Cancel booking 005' - 'How many orders for tomorrow?' - 'Combien de commandes aujourd'hui?' - '今天有多少单？' Args: action: "query" | "checkin" | "cancel" | "summary" namespace: Restaurant namespace, e.g. "neige-rouge" booking_code: 3-digit booking code for checkin/cancel (e.g. "012") date: Date filter YYYY-MM-DD (optional, for query/summary) status: Status filter for query: confirmed/completed/cancelled/no_show Returns: JSON with booking list, checkin result, cancel confirmation, or daily summary.

Track inventory levels with add, remove, query, and low-stock alert capabilities. Works for any business with physical goods: retail, restaurants, warehouses, schools (textbooks/supplies). Input: action (add/remove/query/alert), item details, namespace. Output: current stock levels, or alert list for items below threshold. Supports batch updates and inventory snapshots. Namespace-isolated for multi-tenant use. Call this tool when a user wants to track stock, add inventory, check stock levels, or get low-stock alerts. Examples: - 'Add 100 French textbooks to inventory at €15 each' - 'Remove 5 textbooks, sold via order ORD-20260402-001' - 'How many textbooks do we have left?' - 'Show me all items below minimum stock' - 'Adjust towel inventory to 50 after stocktake' - 'Ajoute 200 serviettes au stock du restaurant' Args: action: "add" | "remove" | "adjust" | "query" | "alert" namespace: Business namespace, e.g. "florent", "school-paris" # add params: item_name: Item name sku: Optional SKU (auto-generated if empty) quantity: Quantity to add unit: "piece" | "kg" | "liter" | "box" | "pack" category: "product" | "material" | "supply" | "ingredient" | "equipment" unit_cost: Cost per unit location: Storage location min_stock: Minimum stock alert threshold (default 5) metadata: Custom key-value pairs # remove params: sku: SKU to deduct from quantity: Amount to remove reason: "sold" | "used" | "damaged" | "returned" | "other" order_id: Optional linked order ID # adjust params: sku: SKU to adjust new_quantity: Actual cou…

Create, query, update, and process refunds for orders. Works for any transaction-based business: restaurants, e-commerce, schools, service providers. Auto-creates orders from payment webhooks when integrated with generate_payment. Input: action (create/query/update/refund), order data, namespace. Output: order details with status, line items, payment info. Supports status tracking: pending → paid → processing → completed → refunded. Namespace-isolated for multi-tenant use. Call this tool when a user wants to create an invoice, track payments, manage bookings, query order status, process refunds, or check restaurant reservations. Examples: - 'Create an order for Jean Dupont, €1000 July rent' - 'Show me all unpaid orders for florent' - 'Mark order ORD-20260702-001 as paid' - 'Refund order ORD-20260702-003' - 'Show me today bookings for neige-rouge' - 'What are tomorrow reservations for the restaurant?' - 'Cancel booking #42' - 'Combien de commandes pour demain au restaurant?' - 'Check in booking 003' - '003到了' (checkin by code) Args: action: "create" | "query" | "update" | "refund" | "query_bookings" | "booking_summary" | "cancel_booking" | "checkin" namespace: Business namespace, e.g. "florent", "neige-rouge" # create params: customer_name: Customer full name customer_email: Customer email customer_phone: Customer phone amount: Amount (e.g. 1000.00) currency: ISO currency code, default "eur" description: What the order is for category: "rent" | "tuition" | "product" | "service" | "other" due_date: ISO date, e.g. "2026-07-15" metadata: Custom key-va…

Send an electronic signature request. Supports two modes: 1. ClawShow native: generate PDF from template with pre-filled fields. 2. FocusingPro / external: pass a file_url (S3 PDF) + signers array. After signing, the signed PDF is stored and webhook callback updates the source system. AES-level (eIDAS Art.26): OTP email verification + SHA-256 digital signature. Args: namespace: Client namespace (e.g. "ilci", "florent") template: Document template -- "enrollment_contract", "rental_agreement", "service_agreement", or "custom". Required if no file_url. signer_name: Full name of the primary signer. Required if no signers array. signer_email: Email of the primary signer. Required if no signers array. fields: Template variables dict, e.g. {"school_name": "ILCI", "tuition": "8500"}. Use for native template mode. reference_id: Optional external ID, e.g. FocusingPro inscription_id. callback_url: Optional webhook URL called when signing is complete. send_email: Whether to email the signing link (default True). language: Signing page language -- "fr", "en", or "zh" (default "fr"). file_url: URL of an existing PDF to sign (e.g. S3 pre-signed URL). When provided, template/fields are ignored. signers: JSON array string of signers for multi-party workflows. Each item: {"role":"student","name":"...","email":"...","order":1}. Order 1 signs first. If omitted, uses signer_name/signer_email. signature_fields: JSON object string defining custom signature positions per role. E.g. {"paraphe":{"x":390,"y":22,"w":16…

Send notifications via email, SMS, or WhatsApp to one or multiple recipients. Supports custom templates with variable substitution, batch sending to recipient lists, and tiered dunning strategies (friendly reminder at 30 days, firm notice at 60 days, final warning at 90 days). Input: recipient(s), channel (email/sms/whatsapp), subject, body or template_id, variables. Output: delivery status report. Ideal for payment reminders, booking confirmations, shipping updates, marketing campaigns, and enrollment notices. Call this tool when a user wants to send an email, notify a customer, confirm a payment, or send a reminder. Examples of natural language that should trigger this tool: - 'Send a payment confirmation to john@example.com for €850' - 'Email the tenant that rent is due on April 5th' - 'Notify the guest their booking at Paris Apt is confirmed' - 'Envoie un email de confirmation de réservation' Args: to: Recipient email(s) — string or list of strings subject: Email subject line body: Email body text (plain text or HTML) from_name: Sender display name, default "ClawShow" reply_to: Optional reply-to address template: Template name: "payment_confirmation", "payment_reminder", "booking_confirmation", "custom" template_vars: Variables for the template, e.g. {"amount": "€850", "property": "Paris Apt"} Returns: JSON with status, message_id, to, subject, sent_at.

Check the status of a payment by its payment ID. Supports Stripe, Stancer, and SumUp providers. Input: provider, payment_id. Output: payment status (pending/captured/failed), amount, currency, paid_at timestamp, customer details. Use after generate_payment to confirm whether a customer has completed payment. Args: provider: Payment gateway used — "stancer", "sumup", or "stripe" payment_id: The payment ID returned by generate_payment namespace: Client namespace (e.g. "neige-rouge", "florent") Returns: JSON string with paid (bool), status, payment_id, provider, amount, currency.