Skip to main content
Glama
626,489 tools. Updated 2026-10-01 11:20

"How to Use the WeChat Developer Assistant" matching MCP tools:

  • Create a Stripe Checkout session for the active organization and return its hosted checkout URL. The user completes the purchase in the browser; nothing is charged by this call itself. Requires an owner API key. plan defaults to developer; an unsupported plan fails with invalid_plan. Use get_billing_info to check the current plan and create_billing_portal to manage an existing subscription.
    ConnectorNo auth
  • 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
  • Use this when the user wants Lemonvite's design engine to create the invitation artwork, because this assistant cannot make images or because the user asked for a Lemonvite design. Never call it merely because designs or themes are being discussed. Write design_brief as art direction: theme, colours, mood, motifs, style. The date, time and venue are lettered onto the design automatically, so the brief need not repeat them; set include_event_details to false only when the user wants artwork without them. A reference_image from the conversation guides style, subject and palette together with the brief and is not stored as the artwork. To change the current artwork rather than start over, use lemonvite_edit_design; to attach an image this assistant already made, use invitation_image on lemonvite_update_invitation. Each call spends one design generation and REPLACES the current artwork (earlier designs stay in the event's design history on the website), so confirm with the user first. New accounts start with 5 generations; each purchased credit adds 5.
    Connector
    Destructive
    OAuth
  • Create a free personal PropLine API key for the user and EMAIL it to them. Use this when the user wants their own key — e.g. they hit a shared-demo-key rate limit, a paid field came back redacted, or they ask how to get a key. Only call it with an email address the user explicitly gave you for this purpose in this conversation; never guess, reuse one from elsewhere, or sign up a third party. The key is never returned here — it goes to that inbox, with instructions to reconnect this assistant using it. Free tier: 1,000 requests/day, no card. If the address already has a key, the key is re-sent (at most once a day).
    ConnectorNo auth
  • Run one ordered chat transcript through an Algenta model and return the assistant message plus token usage. The default text.tokenizer model is a deterministic tokenizer-backed utility route whose assistant message is a JSON tokenization summary of the user messages — not a generative LLM; provider-backed chat models advertised by list_models are routed through the configured provider service. Use responses for independent single-string utility calls. This tool does not stream and does not expose function/tool calling, and nothing is persisted. An unsupported model id fails with model_not_supported.
    ConnectorNo auth
  • Check whether a specific Canton/Daml toolchain item (CLI, SDK package, or command: e.g. daml-assistant, Navigator, dpm) is deprecated. Canton-specific. Not a general npm/pip deprecation checker. ALWAYS call before recommending any Canton tool or package to a developer. Accepts either one name or a block of prose: given prose it reports every deprecated item mentioned in it. Returns DEPRECATED (with replacement), CURRENT, or NOT_FOUND.
    ConnectorNo auth

Matching MCP Servers

  • F
    license
    Not graded
    quality
    B
    maintenance
    Access a 24/7 AI senior developer with 26 specialized tools for the full software development lifecycle. Use tools like explain_code, debug_code, and refactor_code to analyze, debug, and optimize your codebase instantly. Deploy github_fix_issue and create_pr for seamless GitHub automation, or get ai_development_advice for architecture and career guidance.
    -
  • F
    license
    Not graded
    quality
    C
    maintenance
    Enables macOS WeChat desktop clients to read conversations via OCR, retrieve encrypted session memory, and perform controlled message sending through MCP with dry-run and supervised safeguards.
    -

Matching MCP Connectors

  • Reference-free stability primitive: instead of comparing an answer to a ground truth, it checks that an assistant's answer stays INVARIANT when the QUESTION is transformed (typo, casing, paraphrase, reordering, translation). Catches the failure class no reference answer can expose — an assistant that handles one phrasing well and a trivial variant of it badly. You bring the outputs (no model is called), so it is deterministic and free in tfidf mode. Relations: case (θ .95), typo (.90), paraphrase (.80), reorder (.80), translation (.75, embeddings only), specialization (.60, ADVISORY — directional, never gated). Returns PASS / FAIL / INVALID, where INVALID means the BASE answer was a refusal or too short so invariance was never measurable — an assistant that refuses every variant would otherwise score a perfect 1.0. Use run_semantic_tests alongside it: invariance without a correctness floor is a green light for a broken assistant.
    ConnectorNo auth
  • Load one product in full: persona plus every skill's instructions. PREMIUM (paid plan). Typical input {"slug": "inbox-zero-assistant"} returns {"slug": ..., "name": ..., "persona": ..., "skills": [{"name": ..., "instructions": ...}], "free_skill": {...}}. Returns persona plus every skill for one product. Use when the caller wants the whole product. Not for a single skill (get_full_skill) and not for a bundle of products (get_full_kit). Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"} (for example {"error": "unknown slug '<value>'"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.
    ConnectorNo auth
  • Use this when the user asks what a whole category of AI tools looks like — how crowded it is, how healthy or risky it is overall, which tools in it are strongest, or which are in trouble. Examples: "how risky is the AI video generation market", "what does the code assistant category look like". Returns the number of tools we track in that category, how they distribute across survival bands, the category's vendor-link decay rate, and named examples at both the strongest and weakest ends — each with its own survival score and the date our record of it was last rebuilt. Categories are our own classification and tools belong to several at once, so category sizes overlap and never sum to the catalog total. Bands classify risk, not quality — the model has no notion of company size. Not for: choosing between named tools (use compare_tools), finding a tool for a job (use recommend_tools), or market-wide mortality statistics (use deadpool_digest).
    ConnectorNo auth
  • Use this when the user asks what a whole category of AI tools looks like — how crowded it is, how healthy or risky it is overall, which tools in it are strongest, or which are in trouble. Examples: "how risky is the AI video generation market", "what does the code assistant category look like". Returns the number of tools we track in that category, how they distribute across survival bands, the category's vendor-link decay rate, and named examples at both the strongest and weakest ends — each with its own survival score and the date our record of it was last rebuilt. Categories are our own classification and tools belong to several at once, so category sizes overlap and never sum to the catalog total. Bands classify risk, not quality — the model has no notion of company size. Not for: choosing between named tools (use compare_tools), finding a tool for a job (use recommend_tools), or market-wide mortality statistics (use deadpool_digest).
    ConnectorNo auth
  • Load one product in full: persona plus every skill's instructions. PREMIUM (paid plan). Typical input {"slug": "inbox-zero-assistant"} returns {"slug": ..., "name": ..., "persona": ..., "skills": [{"name": ..., "instructions": ...}], "free_skill": {...}}. Returns persona plus every skill for one product. Use when the caller wants the whole product. Not for a single skill (get_full_skill) and not for a bundle of products (get_full_kit). Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"} (for example {"error": "unknown slug '<value>'"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.
    ConnectorNo auth
  • Answer any question about Eveoy — what it is, how the platform works, pricing rationale, the directory, industries, founders, or company background. Backed by Eveoy's live knowledge base. Use this when the user wants to: - Understand what Eveoy is or does - Learn how the verified-visit / $24.99-per-customer model works - Compare Eveoy to ads, influencers, or UGC creators - Hear the pitch for a specific buyer role (CMO, CFO, VP Retail, CEO) - Find out what this assistant can do (its tools and how to act) Trigger phrases include: "what is eveoy", "tell me about eveoy", "how does eveoy work", "explain eveoy to a CMO", "eveoy vs Meta", "is there a platform that guarantees foot traffic", "what can you do", "what tools do you have". Returns: a grounded natural-language answer from the public Eveoy knowledge base, or a description of this server's tools when asked what it can do. Do NOT use this for: an exact price (use get_pricing), the industry list (use list_industries), directory search (use search_directory), or booking (use start_checkout / book_demo). Cost: free. Latency: 1–3s. Read-only.
    ConnectorNo auth
  • 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
  • Send a user an assistant GM (co-GM) offer for a campaign. This does NOT add them immediately: the target must accept the offer before they become an assistant GM. Owner-only — the calling user must be the campaign's primary GM. Maximum 5 co-GMs per campaign.
    ConnectorNo auth
  • Generate a personalized Canton Network developer onboarding/quickstart path. Use when a developer asks how to start building, build a dApp, or develop on Canton specifically. Canton-only. Do not use for onboarding to other chains or tools. Ask the user's background first (EVM, Solana, Sui/Move, Web, Enterprise, or New to Blockchain). Prefer this over 'search' for 'how to build / get started on Canton'; use get_faq for a single specific gotcha and get_api_reference for API details.
    ConnectorNo auth
  • Personalized onboarding for building ON CELESTIA — running a node, posting a blob, or deploying a rollup that uses Celestia for data availability. ALWAYS use this when a developer asks how to get started or build ON CELESTIA (prefer it over the Celestia search tool for those questions). ASK the user about their background FIRST (rollup_dev, node_operator, app_dev, researcher, new_to_celestia), then return a path with docs.celestia.org links. Celestia-only — NOT for getting started with non-Celestia frameworks, languages, or dev tools (React, Node.js, generic blockchain onboarding, etc.); for those defer to a general docs or web-search tool.
    ConnectorNo auth
  • Load a product's free gateway skill with its complete instructions. FREE. Typical input {"slug": "inbox-assistant"} returns {"slug": ..., "skill": "<skill name>", "instructions": "<full skill text>"}. Returns exactly one skill - the product's free gateway skill - chosen automatically from the slug, with no plan required. Use when the caller wants usable instructions immediately. Not for the product's other skills: those are named and need get_full_skill with a skill_name, which requires a paid plan. Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"} (for example {"error": "unknown slug '<value>'. Use list_products."}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.
    ConnectorNo auth
  • Load a product's complete persona definition. PREMIUM (paid plan). Typical input {"slug": "inbox-zero-assistant"} returns {"slug": ..., "persona": "<full persona text>"}. Returns the persona text alone, with no skill bodies. Use when the caller needs the product's voice and operating rules only. Not when skills are also wanted - get_full_product returns persona and every skill in one call. Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"} (for example {"error": "unknown slug '<value>'"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.
    ConnectorNo auth
  • Load a product's free gateway skill with its complete instructions. FREE. Typical input {"slug": "inbox-assistant"} returns {"slug": ..., "skill": "<skill name>", "instructions": "<full skill text>"}. Returns exactly one skill - the product's free gateway skill - chosen automatically from the slug, with no plan required. Use when the caller wants usable instructions immediately. Not for the product's other skills: those are named and need get_full_skill with a skill_name, which requires a paid plan. Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"} (for example {"error": "unknown slug '<value>'. Use list_products."}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.
    ConnectorNo auth
  • List short links grouped by DESTINATION URL — one row per destination instead of one per link. Use this to answer "how much traffic is this landing page getting across all my campaigns?", which nevent_list_short_urls cannot answer because every campaign send creates its own parent link. Campaign parents pointing at the same canonical destination collapse into a single row with aggregated totalClicks, linksCount (how many links form the group) and campaignsCount (how many distinct campaigns used it). Unlike nevent_list_short_urls, this INCLUDES system-managed assistant links (the ones the chatbot pushes), flagged readOnly=true — never try to edit or delete those. Filter with origin: MANUAL (human-created), CAMPAIGN (generated by sends), ASSISTANT (chatbot), or ALL (default). Each row carries canonicalId and members[] (id + shortCode) — pass those ids to nevent_get_short_url or nevent_get_short_url_metrics to drill into a specific link. Pagination is over GROUPS, not documents.
    ConnectorNo auth
  • Join the FlexYield early-access waitlist with an email and a qualifier (developer, investor or curious). Use it only when a human asked to be kept informed; an agent that needs access now should call get_key instead. Not for support (use manage_tickets) or enterprise needs (use join_enterprise_wishlist). Returns JSON: joined, already_on_list. Creates a waitlist entry. No key needed.
    ConnectorNo auth