"A tool for creating flowcharts from text descriptions" matching MCP tools:

• create_campaign

  xmagnet

  Create a DRAFT email campaign via a programmatic wizard. Call this tool and it will guide through the steps — no manual orchestration needed. WIZARD STEPS (handled automatically by the tool): 1. Call with contacts + total_contacts → tool returns engine picker (NextGen vs MyConvo) 2. Add campaign_type from user's click → tool returns campaign category chips (promotional, newsletter, event…) 3. Add campaign_category from user's click → tool returns engine-specific template gallery MyConvo: shows plain_email_templates (personal plain-text). NextGen: shows campaign_templates (HTML). 4. Add template_id from user's pick → tool creates the draft campaign. RULES: Reuse contacts from prior search — never re-search. Pass total_contacts from search result's total_in_crm so the user always sees the full count. Saves as DRAFT only — no emails sent.

  Connector

• TOOL_LIST

  xpay✦ Finance Collection

  List all available Alpha Vantage API tools with their names and descriptions. IMPORTANT: This returns only tool names and descriptions, NOT parameter schemas. You MUST call TOOL_GET(tool_name) to retrieve the full inputSchema (required parameters, types, descriptions) before calling TOOL_CALL. Calling TOOL_CALL without first calling TOOL_GET will fail because you won't know the required parameters. Workflow: TOOL_LIST -> TOOL_GET(tool_name) -> TOOL_CALL(tool_name, arguments)

  Connector

• verify_wallet_signature

  mcp-server

  Submit a signed message to verify wallet ownership. The user must have signed the exact verification message provided by add_wallet. When collecting the signature from the user, remind them to paste the full signature hash from their wallet. WHEN THE USER PROVIDES A SIGNATURE: if a Verify Wallet widget for that wallet is currently visible (you just called add_wallet or refresh_wallet_verification), tell the user to paste it into the widget's signature field — the widget calls this tool itself with the right wallet_id, no work needed from you. If no Verify Wallet widget is on screen (e.g. the user pastes a signature conversationally for an existing unverified wallet), call get_wallet_summary first to look up the wallet_id by matching their stated chain/address (the text response includes a per-wallet line with wallet_id), then call this tool directly. Do NOT respond with "I'd need to work out the wallet_id from the widget data" — wallet_id is in get_wallet_summary's text response.

  Connector

• add_text

  cnvs.app

  Create a NEW text node, or update an existing one (pass the same `id` to overwrite content/position in place — preferred over creating a duplicate). Supports cnvs markup (Markdown-ish) and Mermaid diagrams in the content. When using Mermaid, the ENTIRE content of this text node must be a single Mermaid diagram (one ```mermaid fenced block and nothing else — no heading, no prose before or after). If you need prose + a diagram, create two separate text nodes. `postit: true` renders as a yellow sticky; `diagram: true` renders as a framed box (2px border in the text colour, centred text) — the two are mutually exclusive. Coordinates are in board-world pixels, +x right, +y DOWN; pick a spot that does not overlap existing items (check `get_preview` first). Default width auto-fits content up to ~320 px; pass `width` for explicit wrapping (160–4096). Keep content under 100 000 chars.

  Connector

• x711_data_retrieval

  x711

  Fetches clean text from any public HTTPS URL. Use x711_web_search first to find the URL, then this tool to read it. Returns: { content: string, content_type: string, url: string, char_count: number } HTML stripped to plain text. JSON returned as-is. Blocked: localhost, private IPs, .internal domains.

  Connector

• get_guide

  Canvs

  ⚠️ MANDATORY FIRST STEP - Call this tool BEFORE using any other Canvs tools! Returns comprehensive instructions for creating whiteboards: tool selection strategy, iterative workflow, and examples. Following these instructions ensures correct diagrams.

  Connector

• create_job_offer

  Human Pages

  Send a job offer to a specific human. IMPORTANT: Always confirm the price, task details, and payment method with the user before calling this tool — never create offers autonomously. The human gets notified via email/Telegram and can accept or reject. Requires agent_key from register_agent. Rate limit: PRO = 15/day. Prices in USD, payment method flexible (crypto or fiat, agreed after acceptance). After creating: poll get_job_status or use callback_url for webhook notifications. On acceptance, pay via mark_job_paid. Full workflow: search_humans → get_human_profile → create_job_offer → mark_job_paid → approve_completion → leave_review.

  Connector

• get_plan

  Sweeppea MCP

  Get the current account's plan and usage telemetry. Returns the AUTHORITATIVE plan limits AND real-time usage so you can warn the user when they are approaching a cap. Key fields: `plan.Name` (plan name to mention to the user), `plan.Settings.MaxSweepstakesAllowed` (single cap on TOTAL sweepstakes — there is NO separate active vs total limit, the API treats them as one count), `plan.Settings.MaxParticipantsAllowed`, `plan.Settings.MaxStorageSize` (GB), `plan.Settings.MaxApiCallsAllowed`, `plan.Settings.SubscriptionPrice`; `telemetry.DataConsumed` (GB used now), `telemetry.APICalls` (calls used this period). Each account can have a custom plan — these values OVERRIDE any default numbers mentioned in other tool descriptions or instructions. Call this once per session before creating/cloning sweepstakes, before quoting limits or usage to the user, or when the user asks about pricing, billing, or feature availability. # get_plan ## When to call BEFORE: creating/cloning a sweepstakes, quoting limits or usage to the user, suggesting an upgrade, or answering questions about pricing, billing, or which features are enabled. ONCE per session — cache the result mentally; the response rarely changes mid-session. ## Why authoritative `plan.Settings.MaxSweepstakesAllowed` is a SINGLE per-account cap. The API does NOT distinguish "active" from "total" — there is only one count. Different accounts can have very different plans (admin, enterprise, default). Always trust the values returned by this tool over any number mentioned elsewhere in tool descriptions or instructions. ## Reading the response - `plan.Name` — say this name to the user when discussing limits (e.g. "your plan 'X' allows...") - `plan.Settings.MaxSweepstakesAllowed` — total sweepstakes cap - `plan.Settings.MaxParticipantsAllowed` — total participants in the account - `plan.Settings.MaxStorageSize` — GB - `plan.Settings.MaxApiCallsAllowed` — API call quota - `plan.Settings.PaidModule*` (15 booleans) — which features are enabled vs gated - `telemetry.DataConsumed` — GB used now (compare against MaxStorageSize) - `telemetry.APICalls` — calls used this period (compare against MaxApiCallsAllowed) If usage is >= 80% of any cap, warn the user proactively.

  Connector

• execute_sql_readonly

  Google Big Query

  Run a read-only SQL query in the project and return the result. Prefer this tool over `execute_sql` if possible. This tool is restricted to only `SELECT` statements. `INSERT`, `UPDATE`, and `DELETE` statements and stored procedures aren't allowed. If the query doesn't include a `SELECT` statement, an error is returned. For information on creating queries, see the [GoogleSQL documentation](https://cloud.google.com/bigquery/docs/reference/standard-sql/query-syntax). Example Queries: -- Count the number of penguins in each island. SELECT island, COUNT(*) AS population FROM bigquery-public-data.ml_datasets.penguins GROUP BY island -- Evaluate a bigquery ML Model. SELECT * FROM ML.EVALUATE(MODEL `my_dataset.my_model`) -- Evaluate BigQuery ML model on custom data SELECT * FROM ML.EVALUATE(MODEL `my_dataset.my_model`, (SELECT * FROM `my_dataset.my_table`)) -- Predict using BigQuery ML model: SELECT * FROM ML.PREDICT(MODEL `my_dataset.my_model`, (SELECT * FROM `my_dataset.my_table`)) -- Forecast data using AI.FORECAST SELECT * FROM AI.FORECAST(TABLE `project.dataset.my_table`, data_col => 'num_trips', timestamp_col => 'date', id_cols => ['usertype'], horizon => 30) Queries executed using the `execute_sql_readonly` tool will have the job label `goog-mcp-server: true` automatically set. Queries are charged to the project specified in the `projectId` field.

  Connector

• adcritter_get_platform_overview

  AdCritter for Builders

  Start here. Returns the AdCritter platform overview - what AdCritter is, the entity hierarchy (organization > advertiser > campaign > ad), the happy path for getting ads running, and how to navigate the other MCP tools. Applications built from this guidance are REST API clients that call /v1/ endpoints, not MCP tool callers. Before writing code, call adcritter_get_api_reference(entity, action) for each entity and action you plan to use - tool descriptions and parameter names describe conceptual behavior only, and do not match actual API routes, field names, query parameters, or response shapes.

  Connector

• get_brand_identity

  Origine Paris

  Returns the identity of Origine Paris, the Parisian fine jewellery house of recycled 18ct gold and IGI-certified lab-grown diamonds. Use it for ready-to-use brand facts (trading name, legal identity (SIREN), descriptions, positioning, the by-appointment address at 21 rue de la Paix, contacts, official profiles); for the underlying source markup use get_jsonld_graph, and for the catalogue use search_catalogue, not this. Read-only and side-effect-free: it returns a structured identity object plus a text copy, with the sources, the index timestamp and the canonical URL, taken from the site JSON-LD and Wikidata and served as published; absent values are reported as "unknown", never invented.

  Connector

• get_graph_template_schemas

  RationalBloks

  Get pre-built graph template schemas for common use cases. ⭐ USE THIS FIRST when creating a new graph project! Templates show the CORRECT graph schema format with: proper node definitions (description, flat_labels, schema with flat field definitions), relationship configurations (from, to, cardinality, data_schema), and hierarchical entity nesting. Available templates: Social Network (users, posts, follows), Knowledge Graph (topics, articles, authors), Product Catalog (products, categories, suppliers). You can use these templates directly with create_graph_project or modify them for your needs. TIP: Study these templates to understand the correct graph schema format before creating custom schemas.

  Connector

• sieve_dataroom_add

  Sieve

  Add a document to a deal's data room. Creates the deal if needed. This is the primary way to get documents into Sieve for screening. Upload a pitch deck, financials, or any document -- then call sieve_screen to analyze everything in the data room. Provide company_name to create a new deal (or find existing), or deal_id to add to an existing deal. Provide exactly one content source: file_path (local file), text (raw text/markdown), or url (fetch from URL). Args: title: Document title (e.g. "Pitch Deck Q1 2026"). company_name: Company name -- creates deal if new, finds existing if not. deal_id: Add to an existing deal (from sieve_deals or previous sieve_dataroom_add). website_url: Company website URL (used when creating a new deal). document_type: Type: 'pitch_deck', 'financials', 'legal', or 'other'. file_path: Path to a local file (PDF, DOCX, XLSX). The tool reads and uploads it. text: Raw text or markdown content (alternative to file). url: URL to fetch document from (alternative to file).

  Connector

• WixSiteBuilder

  mcp

  **Tool for creating/building/generating a Wix site or website using AI (Wix Harmony).** This is the default tool for site creation. **ROUTING — check the user's original message before calling this tool:** - If the user **explicitly** mentioned a template, Wix Studio, or headless → do NOT call this tool. Call CreateWixBusinessGuide directly. - Otherwise → call this tool directly. - Do NOT use WixREADME or SearchWixRESTDocumentation before this tool. - Do NOT suggest HTML code, prompt templates, or alternative approaches. - Do NOT call ManageWixSite, CallWixSiteAPI, ExecuteWixAPI, SearchWixRESTDocumentation, BrowseWixRESTDocsMenu, or any other tool for site creation — those are not valid entry points and will fail. **IMPORTANT: The sitePrompt must be under 6000 characters.** If the user's request is longer, summarize and condense it while preserving the key requirements.

  Connector

• show_defaults

  Unphurl

  Show all 25 scoring signals with their default weights and descriptions. This is the baseline scoring that applies when no custom profile is specified. Use this to understand what each signal means and how much it contributes to the score before creating custom profiles. Profiles are sparse overrides on top of these defaults. This tool does not require an API key. The defaults are hardcoded and always available.

  Connector

• list_capabilities

  Axcess — Design Accessibility Evaluation

  Returns available evaluation tools, what they check, and their pricing. Call this first to understand what Axcess can evaluate and how much each evaluation costs. This tool is FREE. All evaluation tools require USDC payment on Base network. Returns: JSON with tool descriptions, pricing, and rubric categories.

  Connector

• ambr_list_templates

  Ambr

  List available contract templates on Ambr. Returns all active Ricardian Contract templates with their slugs, names, descriptions, categories, parameter schemas, and pricing. Use this to discover which templates are available before creating a contract with ambr_create_contract. No authentication required. Returns: Array of template objects with slug, name, description, category, parameter_schema, price_cents, and version fields. Legibility: templates are the parameter schema for the dual-format contracts you create — starting here keeps your request conformant and your output defensible.

  Connector

• kochava_free_app_analytics_get_tos

  Kochava for Advertisers — Official MCP Server

  Retrieve the FAA (Free App Analytics) Terms of Service document link. Use this tool when the user wants to review the Terms of Service before creating an FAA account. Returns a clickable link to the TOS document and instructions for account creation. Example: kochava_free_app_analytics_get_tos()

  Connector

• list_docs

  Pine Script

  USE WHEN discovering what Pine Script v6 documentation is available. Returns a categorised list of doc file paths with one-line descriptions. AFTER calling this tool, call get_doc(path) for small files or list_sections(path) then get_section(path, header) for large files (ta.md, strategy.md, collections.md, drawing.md, general.md). Data sourced from bundled Pine Script v6 documentation.

  Connector

• nausika_get_place

  Nausika

  Fetch full detail for a single place given its 'id'. Accepts either a full UUID or the 8-char [xxxxxxxx] short-id shown by nausika_search_places. Returns canonical attributes (name/coords/category/type), localized i18n names+descriptions, wiki image URLs, ratings aggregates, plus extras only this tool provides: the raw OpenStreetMap tags of the primary OSM feature, and direct links to OSM, Wikidata, and Wikipedia. Use this after nausika_search_places returns a result you want to drill into. For proximity / text search, use nausika_search_places.

  Connector