"Importing FastMCP from the mcp.server Python Module" matching MCP tools:

• reachable_techniquesA

  eurorackA

  Given a rack (the module ids the user owns), return which canonical patch techniques the rack can realize, and which it is one module away from. The set-level companion to find_role_realizations: where that answers "which module fills role R in technique T?", this answers the rack owner's actual question — "given everything I own, what can I actually do, and what am I close to?". This is the right tool the moment a user gives you their modules and asks an open "what can I do / what can this rack do / what am I missing?" question — instead of guessing techniques from training priors or calling find_role_realizations technique-by-technique by hand. It runs the affordance match across the whole technique catalog for you. Returns two buckets: - reachable: every required role has a rack module that fills it. Each carries an `assignment` (role → module). `requires_shared_module: true` flags a technique only reachable by reusing one module for two roles — verify those roles can share one instance. - near_misses: all-but-one role fillable; `missing_roles` names the unfilled role(s) and the `required_affordances` you'd need. This is the acquisition signal — "you can already do X; you're one <affordance> module away from Y". Args: - rack (string[], required): module ids, e.g. ["make-noise/maths", "mutable-instruments/plaits"]. Max 64. Ids that match no module are returned in `unresolved` (with did-you-mean), not silently dropped. - limit (number): max techniques per bucket. Default 25, max 100. Stateless-rack contract: the server keeps no memory of your rack between calls — pass the COMPLETE current rack every call. A partial rack silently narrows what's reported reachable, so if a module id doesn't resolve, surface the `unresolved` did-you-mean to the user rather than proceeding on the incomplete set. Scope: reachability is role-PRESENCE based. It does NOT verify per-role instance counts (cardinality) — a technique needing two independent envelopes is judged reachable if you have one envelope source. The distinct-instance question (can one module fill two roles?) is surfaced as `requires_shared_module`, not silently assumed. For the editorial detail on a specific technique (canonical instance, counter-canonical notes, full realization list), call list_techniques; for one role's candidates, find_role_realizations. To go the other way — which of your modules are redundant / safe to sell — call rack_redundancy.

  ConnectorNo auth

• get_strategy_codeA

  quantifymeA

  Get the actual Python code behind a community leaderboard strategy. Use after `browse_community`: pass an entry's `id` here to read its real `feature_engineering()` + `strategy_config()` source so the user can inspect or tweak it. To deploy it unchanged, pass the same id to `one_shot` as `community_id`. Read-only, no signup needed. Args: community_id: The `id` of a community entry (from `browse_community`). Returns: dict with: id, title, username, description, symbol, timeframe, metrics {total_ret, win_rate, profit_factor, n_trades, mdd, sharpe_strat}, and `code` (the full Python source). SHOW the code to the user, and offer to deploy it via one_shot(community_id=...) or tweak it first.

  ConnectorNo auth

• validate_pythonA

  CodeCraftA

  Validates a Python automation script that runs OUTSIDE the game, on three axes: Python syntax (using the real interpreter), Minecraft commands embedded in the script (against the official command index), and the shape of the /connect WebSocket message envelope. For behavior pack scripts use validate_script instead — Python does not run inside a pack. The embedded command check is the most valuable one: a command written from memory can look syntactically fine and still do nothing in the game. Only strings starting with / are treated as commands. If syntax could not be checked, syntaxChecked is false in the result; ok:true alone does not mean the syntax is valid.

  ConnectorNo auth

• create_codesA

  Sweeppea MCPA

  Add 1 to 1,000 codes you ALREADY have — from a POS, a CRM or a printed batch — to a sweepstakes, with attributes shared by all of them. To have Sweeppea invent the codes for you, use generate_codes instead. Codes are up to 20 letters, digits, - or _; whitespace is stripped; they are matched exactly and case-sensitively. The response reports Duplicates and Invalid separately from Created — always tell the user those counts rather than claiming every code landed. Requires the Codes & Coupons module enabled on the account — on 403 "module not enabled", do NOT retry; tell the user to contact Sweeppea support.

  ConnectorNo auth

• toggle_moduleA

  BorealHostB

  Enable or disable an AI module on a site. The module must be in the plan's available module list. Requires: API key with write scope. Args: slug: Site identifier module_name: Module to toggle. Available modules: "chatbot" (AI chat widget), "seo" (SEO optimization), "translation" (content translation), "content" (AI content generation) Returns: {"module": "chatbot", "enabled": true, "message": "Module enabled"} Errors: NOT_FOUND: Unknown slug or module not in plan VALIDATION_ERROR: Invalid module name

  ConnectorNo auth

• find_compatible_withA

  eurorackA

  Return modules that have a typed compatibility relationship with the given module. Both edge directions are returned and tagged via the per-match `direction` field — so a single call answers both "what is X a R for?" and "what is a R for X?". `relationship` is OPTIONAL. Omit it to get EVERY edge touching the module across all relationship kinds — the bare "what pairs with / relates to X?" question — with each match self-describing via its own `relationship`. Pass a relationship to restrict to that one kind. Prefer the relationship-less call when you don't already know which kind exists; reach for the typed form only when the question names a specific role ("what clocks X?"). Use this for two question shapes: 1. Patch-time compatibility — "what could I use as a clock source for X?" (returns matches with direction='inbound'), or "what does X clock?" (direction='outbound'). 2. Catalog comparison — "what's an alternative to X?" (symmetric), "what does X replace?" (outbound) / "what replaces X?" (inbound), "is there an expander for X?" (inbound). The vocabulary describes the edge as stored (from = role-bearer, to = target): Patch-time: - clock-source-for — A clocks B - cv-source-for — A produces CV that B consumes - modulator-for — A is a modulator suitable for B (LFO, S&H, random) - audio-source-for — A is an audio source for B (typically a VCO into a VCF) - quantizer-for — A quantizes for B - trigger-source-for — A produces triggers that B consumes - envelope-target-for — A is something B's envelope output is designed to drive Catalog: - replaces — A is the newer successor to B (Morphagene replaces Phonogene) - alternative-to — symmetric: A and B occupy similar design space with different character - expander-for — A is an expander module for the host module B Direction tag on each match: - outbound: queried module is the FROM side (role-bearer). Match is what the queried module does as R. - inbound: queried module is the TO side. Match is the R-for the queried module. - symmetric: only for alternative-to. Args: - module_id (string, required): "<manufacturer-slug>/<module-slug>" - relationship (string, optional): one of the values above. Omit for all edges. - limit (number): default 50, max 200 Returns: { "module": { id, name }, "relationship": <relationship> | null, // null when none was passed (all-edges query) "matches": [{ id, name, manufacturer, notes, source_id, direction, relationship }] } If the module is unknown, returns an error. If no relationships have been recorded in either direction, returns matches=[]. The `notes` field describes the edge in the canonical A→B direction; combined with `direction` the caller can read it correctly either way.

  ConnectorNo auth

• get_academy_moduleA

  Analytics Legends — SAP Analytics IntelligenceA

  Read one Academy training module in full — body, learning objectives and summary, EN, FR and DE — the written course corpus the €29.90 Consultant Pass sells. On THIS endpoint the machine-access subscription is the MCP Pass (€39.90/month, analyticslegends.ai/pricing/), which opens the ENTIRE paid tranche from one key; the €29.90 Consultant Pass is its web-subscriber equivalent and opens the same tier floor here. Requires a subscriber API key (Authorization: Bearer alk_…), Consultant tier or above; without one this tool refuses and `find_academy_modules` keeps serving the catalogue. Takes the module id (`M001`) or its slug (`datasphere-foundations`), both matched case-insensitively — `find_academy_modules` returns both on every row, and `query_knowledge_graph` returns the same ids as `module:M001` node ids, so a graph walk now ENDS somewhere. Unlike `get_study`, the whole module is served in one call: the longest body measured is 17 865 characters, two orders of magnitude under the response ceiling, so sectioning it would cost the caller context without protecting anything.

  ConnectorNo auth

• get_quickstartA

  Vector Panda DocumentationA

  The Vector Panda quickstart: install the veep Python SDK, upload a file, and run similarity queries end to end.

  ConnectorNo auth

• remove_suppressionA

  Sweeppea MCPA

  Remove ONE address from the do-not-contact list, re-enabling messages to it. Only entries added by hand (reason manual) can be removed — a recipient own opt-out, a STOP reply or a complaint is NEVER removable, and trying is both futile and a compliance problem. confirm=true is REQUIRED; set it only after the user confirmed they have a lawful basis to contact that address again. Send address or address_hash; address_hash wins when both are sent. Check the reason with fetch_suppressions first. Requires the Send Message module enabled on the account — on 403 "module not enabled", do NOT retry; tell the user to contact Sweeppea support. When a send is refused, call fetch_messaging_usage first: it is what distinguishes module access, plan channels, an exhausted allowance, a sending pause and a missing 10DLC number.

  Connector

  Destructive

  No auth

• visualize_moduleA

  eurorackA

  Module visualization tool. Use when the user wants to understand how a module's modes work, how parameters change between modes, or what a specific mode does — a visualization communicates the per-mode behavior better than prose. The host renders the result inline in the chat as an interactive visualization (mode buttons, per-mode descriptions, schematic curves); you do not need to build an artifact yourself — just call this tool. Do not use for general module specs (HP, jacks, capabilities) — call get_module instead. After calling, your prose can reference what the user is seeing in the visualization (e.g. "in formant mode, all three outputs become bandpass filters") rather than describing the visualization itself. Currently supported viz families: - filter_response — filters with characterized response curves (e.g. Three Sisters, Ripples, Belgrad, A-124, Filter 8, QPAS, SVF 1U, Cinnamon, C4RBN, Ikarie) - oscillator_morph — multi-mode oscillators and excited resonators (e.g. Rings, Loquelic Iteritas, Plaits) A module is supported when every one of its modes has a behavior_model_id the renderer knows. If you're unsure whether a given module qualifies, just call this tool — the error names the gap. Errors: - "Module not found: <id>" if no module with that id exists. - "Module not yet supported by visualize_module: <id>" when one or more modes lack a renderer-known behavior_model_id, or when the module mixes incompatible viz families. Suggest get_module for the underlying spec. The returned spec is a JSON object with: module_id, module_name, manufacturer, viz_type, params[], modes[], response_model_id, presets[]. Each mode has a behavior_model_id that the renderer uses to pick the curve set (e.g. crossover_lp_bp_hp vs formant_three_bp for filter_response). `response_model_id` (top-level) vs per-mode `behavior_model_id`: for multi-mode modules the top-level field is intentionally null — each mode carries its own behavior_model_id since the modes use different curve sets (e.g. Three Sisters' crossover vs formant). Read the per-mode values from `modes[].behavior_model_id`. The top-level is populated only for single-curve modules where one model applies across the whole module. `null` at top-level + populated per-mode = "modes carry distinct models," not a bug.

  ConnectorNo auth

• import_leads_from_fileA

  PersuadioAIA

  Upsert leads from an uploaded CSV or XLSX file into this account. WRITES TO THE DATABASE — SENDS NOTHING on any channel, ever; this only stores contacts. Deduplicates by phone/email (dedupe_by, default both) against both the file itself and every lead already in this account. Re-importing a lead that is opted-out, suppressed, or do-not-contact NEVER clears those flags and NEVER moves the lead — only genuinely new contacts are created. Returns an import_id: pass it to clone_campaign_draft's import_ids to attach this audience to a campaign. idempotency_key is required — retrying the same key returns the same result rather than importing twice; reusing it with different arguments is rejected as idempotency_conflict.

  ConnectorOAuth

• delete_codesA

  Sweeppea MCPA

  Permanently delete 1 to 1,000 codes. IRREVERSIBLE. Only codes nobody holds are deleted — assigned, redeemed and voided codes are never removed and come back in Skipped, so always report Deleted and SkippedCount to the user rather than assuming the whole batch went. confirm=true is REQUIRED on every call; set it only after the user confirmed THIS deletion. To take a code back from a participant instead, use unassign_code. Requires the Codes & Coupons module enabled on the account — on 403 "module not enabled", do NOT retry; tell the user to contact Sweeppea support.

  Connector

  Destructive

  No auth

• generate_codesA

  Sweeppea MCPA

  Generate 1 to 5,000 unique random codes with a chosen length, character set, case, prefix and suffix. Use this when Sweeppea should invent the codes; use create_codes when the user already has them. prefix + length + suffix must not exceed 20 characters in total. NOTE: here the character set is the STRING type ("alphanumeric" or "numeric"); the same concept in update_code_settings is the INTEGER coupon_code_type (1 numeric, 2 alphanumeric). They are two encodings of one idea — do not copy a value from one tool to the other. Requires the Codes & Coupons module enabled on the account — on 403 "module not enabled", do NOT retry; tell the user to contact Sweeppea support.

  ConnectorNo auth

• get_codeA

  Sweeppea MCPA

  Fetch one code, either by its coupon_token, or by the code itself plus the sweepstakes_token — the second form is what a point-of-sale system has in hand. Send one form or the other: coupon_token wins if both are sent. Codes are matched exactly and case-sensitively. Read-only; it never redeems anything — use redeem_code for that. Read-only and NOT gated by the Codes & Coupons module: only the writes of this category document a module-not-enabled 403. If this call returns 403, look for another cause before telling the user the module is off.

  ConnectorNo auth

• unassign_codeA

  Sweeppea MCPA

  Take a code back from its participant and make it available again. DESTRUCTIVE: any redemption recorded on that code is cleared along with the assignment, so a redeemed code loses its redemption history. Voided codes are never released. confirm=true is REQUIRED. If the goal is only to reverse a redemption while keeping the participant, use unredeem_code instead — always offer that alternative first. Requires the Codes & Coupons module enabled on the account — on 403 "module not enabled", do NOT retry; tell the user to contact Sweeppea support.

  Connector

  Destructive

  No auth

• get_campaignA

  Sweeppea MCPA

  Fetch one campaign in full: content, audience, sender profile, counters and the actions this API may take on it. Read that action list before offering the user a pause, resume or cancel — it tells you what the campaign current status actually allows. Read-only and NOT gated by the Send Message module: only the writes of this category document a module-not-enabled 403. If this call returns 403, look for another cause before telling the user the module is off.

  ConnectorNo auth

• importParsedPayrollA

  PuzzleB

  Import the parsed payroll run(s) from a payroll document onto the specified account, recording real payroll objects via bulkUpsertPayrolls. Resolves each parsed worker name to an existing employee/contractor; it does NOT create workers. If any worker on a run cannot be matched, NOTHING is imported and the unmatched names are returned — create those workers first, then retry. Idempotent: re-importing the same run (same nativeId) updates rather than duplicates. Confirm the preview from getParsedPayroll with the user before calling. Returns each imported run's id and in-app url — link the url(s) in your reply.

  Connector

  Destructive

  OAuth

• searchA

  Deno LandA

  NOT AVAILABLE: deno.land/x has no public search API — the apiland.deno.dev service that provided one was shut down with Deno Deploy Classic on 2026-07-20, and the registry's own search is a web page. This tool returns an empty list with `empty_reason: "upstream_removed"` rather than guessing. If you know the module name, call module or versions instead.

  ConnectorNo auth

• generate_testsA

  SpecProofA

  Generate a cited, runnable conformance test that verifies one normative requirement. The test is grounded in the requirement sentence plus its surrounding clause from the corpus, and every test cites the spec, section and page it enforces. If the requirement is not testable (boilerplate, scope text), the generator abstains rather than inventing a test. Args: requirement_id: The requirement's id, as shown by get_requirements target: "pytest" for a runnable Python test module, or "gherkin" for a reviewable .feature file (default: pytest)

  ConnectorNo auth

• mapA

  SymvantaA

  Token-efficient repo (or subtree) skeleton: directory tree with each file's classes (methods in parens), functions, and HTTP endpoints, from the graph. Orient before drilling in. Scope with "path", cap with "maxDepth", density:"full" adds properties. view:"architecture" instead returns a module map (Louvain clusters with hubs, paths and cross-module coupling), plus namedModules/totalModules: a module NAME comes from a generated summary and is provisional, its id (the member-set hash in the header) is the stable key, so pin modules by id and re-read names rather than caching them.

  ConnectorNo auth

• test_python_package_runtimeA

  Python Package Runtime TestA

  Test a specific Python package/version on a supported Python/Linux target runtime using empirical execution. Returns scoped install evidence, usable-import evidence when requested, and a scoped result/receipt. Supported boundary: public PyPI on Linux x86_64 / CPython 3.13. This is not generic package advice, security verification, arbitrary Python execution, broad compatibility testing, feature behavior testing, or application integration testing.

  ConnectorNo auth