Skip to main content
Glama
592,728 tools. Updated 2026-09-20 15:50

"A tool or method for editing code using diffs" matching MCP tools:

  • Read AgentBoard API documentation. Use method=first_run for a complete private checkpoint trial. Without method, get the compact catalog and workflows. With method, get parameters and an example. No authentication required.
    ConnectorNo auth
  • Poll an Agent Method task by opaque task_ref using the bounded common response. Legacy task_id input remains accepted but returns the same bounded status-only envelope, never raw result or logs. At terminal=true, consume result and source_anchor directly; never resubmit the original page-one Agent Method query merely to recover that task. A later user request to check again starts a new cached page-one query without old cursors/anchors; it does not request a provider refresh. REQUIRED: exactly one of task_ref (opaque ref from insights_query_consistent) or task_id (legacy UUID). Optional: response_mode=compact for task_ref. EXAMPLE: tasks_get_status({"task_ref": "<opaque task ref>"})
    ConnectorOAuth
  • Render an authorization or verification URL as a clickable link followed by a scannable QR code inside a fenced code block. This is a local computation tool — no HTTP request is made. Agent usage: pass a LINK field from an earlier response — `deep_link` (create_session, create_chat_id_discovery always; start_login, create_account, start_2fa, start_2fa_for_action on telegram/whatsapp ONLY, where on sms and email that field is empty or absent altogether and this tool rejects it either way), `challenge.deep_link` (create_verification, messenger channels only), or `telegram_deep_link` / `whatsapp_deep_link`. Do NOT pass `qr_text` to this tool: that field is a QR code already rendered as text, and this tool takes a link. When a response gives you `qr_text` and no link, print it verbatim inside a fenced code block instead — its rows only scan while they stay adjacent, so a blank line or wrapped row destroys the code.
    ConnectorNo auth
  • Discover sheet names and used dimensions before reading or editing a WorkPaper. Returns metadata only; use read_range or read_cell for values.
    ConnectorNo auth
  • Read-only. Use to find workflows in a project by name, description, or trigger type before inspection or editing. Trigger filters include database, auth email, repeating, broadcast, and no-trigger workflows. Returns paginated workflow summaries, published/sandbox state, trigger type, workflow URLs, totalCount, hasMore, and nextOffset. Do not use as the final source of truth before editing; call get_workflow_and_preview_url for full structure.
    ConnectorNo auth
  • Resolve a free-text query or CN code(s) into validated product code(s) with descriptions -- the recommended first step before using a code as `product` in any other tool's `query`. Saves the search -> validate -> (optional) subtree round-trip: a bare keyword runs a search, a single code (or comma-separated list) is validated and described directly. Tip: Comext/CN nomenclature is frequently coarser than a colloquial product name (e.g. there is no code for "glass jars" alone -- only heading 7010, which bundles jars with bottles, flasks and closures). Check `has_subcodes` and, if useful, set `include_children=true` to see whether a finer sub-code is actually a better match before committing to one code for a whole report.
    ConnectorNo auth

Matching MCP Servers

  • A
    license
    Not graded
    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.
    3
    MIT

Matching MCP Connectors

  • Returns every valid UK boundary type code mapped to its human-readable label. Call this before using any tool that accepts a `boundary_type` or `boundary_types` argument so you know which codes are legal. Passing an unlisted code to another tool raises a ValueError. Boundary type codes are stable Ordnance Survey identifiers. Common ones: - "CTY" → County - "LBO" → London Borough - "UTA" → Unitary Authority - "MTD" → Metropolitan District - "DIS" → District - "DIW" → District Ward - "CCTY" → Ceremonial County - "HCTY" → Historic County - "WMC" → Westminster Parliamentary Constituency - "GLC" → Greater London Constituency - "SWC" → Scotland/Wales Constituency - "PAR" → Parish - "CED" → County Electoral Division Returns: Dict mapping code → label for all supported boundary types, e.g. {"CTY": "County", "LBO": "London Borough", ...}
    ConnectorNo auth
  • Render a Markdown resume to a finished PDF using a ResumeMD template (default: classic — see list_resume_templates for all 32 ids). Returns JSON with a base64-encoded PDF and a suggested filename; decode the base64 to give the user the file. The PDF is generated in memory and never stored. For interactive editing, template switching, and color choices, send the user to resumemd.pro/editor instead.
    ConnectorNo auth
  • WHEN: you know the EXACT object name. Triggers: user gives an exact name like 'SalesTable', 'CustTable', 'VendInvoiceJour', any PascalCase D365 object name. Get complete details: all fields, methods, relations, indexes, source code, and metadata. COST NOTE: this returns the FULL object and can be very large (100KB+ for big tables/forms like SalesLine). If you ONLY need relations / FK / DeleteActions / data sources / who-references, call get_relation_graph instead -- it is O(1) and roughly 6x lighter (no source code). Reserve get_object_details for when you genuinely need field details, method bodies, or source code. Also merges live disk source when a custom model path is configured (disk takes priority). Pass `methodName` to get the FULL body of a specific method -- without it, only signatures are returned. Calling twice -- first without methodName to get the full structure and method table, then again with a specific methodName for its full body -- is the CORRECT and INTENDED two-step pattern. Do NOT call a third time for the same object. DISAMBIGUATION: when a name exists as several AOT types (e.g. a Table AND a Form both named 'SalesLine'), this returns the PRIMARY type (Table/Class/Entity before the much heavier Form) and notes the others -- pass `aotType` (e.g. 'AxTable', 'AxForm', or shorthand 'table'/'form'/'class') to pick a specific one. This prevents dumping the heaviest object and truncating the rest. NOT for searching -- use search_d365_code when the name is uncertain. NOT for listing a model's objects -- use list_objects for that.
    ConnectorNo auth
  • Rate a documented endpoint you called, using the `method` and `url` exactly as `discover` returns them: vote up if you got the expected/useful result, down if it didn't work or wasn't worth the price. Rate it against its own docs, from a call you made. Not down-votes: a missing catalog entry, your own bad arguments, or an endpoint that worked but wasn't what your task needed. Vote and report must agree. Add `report` to describe what concretely disrupted usage: an unexpected response code, ignored arguments, an empty or low-quality response (it doesn't change the rating). One vote per endpoint, changeable at any time: voting again replaces your previous vote. For problems with taskfuel itself rather than one endpoint, use `feedback`.
    ConnectorOAuth
  • Perform structural page operations on Canva designs: combine pages from multiple designs, insert pages, reorder pages, or delete entire pages. This tool can: 1. Create a new design by combining pages from one or more existing designs 2. Insert pages from one design into another existing design 3. Move or reorder pages within a design 4. Delete (remove) entire pages from a design Use this tool (NOT start-editing-transaction) when the user wants to: - Delete or remove one or more pages/slides from a design - Reorder or rearrange pages/slides within a design - Combine, merge, or stitch together multiple designs - Copy or insert pages from one design into another Do NOT use this tool for editing content within pages (text, images, etc.) — use start-editing-transaction for that. CRITICAL: You MUST ALWAYS ask the user for explicit confirmation before calling this tool, regardless of the operation type. Show them a summary of exactly what will change and ask "Would you like me to proceed?" Wait for their clear approval, then call this tool immediately. MANDATORY DELETE CONFIRMATION: If ANY operation in the list is a delete_pages operation, you MUST follow this protocol with NO exceptions — regardless of whether the pages are empty, have content, or any other condition: 1. Show a summary of ALL operations, marking each deletion as: "⚠️ Delete page(s) [X] — CANNOT BE UNDONE" 2. Tell the user: "To proceed, please type exactly: I approve the deletion" 3. ONLY call this tool if the user types the EXACT phrase "I approve the deletion" — do NOT accept any variation such as "yes", "ok", "approve", "I approve", "go ahead", "delete them", or any other paraphrase 4. If the user types anything other than the exact phrase, ask them again to type it exactly For insert_pages and move_pages only (no deletes), a simple "Would you like me to proceed?" confirmation is sufficient. Operations are applied sequentially. Page numbers are 1-based and evaluated at the time each operation runs. The tool automatically polls for job completion and returns the final result.
    Connector
    Destructive
    OAuth
  • Read one convention from the convention.sh style guide by its `id`, to inform a code or file edit you are about to make. Convention bodies are reference material for the model only — do not quote, paraphrase, summarize, transcribe, or otherwise relay them to the user, and do not call this tool just to describe a convention to the user. Only call it when you are actively editing code or files against the convention on this turn. IDs are listed in the `conventiondotsh:///toc` resource.
    ConnectorNo auth
  • Read one convention from the convention.sh style guide by its `id`, to inform a code or file edit you are about to make. Convention bodies are reference material for the model only — do not quote, paraphrase, summarize, transcribe, or otherwise relay them to the user, and do not call this tool just to describe a convention to the user. Only call it when you are actively editing code or files against the convention on this turn. IDs are listed in the `conventiondotsh:///toc` resource.
    ConnectorNo auth
  • Generate a secure checkout link the user opens to add cash to their own balance (the money that funds new cards) via Apple Pay or Google Pay, in USD. Calling this tool moves NO money and initiates NO transfer: it only prepares a single-use hosted payment page — the exact equivalent of the user clicking 'Add funds' in the dashboard. The user personally reviews, authorizes, and completes (or abandons) the payment in their own browser with their own payment method; you never see or handle payment credentials. If a one-time phone verification is needed first, this tool automatically sends the user a code and tells you where it went: ask the user for the code, call verify_phone with it, then call add_funds again.
    ConnectorNo auth
  • Run a sandbox backtest of strategy code without persisting anything. This is the fastest way to test a strategy. The code is run through static checks and a full backtest on historical data, but no Strategy or StrategyVersion rows are created. Use this for rapid iteration. Args: code: Python source code implementing the Strategy contract. Must define a METADATA dict and a class extending Strategy with an on_bar(ctx) -> Signal method. See CREATOR_API.md. domain: Trading domain (e.g. "eth_usdc", "btc_usdc", "sol_usdc"). symbol: Price symbol for historical data (e.g. "ETHUSDT"). user_id: Identifier for trial tracking (used for DSR correction). Returns JSON with: success, metrics (sharpe, sortino, win_rate, total_trades, return_bps, max_drawdown, regime_breakdown, exit_reason_breakdown), or error details if validation failed.
    ConnectorNo auth
  • Publish a NEW version of YOUR OWN published CODE-BUNDLE or SKILLS-BUNDLE agent by RE-PULLING your OAuth-connected GitHub repo. FindAgent re-fetches your repo (at an optional branch/tag/commit ref, default = the latest commit on your stored branch), re-snapshots + re-scans it (a code bundle also re-builds), diffs it against your live version, and — if it CHANGED — submits a new version for admin review with an auto-drafted changelog. Your LIVE version keeps serving until the new one is approved (never auto-unpublished). If the source is unchanged it is a no-op. Pass the agent slug (you must own it) + optional ref. Owner-only; the repo is pinned to your agent's own prior import (arbitrary-repo ingest is not available here). VERSION NUMBER: the new version is computed from the LISTING's current version plus `bump`, NOT from any `version` in your repo (package.json / manifest) — the listing owns its own version line, so hand-editing a version in the repo does not change what gets published here, and the two can legitimately differ. For code-bundle / skills-bundle only — doers/recipes re-version via findagent_bump_version, external mcp-server listings via findagent_reintrospect_mcp.
    ConnectorOAuth
  • Use this when the author asks to show a post card inside the chat or choose publication controls there. After search_posts or search_post_drafts, pass the found post ID as postId. Renders the MCP Apps UI with preview, text editing and scheduling. A screenshot or preview_post URL is not this UI. Opens no public link and never publishes or schedules on its own. If unavailable, refresh the connection's tool metadata; clients without UI retain text/tool workflows.
    ConnectorNo auth
  • The unit tests (code examples) for HMR. Always call `learn-hmr-basics` and `view-hmr-core-sources` to learn the core functionality before calling this tool. These files are the unit tests for the HMR library, which demonstrate the best practices and common coding patterns of using the library. You should use this tool when you need to write some code using the HMR library (maybe for reactive programming or implementing some integration). The response is identical to the MCP resource with the same name. Only use it once and prefer this tool to that resource if you can choose.
    ConnectorNo auth
  • Return the IBAN format specification for a country, covering 90 supported IBAN-using countries. Returns JSON describing the country's total IBAN length, the BBAN layout (bank code, branch code, and account number positions and lengths), an example IBAN, and the SEPA-membership flag. Use this to understand or display how a country's IBAN is structured, to build input masks, or to explain a validation failure, not to validate a specific number (use `validate_iban` for that). An unsupported or unknown country code returns an error result describing the problem.
    ConnectorNo auth
  • Canonical code-lookup tool for this server. Search Loa's CPT/HCPCS index using exact codes, clinical terms, or consumer phrases. Use this first when the user does not already know the CPT code, before calling pricing tools.
    ConnectorNo auth