Skip to main content
Glama
649,985 tools. Updated 2026-10-10 21:34

"WeChat" matching MCP tools:

  • Create a shareable Pairoa invite link for the current user. Returns { ref, url, share_text }. ONLY works after the user has claimed an account (claim_account). Otherwise returns AUTH_REQUIRED — guide them to claim first (claiming happens automatically on their first match). The 'share_text' is ready to forward AS-IS — to a Slack/Discord/WeChat group, a tweet, or a DM. Relay it to the user so they can paste it wherever they like; offer the bare 'url' too if they only want the link. Invites carry NO reward and are purely a convenience for word-of-mouth. Don't over-promote or nag. We do not track who the invitee is — only a private count of how many people a link brought in.
    ConnectorOAuth
  • 🔌 Connect a messaging channel to this workspace, or find out how. Call with no `channel` for the catalogue: every channel, its connect_mode and its link. Call with `channel` only to learn what to ask the person for (credential_fields). Call with `channel` + `credentials` to connect a credentials channel: email over IMAP with an app password, telegram_bot with a bot token, line with the channel access token and channel secret, avito. Channels that need a QR scan, a phone code or a browser sign-in (telegram, whatsapp, instagram, facebook, email (Google sign-in), youtube, tiktok, x, threads, linkedin, wechat, zalo, maxru, the voice carriers) cannot be connected from here: the tool answers success with needs_person=true and the link https://dialogbrain.com/connect/<channel>, which opens the connection dialog for that channel. Give the person that link; do not tell them to look for it in settings. A website widget is not connected here at all: use widgets.create.
    ConnectorAPI key
  • 🔌 Connect a messaging channel to this workspace, or find out how. Call with no `channel` for the catalogue: every channel, its connect_mode and its link. Call with `channel` only to learn what to ask the person for (credential_fields). Call with `channel` + `credentials` to connect a credentials channel: email over IMAP with an app password, telegram_bot with a bot token, line with the channel access token and channel secret, avito. Channels that need a QR scan, a phone code or a browser sign-in (telegram, whatsapp, instagram, facebook, email (Google sign-in), youtube, tiktok, x, threads, linkedin, wechat, zalo, maxru, the voice carriers) cannot be connected from here: the tool answers success with needs_person=true and the link https://dialogbrain.com/connect/<channel>, which opens the connection dialog for that channel. Give the person that link; do not tell them to look for it in settings. A website widget is not connected here at all: use widgets.create.
    ConnectorAPI key
  • 🔌 Connect a messaging channel to this workspace, or find out how. Call with no `channel` for the catalogue: every channel, its connect_mode and its link. Call with `channel` only to learn what to ask the person for (credential_fields). Call with `channel` + `credentials` to connect a credentials channel: email over IMAP with an app password, telegram_bot with a bot token, line with the channel access token and channel secret, avito. Channels that need a QR scan, a phone code or a browser sign-in (telegram, whatsapp, instagram, facebook, email (Google sign-in), youtube, tiktok, x, threads, linkedin, wechat, zalo, maxru, the voice carriers) cannot be connected from here: the tool answers success with needs_person=true and the link https://dialogbrain.com/connect/<channel>, which opens the connection dialog for that channel. Give the person that link; do not tell them to look for it in settings. A website widget is not connected here at all: use widgets.create.
    ConnectorAPI key
  • Send this page’s CURRENT LIVE version to WeChat as a service-account template message, to the people in this workspace (the creator plus every member; you are excluded when “also send to me” is off). It is never sent to clients — forward them the link instead. Pass `include_subscribers: true` to also send it to this page’s subscribers (each person gets a version once, and at most one reminder a day). The receipt’s first line is the same sentence the publish receipt uses — “This time it will notify: you, 2 teammate(s), 5 subscriber(s) (4 reachable)” — relay it to the user as is. Each person receives their own personal link, created on first send and reused afterwards, so reading activity shows who opened it. This ignores the workspace’s automatic-push switch: it is a manual send. People who have not followed the service account do not receive it, and the receipt reports those separately (not followed / refused / no WeChat binding) — that is not an error. A page with no live version is rejected with a clear 409 rather than silently doing nothing. When YOU did not receive it (no WeChat binding or not following), the receipt includes a binding QR code (an image plus `bind_qr_image_url`): once the user scans it in WeChat, the binding completes within seconds and this page is re-sent to them only — no second call needed. Never tell the user to “sign in by scanning in WeChat” — that creates a separate account.
    ConnectorAPI key
  • Record who this workspace is: company or organization name, industry, who the page is mainly shared with, and one sentence on what it is used for. The web form for this was retired; this is the only way to write it. company_name is the sole source of the company name on WeChat share cards — without it recipients see a generated workspace name. Fields passed are merged into the existing profile and omitted fields are left unchanged, so changing only the company name needs only company_name. A first-time profile must supply the required fields: with usage=work, company name and industry are required; customer_type and use_case are required in both modes. Validation matches the retired web form exactly: placeholder names such as “personal”, “test” or “my company” are rejected (pass usage="personal" for personal use, which does not ask for company or industry), phone numbers and messaging handles are not allowed in the name, and industry must be one of the listed values. The profile is used for compliance and support and is not shown to viewers, except that the company name appears on share cards. Read-only members cannot call it.
    ConnectorAPI key

Matching MCP Servers

  • A
    license
    Not graded
    quality
    C
    maintenance
    Enables DeepSeek Harness to run bounded archive operations—diagnose, status, sync, and verify—against a local macOS chat database with integrity and privacy protections.
    MIT

Matching MCP Connectors

  • No money moves through LivePage: viewers scan your own code and funds go straight into your own collection account; the platform never places an order, collects or transfers funds. This tool only stores one QR-code image and shows it to viewers who submit a form that carries an amount. Replace this workspace's business collection QR code with the image you pass (base64 PNG or JPEG). After a viewer submits a form that carries an amount (set_form), they see the total due, this code and an “I have paid” button. COMPLIANCE: upload a BUSINESS collection code (merchant code) from WeChat Pay or Alipay, never a personal static code — under the barcode-payment rules in force since 1 March 2022, personal static codes may not be used to collect business payments. Replacing an existing code takes effect at once and the old image cannot be recovered; every change is written to the audit log and notifies the workspace owner on WeChat — this is the one setting where a mistake silently sends money elsewhere. Confirm with the user that it is their own merchant code before uploading; do not go and find an image or scrape a QR code off a web page. PNG or JPEG only, up to 2 MB, recognised by the image bytes themselves — a filename ending in .png proves nothing. Use remove_payment_qr to take it down.
    Connector
    Destructive
    API key
  • Removes the displayed QR-code image only; no funds are involved, because money never moves through LivePage. Take down this workspace's business collection QR code. Forms that carry an amount then show the total only, with no payment step; the form itself keeps collecting submissions. This cannot be undone, and you do not need it to swap codes — set_payment_qr replaces one directly. Removal is written to the audit log and notifies the workspace owner on WeChat. Payment marks already recorded on submitted rows are unaffected.
    Connector
    Destructive
    API key
  • Facts a foreign traveler needs for a Chinese city, checked against official sources and dated: which attractions need real-name/passport booking and when tickets release, official ticket channels (no resellers), whether hotels register foreign guests, whether foreign cards work via Alipay/WeChat, and honest local notes. Use for questions like 'how do I book X in <city>' or 'can foreigners stay in hotels in <city>'.
    ConnectorNo auth
  • Book a London airport or cruise port transfer to/from any UK address. Creates a REAL reservation — only call after the customer confirms. REQUIRED FLOW — collect ALL info before booking: 1. Ask: Where are you travelling from and to? 2. Ask: What date and time? (ask naturally, never expose technical formats like YYYY-MM-DD to the user) 3. MANDATORY — Ask: How many passengers travelling, and how many suitcases/large bags? You MUST collect the exact passenger count for EVERY booking, even when the customer has already chosen the largest vehicle (Executive 8 Seater / Minibus). Passenger count is operational data the driver needs (seat allocation, child-seat planning, dispatch) — never skip this question, never assume "they picked the big car so it doesn't matter". Do not proceed without an explicit number. 4. Call london_airport_transfer_quote to show prices and car options 5. Ask: Which car type would you like? (show the options with prices) 6. Ask: Passenger full name 7. Ask: Phone number (with country code) 8. Ask: Email address (for booking confirmation) 9. CRITICAL — POSTCODE / EXACT ADDRESS: NEVER book using only a city, town, or area name (e.g. "Windsor", "Manchester", "central London"). UK city names cover wide areas — pricing and the actual pickup/dropoff point will be wrong (a customer asking for "Windsor" must reach SL4, not Harrow HA). If you only have a city/town name, ask the customer for the FULL UK postcode (e.g. "SL4 5LP") AND the house/building number or name. If you have a postcode but no building number, ask for the building number/name. Do not guess, do not substitute a default. The exact door is required so the driver can reach the customer. 10. Ask the RIGHT transport detail based on booking type: - Airport PICKUP (customer arriving at airport) → Flight number (e.g. BA2534). Use validate_flight to verify and auto-detect terminal. - Airport DROPOFF (customer going TO airport) → Flight number is optional, don't require it - Cruise port pickup/dropoff → Cruise/ship name (e.g. P&O Ventura) - Train station pickup/dropoff → Train number or arriving from where - Non-airport/port/station route → skip, no transport detail needed 11. MANDATORY — Ask: "Do you have any special requests? For example, child seat, extra luggage, wheelchair, pet?" You MUST ask this every time. Do NOT skip it. If they mention a child seat, ask the child's age (baby seat 0-12mo, child seat 1-4yrs, booster 4-12yrs). Check seat limit for their car (Saloon 1, People Carrier 2, 8 Seater 3). If they ask for extra pickup or drop-off stops, tell them: "No problem! Extra stops will change the price — let me get you an updated quote." Then call london_airport_transfer_quote again with the full route. 12. MANDATORY — Before confirming the booking, inform the passenger: "We'll create your booking and you can pay the driver in cash on the day. If you prefer to pay online, you can do so via your manage booking link — we accept all major cards including Amex, Apple Pay, Google Pay, PayPal, Revolut, WeChat Pay, and AliPay." Wait for the customer to confirm. 13. Confirm all details with the customer, then call book_london_airport_transfer 14. AFTER booking: Share the reservation_id number (the numeric LT reference, e.g. "966811") and the manage_booking_url. This numeric reservation_id is what appears on the customer confirmation email AND what the manage-booking page accepts — it is the customer-facing reference. Do NOT mention the internal booking_reference (APL-XXXXXX format) to the customer; that is for our internal tagging only. Say: "Booking confirmed! Your reference is #{reservation_id}. You can track your driver, view booking details, and pay online (all major cards, Amex, Apple Pay, Google Pay, PayPal, Revolut, WeChat Pay, AliPay) using this link: {manage_booking_url}" - Share meeting_point instructions — ALWAYS include the terminal/location name from meeting_point.name (e.g. "Meeting point at Heathrow Terminal 2: ..."). Never show meeting instructions without specifying which terminal or location. IMPORTANT: Never call book_london_airport_transfer without customer confirmation. Always show the price first via london_airport_transfer_quote. IMPORTANT: The customer MUST choose a car type from the quote. Do NOT auto-select a car — always ask which one they want. IMPORTANT: Email address is REQUIRED — it is used for the booking management link and confirmation. IMPORTANT: Always inform the customer about payment options (cash or card/Apple Pay/Google Pay via manage booking link) BEFORE making the booking. IMPORTANT — PRICING: Quote the prices returned by london_airport_transfer_quote EXACTLY. Do NOT calculate discounts, do NOT round up or down, do NOT modify prices in any way. The prices returned are already final and include all surcharges. Never offer a discount unless it is explicitly returned by the quote tool. The MCP server is the only source of truth for pricing. BOOKINGS WITHOUT AN ACCOUNT: passenger_email is REQUIRED (the booking reference + this email is how the customer manages the booking later), and callers without an account may create at most 5 bookings per hour.
    ConnectorOAuth
  • Get an upload page for the user, who picks the files on their phone or computer (PDF / PPTX / images / large files). Which upload route: terminal ⇒ SPACE CLI (create_cli_token first); no terminal and text files up to 2 MB in total ⇒ publish_file; anything else or unsure ⇒ create_upload_link. Use this when you have NO terminal and the page is not text files within 2 MB (PDF, PPTX, images, large files), or when you are not sure: the platform creates an upload page link; give it to the user and they pick the files on their phone (WeChat works) or computer. The link is valid for 2 hours, succeeds only once, uploads only into this one page, and needs no login. To add a version to existing pages pass proposal_id (find it with list_proposals first); to create new pages pass title (optional folder_id). hold defaults to true: after approval the version is NOT released until the user confirms the preview and you call publish_version. After calling, hand the url to the user unchanged, say exactly which file to upload and ask them to come back and say “uploaded” when done; then call get_version with version_id every 15–30 seconds until it is no longer uploading: preview_ready or approved ⇒ give the user the preview URL to confirm; converting ⇒ keep polling; review ⇒ tell the user it is under manual review. After upload, the page also links to the page details for preview and sharing; keep following up through get_version and do not publish a version that is waiting to publish before the user confirms. For a single HTML or Markdown file whose content you already have, use publish_file instead — the user does not need to do anything. Keywords: publish · web page · webpage · link · share · share to WeChat · WeChat link · html · pdf · markdown · upload · LivePage · proposal.
    ConnectorAPI key
  • Publish an HTML / Markdown page or document straight to a WeChat-ready LivePage link; no terminal needed. Which upload route: terminal ⇒ SPACE CLI (create_cli_token first); no terminal and text files up to 2 MB in total ⇒ publish_file; anything else or unsure ⇒ create_upload_link. Use this when you have no terminal and the page is text files — HTML or Markdown pages and documents (no upload session to open first): pass the complete text content and the platform uploads it for you. Validation, content moderation (never released while moderation is unavailable), automatic release after approval or hold, and the result are exactly the same as finalize_upload. To add a version to existing pages pass proposal_id (find it with list_proposals first); to create new pages pass title (optional folder_id). One file: pass filename + content (.html / .htm / .md). When the page, styles and scripts are separate files, pass files: [{ path, content }] instead (one or the other): paths may include directories (e.g. css/style.css) and pages reference each other with relative paths; text files only (html / htm / md / css / js / mjs / json / svg / txt / csv), at most 50; the entry is manifest.entry, else index.html, else the only page. When a file is already at a public https URL (a cloud-drive public download link, a PDF link produced by another tool), pass { path, url } in files instead (e.g. [{ path: 'report.pdf', url: 'https://…' }]) and the platform fetches it — PDF, PPTX and images work: up to 50 MB each and 50 MB in total, at most 5 URLs, fetched within 30 seconds; only public addresses, and links that need a login cannot be fetched (fetch_failed, with fetch_* details in issues). UTF-8 text, up to 2 MB in total — anything larger is rejected with too_large and never truncated. The contents of images, PDF, PPTX and other binary files cannot be sent here: use a URL if there is one; otherwise without a terminal, use create_upload_link to give the user an upload page; with a terminal, use the SPACE CLI with create_cli_token. IMPORTANT: set hold=true whenever the user has not explicitly approved releasing this version, then give them the preview URL before publish_version. For a small edit (a typo fix) that should not notify anyone, pass quiet=true: workspace people and subscribers are not notified this time, and subscribers are notified on the next update. Keywords: publish · web page · webpage · link · share · share to WeChat · WeChat link · html · pdf · markdown · upload · LivePage · proposal.
    ConnectorAPI key
  • Open a direct upload session (a presigned URL per file): a SPACE CLI step; without a terminal do not open one. Which upload route: terminal ⇒ SPACE CLI (create_cli_token first); no terminal and text files up to 2 MB in total ⇒ publish_file; anything else or unsure ⇒ create_upload_link. It is not a separate upload route: you cannot PUT to its URLs, so the version stays stuck in uploading. Create a version and receive a presigned PUT URL for each file, valid for 15 minutes. Provide each relative path, byte size and SHA-256. Upload bytes to those URLs, then finalize_upload. PPTX files are converted to page images; unavailable fonts may be substituted. Quota errors include recovery guidance. Keywords: publish · web page · webpage · link · share · share to WeChat · WeChat link · html · pdf · markdown · upload · LivePage · proposal.
    ConnectorAPI key
  • 根据同一条视频的 object_id、object_nonce_id 和一级评论 comment_id 获取评论回复;用户已提供完整合法的 ID 组合时直接使用;已有作品链接、encrypted_object_id 或完整 object_id + object_nonce_id 组合但缺少必需 ID 时,按已有输入调用相应工具,从作品详情结果或一级评论结果补全;缺少作品定位信息时向用户索取;不要传回复项的 comment_id。
    ConnectorNo auth
  • 按搜索词搜索微信视频号视频,当前仅返回视频、不返回图文。用户需要按搜索词查找视频时使用;已有作品链接时直接使用详情或评论工具;已有合法 encrypted_object_id 时直接使用按 ID 详情或口播转文字工具,均无需先调用搜索;支持 sort_type、duration_range 和 page_token 翻页。
    ConnectorNo auth
  • Rename a page (keywords: rename, change title, retitle). The page name is what the web console list, list_proposals and folder page pages show. ★ The page name is separate from each version’s manifest title (the title readers see and the WeChat card title): publishing a new version never changes the page name. If the page title changed but lists still show the old name, rename it with this tool. - Changes only the name: links, versions, visibility and analytics stay the same, and no version’s content is modified. Every rename is audited.
    ConnectorAPI key
  • Call after all file PUTs finish. Verifies size, SHA-256, signatures, archive and HTML safety, manifest and content moderation. PDF/PPTX conversion may take 1–3 minutes; poll get_version every 15–30 seconds. Validation failures include file/line/fix issues; correct and upload the affected files. Review status blocks publishing. Moderation outages never release content. IMPORTANT: by default an approved update may immediately replace the live version. Set hold=true whenever the user has not explicitly approved releasing this version, then provide its preview URL for review. Keywords: publish · web page · webpage · link · share · share to WeChat · WeChat link · html · pdf · markdown · upload · LivePage · proposal.
    ConnectorAPI key
  • Make an approved version that is waiting to publish live, or roll back to an earlier approved version. Existing versions and comments remain. Call only after the user explicitly approves publishing or rolling back. Approved uploads without hold may already have become live. quiet=true makes this switch notify no one (workspace people or subscribers); releasing a held version keeps the quiet choice made at upload unless you pass it. Keywords: publish · web page · webpage · link · share · share to WeChat · WeChat link · html · pdf · markdown · upload · LivePage · proposal.
    Connector
    Destructive
    API key
  • List pages in the current workspace, including title, proposal_id, version state, current_version_id (the version clients see now), visibility, URL and recent activity. Use this to find existing pages rather than asking the user to copy IDs. Omit folder_id for all pages, use a folder ID for that folder, or null for pages not in any folder. In a new session, take current_version_id straight to preview_version or get_version: a proposal_id is not a version_id, and get_version on a proposal_id returns not_found. Use list_versions for earlier versions or a rollback. Existing legacy links are reported with their counts and link_ids: those links remain valid independently of default-link visibility, and revoke_share_link takes one of those link_ids to stop it. This is the only place a link_id is available. Each row also flags versions that exist but clients cannot see: pending_version is a version that never finished publishing (still uploading, converting or under moderation), and held_version is an approved version waiting to publish. When either is present, continue with that version (list_versions or get_version to see its state, publish_version to publish one that is waiting) instead of treating the page as unpublished and creating another one. When the result carries notices (the LivePage team has replied to feedback the user sent earlier; shown only once), pass them on to the user in a sentence or two before anything else. Keywords: publish · web page · webpage · link · share · share to WeChat · WeChat link · html · pdf · markdown · upload · LivePage · proposal.
    ConnectorAPI key
  • Owner only. Create a time-limited link for a teammate to sign in with WeChat and join this workspace as editor or viewer. Cannot grant owner through a shareable invitation. Returns a URL, QR URL and share_text the user may forward. This tool creates the invitation; it does not message anyone. Existing invitations can be revoked in Members.
    ConnectorAPI key