Skip to main content
Glama
466,711 tools. Updated 2026-08-20 06:25

"A monitoring solution for my application" matching MCP tools:

  • Display the user's images inline — one or many. Users speak plainly and will NOT know asset ids; never ask for one, resolve it yourself. For "show me" or "show me my last image" call with NO arguments (shows the most recent image). For "show me my last 4 images / my last 10 pictures" pass count=N (returns a clean grid, up to 12). For a specific known image pass assetId. Renders a branded SwitchApp media card with a Download action per result; do not just print URLs. (Videos are not shown here — use list_my_videos and return the newest finished video's view_url, which plays.)
    Connector
  • Surgically update ANY field in a skill or solution definition, redeploy, and optionally re-test — all in one step. ⚠️ MERGE-BY-DEFAULT (v0.4.0) — Arrays are protected from silent replace. Bare array writes on solution.linked_skills / ui_plugins / platform_connectors / handoffs / grants / triggers (etc.) and skill.tools / connectors / handoffs / scenarios are REFUSED to prevent sibling loss. Add or remove items with the _push / _delete / _update suffixes; opt into a full-array replace only when you really mean it. OPERATIONS (safe by construction): 1. Scalar (dot notation): { "problem.statement": "new value", "role.persona": "You are..." } 2. Deep nested: { "intents.thresholds.accept": 0.9, "policy.escalation.enabled": true } 3. Array APPEND: { "tools_push": [{ name: "new_tool", description: "..." }] } 4. Array REMOVE: { "tools_delete": ["tool_name"] } 5. Array MODIFY-ONE: { "tools_update": [{ name: "existing_tool", description: "updated" }] } 6. Full-array REPLACE (opt-in): { "linked_skills": [...], "linked_skills_replace": true } — or { _replace: true, ... } to opt every array in this call. SOLUTION-LEVEL EXAMPLES (target='solution'): - ADD a skill to the solution: updates: { "linked_skills_push": ["my-new-skill"] } ← NOT { linked_skills: ["my-new-skill"] } (that would REFUSE — it drops your other skills) - REMOVE a skill: updates: { "linked_skills_delete": ["old-skill"] } - ADD a UI plugin: updates: { "ui_plugins_push": [{ id: "mcp:conn:panel", ... }] } - ADD a handoff: updates: { "handoffs_push": [{ id: "h1", ... }] } SKILL-LEVEL EXAMPLES (target='skill' + skill_id): - Change persona: updates: { "role.persona": "You are a friendly assistant" } - Append to persona: updates: { "persona_append": "\n\nALWAYS respond in 2 sentences." } - Add a guardrail: updates: { "policy.guardrails.never_push": ["Never share passwords"] } - Add a tool: updates: { "tools_push": [{ name: "conn.tool", description: "...", inputs: [...], output: {...} }] } - Change intent: updates: { "intents.supported_update": [{ id: "i1", description: "new desc" }] } - CREATE a new skill: target='skill', skill_id='my-new-skill', updates: { "problem.statement": "...", "role.persona": "..." } — auto-scaffolded and added to solution topology. PREVIEW BEFORE WRITING: pass dry_run:true to see the diff (arrays_merged, arrays_replaced, dropped_ids, added_ids) without applying. Use this before any destructive-looking edit.
    Connector
  • Track every document added or changed in one RIS application within an exact date window (changed_from/changed_to), optionally including deletions (include_deleted) — the delta-sync and monitoring primitive for mirrors and watchers, and the only surface that reports removals. Unlike the search tools’ coarse, additive-only changed_since intervals, this is exact-dated and deletion-aware. application takes any RIS application code (e.g. BrKons, Dsk, BgblAuth); the four applications with a different History-feed name are mapped automatically. Each changed document comes back in a compact cross-class record — document_number (for ris_get_document), title, dates, binding_status, and rendition URLs — plus its last-changed date; removed documents come back as deleted records with a deletion timestamp. One application per call; page explicitly for large windows. Application codes and coverage: ris_list_reference topic applications.
    Connector
  • Semantic (vector) search across documents in a collection. Returns ranked text chunks with relevance scores. Free — no credits consumed. Use when you need raw matching chunks from a collection. For a synthesized cited answer from the same context, use collection.ask instead. PREREQUISITE: Collection must be populated via collection.add_document and async indexing must complete (poll job.status) before results appear. Returns: { results: [{ bundle_id, chunk_id, text, score: number (0–1), title? }] } Example prompts: - "Search my Q4 Contracts collection for mentions of liability cap." - "Find the clause about data retention in my due diligence docs." - "Search for revenue numbers across my quarterly reports."
    Connector
  • Create a new application (workspace) owned by the caller. Requires a personal API key (usr_...) — application-scoped keys cannot create applications. Seeds default flows unless skipDefaultFlows is true. Creates persistent state and is NOT idempotent: calling it twice creates two applications. Returns the new application id, which you then pass as applicationId to the other tools.
    Connector
  • Submit a completed Experience Application for human review. Rejects with a missingFields list if any required field is still empty, or a 409 if the Application Fee hasn't been paid/waived yet (call purchaseProduct with productId 9 and applicationId first — Experience uses product 9, NOT product 8). There is no partial/optimistic submission. On success the application moves to human review. Requires NOMADSTAYS_MCP_AGENT_TOKEN.
    Connector

Matching MCP Servers

  • A
    license
    -
    quality
    A
    maintenance
    Governs and automates network monitoring across SolarWinds Orion and Paessler PRTG platforms with a unified MCP server, enabling querying, alert management, and governed writes with audit logging.
    MIT

Matching MCP Connectors

  • Client-website monitoring for agencies: uptime, incidents, SSL/domain expiry, server metrics.

  • Site & competitor monitoring: snapshots, evidence-backed diffs, briefs, price checks, mentions.

  • Find USGS water monitoring sites in a state. Returns a list of monitoring stations with their site numbers, names, and locations. Use site numbers with get_water_levels to retrieve data. Args: state: Two-letter US state abbreviation (e.g. 'CA', 'TX'). site_type: Type of monitoring site. 'ST' for stream/river, 'GW' for groundwater well, 'SP' for spring. limit: Maximum number of sites to return (default 50).
    Connector
  • Securely register the D365 F&O environment's Application Insights / Log Analytics connection for the CURRENT session. The client secret is encrypted in memory (AES-256-GCM), never written to disk and never echoed back. Once set, appinsights_query and appinsights_diagnose_slowness use it automatically until it expires or you call appinsights_clear_connection. HOW TO GET THE VALUES: workspaceId -- the Log Analytics WORKSPACE ID (GUID, not the App Insights app id) behind the Application Insights resource the environment is linked to (D365FO: System administration > Monitoring and Telemetry parameters > Application Insights Registry tab shows the connection string; the workspace id is on that Log Analytics workspace resource's Overview blade in the Azure Portal). tenantId/clientId/clientSecret -- an Entra ID app registration granted the 'Log Analytics Reader' (or 'Monitoring Reader') role on that workspace resource (Azure Portal > workspace > Access control (IAM) > Add role assignment). Read-only -- no write access is ever needed or used. In a locked server deployment (APPINSIGHTS_LOCK_SERVER_CONFIG=true) this tool is disabled and the server's own environment credentials are used instead.
    Connector
  • Rotate the client secret for a confidential OAuth application in a connected Clerk application. **Sensitive** — the response includes a new client_secret. Update authorized OAuth clients immediately and do not log the secret. Call clerk.get_connected_accounts first. Pass clerk_instance_id to target a specific connection, or omit it to use the default account. Returns the updated OAuth application summary with the new client_secret. Cost = 10 tokens.
    Connector
  • Use when: you have a candidate fix for an open issue and want to publish it without closing the issue yet (preferred default). Returns: the published solution linked as a candidate — issue stays open until confirm (resolve_open_issue with solution_id) or usage threshold. Do not use when: you are certain this is the definitive fix and should close immediately (use resolve_open_issue with solution body), or no open issue matches (use submit_solution). Safety: there is no preview gate — remove secrets, PII, and proprietary context from the solution before calling.
    Connector
  • Use when: confirming a candidate (pass solution_id) or force-closing with a definitive fix (pass solution body). Prefer propose_open_issue_solution for non-definitive / advisory fixes. Returns: the winning solution and the resolved open issue — marks the issue resolved immediately. Do not use when: you only want to attach a candidate without closing (use propose_open_issue_solution), or no matching open issue exists (use submit_solution). Safety: there is no preview gate — remove secrets, PII, and proprietary context from the solution before calling.
    Connector
  • Use when: search found no same-root-problem match and you solved a generic reusable technical issue worth sharing. Returns: the published solution record and URL — publishes immediately, there is no confirmation step. Do not use when: an existing solution covers the same problem (use suggest_edit or add_addendum). Safety: there is no preview gate — remove secrets, PII, company names, private URLs, and incident-specific details before calling.
    Connector
  • Check the status of the API key you're using right now — see call count, rate limit, and creation date. Useful for monitoring your MCP usage. TRIGGERS: - 'check my API key', 'API key status', 'how many calls have I made' - 'my usage', 'rate limit status', 'key info'
    Connector
  • Delete a table. The request requires the 'name' field to be set in the format 'projects/{project}/instances/{instance}/tables/{table}'. Example: { "name": "projects/my-project/instances/my-instance/tables/my-table" } The table must exist. You can use `list_tables` to verify. Before executing the deletion, you MUST confirm the action with the user by stating the full table name and asking for "yes/no" confirmation.
    Connector
  • Fetch one NIH project application record by application ID (numeric, distinct from project number). Returns its complete abstract, public-health relevance, terms, PIs, organization, dates, and award amount. Use nih_grant_award_history for multi-year award history.
    Connector
  • Retrieve craft knowledge for building a specific form type. Returns question psychology, difficulty curves, narration style, scoring setup, and writing principles as markdown. Does NOT return a step-by-step build workflow - use clipform_get_workflow for that. Available types: quiz, survey, interview, funnel, testimonial, application, booking. Aliases also accepted: trivia → quiz, test → quiz, exam → quiz, feedback → survey, poll → survey, nps → survey, questionnaire → survey, case-study → interview, callout → interview, lead-gen → funnel, qualification → funnel, lead-magnet → funnel, story → testimonial, review → testimonial, job-application → application, admission → application, enrollment → application, grant → application, registration → booking, signup → booking, event → booking, rsvp → booking, workshop → booking. Quiz variants (optional): personality, comprehension, composition - appends variant-specific addendum to the base quiz guide.
    Connector
  • Get full detail for a Tuki solution: description, who it is for, capabilities, status and contact / CTA. Use after `list_solutions` or when the user asks about a specific Tuki product (WhatsApp Booking OS, boutique ticketing, rental inventory software, event post-sale, tailor-made tourism software).
    Connector
  • Run a raw KQL (Kusto) query against the D365FO environment's Application Insights / Log Analytics workspace (read-only -- the query language has no mutation operators). Requires the connection to be configured first via appinsights_set_connection (or server env vars). Use the standard App Insights schema: requests, dependencies, exceptions, traces, customEvents, pageViews, performanceCounters. Prefer appinsights_diagnose_slowness for a ready-made "why is it slow" report -- use this tool for anything more specific/custom. Triggers: 'run this KQL', 'query app insights', 'requête KQL', 'log analytics query', 'custom App Insights query for my environment'.
    Connector
  • For puzzle/CTF/bounty contracts: classifies each as locked_no_payout (funded but a correct solution pays nothing — the funds can never leave, e.g. TeikhosBounty), frontrun_bait (pays msg.sender/tx.origin on a calldata condition → broadcasting the solution publicly will be front-run; submit privately), owner_only_payout, claimable, indeterminate or unfunded — from a verified-source payout-path analysis + a bytecode value-exit scan. view="summary" returns per-class counts + ETH-at-stake rollups + a teaser; view="detail" returns the full annotated watchlist (paid via x402 at GET /v1/premium/puzzle-risk; served here for agents); pass `address` for a single-contract verdict. Heuristic — verify on-chain before acting.
    Connector