Skip to main content
Glama
260,860 tools. Last updated 2026-07-05 08:54

"A method for finding public WeChat accounts" matching MCP tools:

  • Attach a Stripe payment method to your Disco account. The payment method must be tokenized via Stripe's API first — card details never touch Disco's servers. Required before purchasing credits or subscribing to a paid plan. To tokenize a card, call Stripe's API directly: POST https://api.stripe.com/v1/payment_methods with the stripe_publishable_key from your account info. Args: payment_method_id: Stripe payment method ID (pm_...) from Stripe's API. api_key: Disco API key (disco_...). Optional if DISCOVERY_API_KEY env var is set.
    Connector
  • List the user's connected social media accounts (Instagram, TikTok, LinkedIn) so you can offer to publish content for them. Returns whether the Connectors add-on is active and the connected accounts. Read-only, no credits. Call this before offering to post, or when the user asks to publish.
    Connector
  • Core dossier check: Send a CORS preflight OPTIONS request to https://<domain>/ and return the access-control-* response headers. Use to verify CORS policy for a specific origin-method pair, or to check whether a domain allows cross-origin requests; provide origin and method to simulate a precise preflight, or omit to use defaults (origin: https://domainposture.com, method: GET). Single OPTIONS request via fetch, 5 s timeout. Returns a CheckResult: on success, {status:"ok", headers:{access-control-allow-origin,...}}; on failure, {status:"error", reason}.
    Connector
  • Search the DevMatch index for engineers matching a role or project. Input: pass the richest context you have — (1) a full job description (most common), (2) a synthesized brief after reviewing a company's public repo (README + stack + role needs — preferred over a bare URL when you've evaluated the project), (3) a public github.com repo URL (server fetches README/topics; private repos → paste README as text), or (4) an informal role brief. Longer, more specific input ranks better. Returns up to limit ranked candidates (default 20, max 50) with full inline profiles in structuredContent (view=candidates): login, name, bio, location, followers, html_url, top_repos, top_topics, signals, matched_projects, and contact. Results never include bots, CI, or service accounts — they are filtered out automatically. Use the optional `exclude` array (GitHub logins or org names) to drop additional accounts. AGENT MODE: consume structuredContent only. HUMAN MODE: MCP App panel shows candidate cards; use server instructions for text-only hosts. Do not call get_profile for handles already in these results unless the user asks for deeper detail.
    Connector
  • Returns real-time balance payload per account id (GET /accounts/:id/balance). Pass `account_ids` as an array (1–50). CREDIT accounts may return Pluggy BALANCE_FETCH_ERROR — those rows include a structured `warning` instead of throwing. Response shape: `{ results: [...], errors: [{ id, status, message }] }`.
    Connector
  • Returns real-time balance payload per account id (GET /accounts/:id/balance). Pass `account_ids` as an array (1–50). CREDIT accounts may return Pluggy BALANCE_FETCH_ERROR — those rows include a structured `warning` instead of throwing. Response shape: `{ results: [...], errors: [{ id, status, message }] }`.
    Connector

Matching MCP Servers

  • A
    license
    -
    quality
    C
    maintenance
    A production-ready MCP server for Method CRM API integration. It enables LLMs to interact with Method CRM data through tools for tables, files, users, events, and API key management.
    Last updated
    2
    MIT

Matching MCP Connectors

  • Returns real-time balance payload per account id (GET /accounts/:id/balance). Pass `account_ids` as an array (1–50). CREDIT accounts may return Pluggy BALANCE_FETCH_ERROR — those rows include a structured `warning` instead of throwing. Response shape: `{ results: [...], errors: [{ id, status, message }] }`.
    Connector
  • Returns real-time balance payload per account id (GET /accounts/:id/balance). Pass `account_ids` as an array (1–50). CREDIT accounts may return Pluggy BALANCE_FETCH_ERROR — those rows include a structured `warning` instead of throwing. Response shape: `{ results: [...], errors: [{ id, status, message }] }`.
    Connector
  • Full detail for a single Ukraine ProZorro tender by id (via the keyless OpenProcurement public API). Returns tenderID, title, description, status, procurement method, value (amount+currency), the buyer/procuring entity (name, EDR identifier, region, contact), tender period (start/end), enquiry period, number of bids, and line items (description, CPV classification, quantity, unit). Text is largely Ukrainian. Accepts the 32-char tender id from prozorro_recent_tenders / prozorro_search_tenders.
    Connector
  • List all Kash / free-cash-register.net accounts linked to an email address. Use this before account_create to check if the user already has an account. Returns an array of accounts, each with accountTitle, accountID, and a getOTPForAccount URL that can be used to request a one-time password (OTP) to retrieve the APIKEY. This endpoint is public and requires no authentication.
    Connector
  • Score and rank the user's OWN accounts by StackSignal-style fit: a 0-100 composite blending ICP Match (firmographic fit to a supplied ICP), Intent (engagement/pipeline signals on the account), and an optional Stack Fit layer. Pass `config.icp` (segments / industries / minArr) to drive ICP Match — without it, scoring falls back to Intent only and says so. Stack Fit stays dormant unless `config.icp.idealStack` is supplied. Accepts loosely-typed account records (aliases for segment, industry, arr, lastActivityDays, openPipeline, techStack are normalized). Returns the book ranked highest-fit-first with each layer's sub-score. This scores the accounts the user already owns (the StackSignal product) — it does NOT return net-new accounts to buy. Use when the user asks 'which of my accounts best fit our ICP', 'rank my book by fit', or pastes accounts plus an ICP definition.
    Connector
  • Lists all Mail.app accounts by name. Call this first to discover account names, then use list_emails(account=name) to fetch messages from a specific account. Much faster than querying all accounts at once.
    Connector
  • Reads messages from a specific WhatsApp chat. The chat_id must come from a previous whatsapp_list_chats call. ⚠️ Uses Wacli (unofficial WhatsApp client). Accounts may be restricted for ToS violations.
    Connector
  • Returns real-time balance payload per account id (GET /accounts/:id/balance). Pass `account_ids` as an array (1–50). CREDIT accounts may return Pluggy BALANCE_FETCH_ERROR — those rows include a structured `warning` instead of throwing. Response shape: `{ results: [...], errors: [{ id, status, message }] }`.
    Connector
  • Returns real-time balance payload per account id (GET /accounts/:id/balance). Pass `account_ids` as an array (1–50). CREDIT accounts may return Pluggy BALANCE_FETCH_ERROR — those rows include a structured `warning` instead of throwing. Response shape: `{ results: [...], errors: [{ id, status, message }] }`.
    Connector
  • Returns real-time balance payload per account id (GET /accounts/:id/balance). Pass `account_ids` as an array (1–50). CREDIT accounts may return Pluggy BALANCE_FETCH_ERROR — those rows include a structured `warning` instead of throwing. Response shape: `{ results: [...], errors: [{ id, status, message }] }`.
    Connector
  • Returns real-time balance payload per account id (GET /accounts/:id/balance). Pass `account_ids` as an array (1–50). CREDIT accounts may return Pluggy BALANCE_FETCH_ERROR — those rows include a structured `warning` instead of throwing. Response shape: `{ results: [...], errors: [{ id, status, message }] }`.
    Connector
  • Returns real-time balance payload per account id (GET /accounts/:id/balance). Pass `account_ids` as an array (1–50). CREDIT accounts may return Pluggy BALANCE_FETCH_ERROR — those rows include a structured `warning` instead of throwing. Response shape: `{ results: [...], errors: [{ id, status, message }] }`.
    Connector
  • Returns real-time balance payload per account id (GET /accounts/:id/balance). Pass `account_ids` as an array (1–50). CREDIT accounts may return Pluggy BALANCE_FETCH_ERROR — those rows include a structured `warning` instead of throwing. Response shape: `{ results: [...], errors: [{ id, status, message }] }`.
    Connector
  • Returns real-time balance payload per account id (GET /accounts/:id/balance). Pass `account_ids` as an array (1–50). CREDIT accounts may return Pluggy BALANCE_FETCH_ERROR — those rows include a structured `warning` instead of throwing. Response shape: `{ results: [...], errors: [{ id, status, message }] }`.
    Connector