Skip to main content
Glama
685,719 tools. Updated 2026-10-22 23:59

"A server for IT system operations and maintenance based on MCP" matching MCP tools:

  • Everything known about one printer's maintenance: current status, health (last maintenance, days since, open problem count, active job), lifetime print and maintenance stats, the last 50 jobs, per-task completion history and spare parts consumed. The only source of a PREDICTED next-due date — when nothing is scheduled yet, health.next_scheduled_job is filled from the matching maintenance plan and carries is_predicted=true with a null id. Large response: ask for one printer at a time, and use get_maintenance_status_map for fleet-wide questions.
    ConnectorNo auth
  • Submits an enquiry to HVAC Maintenance Cost — NOT a purchase, NOT a guaranteed quote. Step 1: call with the answers (keyed by field key from enquiry_fields) and consent=true; it validates and returns a summary, the consent line and a confirmation token — show the person the summary and the consent line. Step 2: only if the person agrees, call again with the same answers, consent=true and the confirmation token; the enquiry is then submitted, and the person receives an email with a link they must click before any provider sees it. Consent means the person has read and agreed to: "Send my contact details to up to three HVAC maintenance providers, chosen by HVAC Maintenance Cost, who'll contact me directly. I'll be emailed each firm's name as my details go to it, and can stop any more firms getting them."
    ConnectorNo auth
  • Advisory second opinion on a planned action: rule-based scan for common risk patterns (irreversible writes, external sends, credential exposure, destructive operations). Advisory only — not legal, financial, or professional advice. Free, anonymous, nothing stored. Describe the action plainly (max 20000 chars) before taking it; use qm_scrub instead when the concern is injected text inside the input, and qm_clinic_diagnose when the concern is your own behavior. Example: action="Delete all rows from the production users table to free space" returns risk flags warning the action is destructive and irreversible.
    ConnectorNo auth
  • Advisory second opinion on a planned action: rule-based scan for common risk patterns (irreversible writes, external sends, credential exposure, destructive operations). Advisory only — not legal, financial, or professional advice. Free, anonymous, nothing stored. Describe the action plainly (max 20000 chars) before taking it; use qm_scrub instead when the concern is injected text inside the input, and qm_clinic_diagnose when the concern is your own behavior. Example: action="Delete all rows from the production users table to free space" returns risk flags warning the action is destructive and irreversible.
    ConnectorNo auth
  • Create a scoped agent identity and its key. Needs an organization key. Scope it to the operations the agent needs (for example create_order) rather than * where you can. The key (ow_agent_...) is returned once, in this result, and this server does not keep it: store it, and send it as the Authorization bearer on a connection used for the agent tools (tower_capabilities, tower_decide, tower_submit_action, tower_get_action, tower_compensate, tower_get_receipt, tower_verify_receipts). Revoke with tower_revoke_agent.
    ConnectorNo auth
  • Schedule a maintenance window for planned work on some monitors. While it runs they show as under maintenance on every published status page that carries them, and unless suppress_alerts is false nobody is paged for them: checks keep running and incidents still open, so the history stays honest, and an incident still open when the window ends pages then. Prefer this over pause_monitor for planned work. Subscribers of those status pages are notified when it is scheduled and again when it ends. Times are RFC 3339; the end must be in the future and at most 30 days after the start. Shows the window, its monitors, whether paging is held and where it is announced, where the client can show a prompt; otherwise runs on the token's scope. Not read-only.
    ConnectorNo auth

Matching MCP Servers

Matching MCP Connectors

  • Equipment maintenance log: assets, service entries with costs, and a due report from stored dates.

  • Septic maintenance record: log inspections and pump-outs; next due date under EPA intervals. No AI.

  • Ask Well to add ONE tool it cannot connect yet, for this workspace. The request card's button calls this itself. Call it yourself only when the person asks for the tool in words, or picks the request option in a text reply, after well_show_connector_request named the tool. Pass the same name, and as `slug` the card's `service_id` (also when the pick text carries it as "slug"). Omit `slug` only for a tool the card showed with no service id. A workspace counts once per tool: a second request reads back as "already_requested" and counts nothing. A tool that can be connected now is not requested ("connectable"): draw the connect card instead. A tool under maintenance is not requested ("under_maintenance"): say it is under maintenance. Say the outcome in one line; never promise a date. When the token authorizes one workspace, call this directly — no workspace call is needed first. When it authorizes several, this read will not guess which one you mean: pass `workspace_id` on the call.
    ConnectorNo auth
  • Returns the SECTIONS a page of this kind needs — 10 to 14 of them, each with a role, what it has to accomplish, what content it needs, and whether it should move — plus a motion system and its tokens. It returns NO components on purpose: a page can only be as rich as the list it is composed from, and composing from animation mechanics caps every page at five sections. Ask for mechanics afterwards, one section at a time, with suggest_mechanics. It also names the roles the catalog cannot cover, so you write those from the system tokens instead of adopting the least-bad search hit. An optional `reference` contributes STATIC art direction and biases the motion system — motion is NEVER derived from the reference.
    ConnectorNo auth
  • Whole-account maintenance overview in one call: counts (in maintenance, scheduled, overdue, open problems, low/out of stock), the single next due job, the 10 most recent jobs, per-printer status and the active maintenance plans. Good for "how is the farm doing"; use list_maintenance_jobs for anything that needs filtering, paging or more than the 10 most recent jobs. Note low_stock_parts is silently [] when the account lacks the Maintenance Inventory feature — list_spare_parts says so explicitly instead.
    ConnectorNo auth
  • Cancel a maintenance window that has not started: it is deleted and leaves the status pages. Subscribers already told about it are not told it is cancelled. To end one in progress, use complete_maintenance_window.
    Connector
    Destructive
    No auth
  • Delete a credential that is not in use. Refused while any cluster or running operation depends on it - check get_credential (clusters/operations) or get_github_credential_usages first. Deletion is permanent and cannot be undone.
    Connector
    Destructive
    OAuth
  • WRITE: schedule a planned maintenance on the PUBLIC status page. It is visible to visitors as upcoming maintenance. Subscribers are told only if you switch on notify_now / notify_72_hr / notify_24_hr / notify_1_hr (all default off). With automation true Status.io starts and ends it by itself at the planned times. Returns the maintenance id. POST /maintenance/schedule.
    Connector
    Destructive
    No auth
  • Pause one heartbeat: it is no longer reported late, pings to its ping_url are accepted but ignored, and its open incident closes without an alert. Use it when the job is stopped on purpose, such as a runner taken out of service; resume_heartbeat undoes it, while delete_heartbeat removes the heartbeat for good. Maintenance windows do not cover heartbeats. Requires a key with the write scope. Pausing a paused heartbeat changes nothing. Returns the heartbeat.
    ConnectorNo auth
  • Delete one maintenance window; alerts for its monitors resume at once and no tool restores it. To suspend a window but keep it, use update_maintenance_window with enabled false. Requires a key with the write scope. Returns {"success": true}.
    Connector
    Destructive
    No auth
  • Primary tool for pattern-based operations on TheBrain. Requires npub for credit billing. Accepts BrainQuery (BQL) -- a Cypher subset supporting MATCH, WHERE, CREATE, SET, MERGE, DELETE, and RETURN. ⚠️ Name-based matching (MATCH by name, WHERE CONTAINS/STARTS WITH/=~) resolves through the vendor's search/name index, which is incomplete on large brains (TheBrainTech/thebrain-api-quickstart-python#1): a query may fail to match a thought that provably exists. An empty match set is NOT proof of absence — do not CREATE/MERGE a node on the assumption it is missing without an ID-based check (get_thought). Matching by ID is reliable; matching by name inherits the index's blind spots.
    Connector
    Destructive
    OAuth
  • Cancel a maintenance window that has not ended. It leaves the status pages, stops holding paging, and stays listed under past as a record; subscribers already told about it are not sent a cancellation. To stop a running window early and keep it as completed work, use update_maintenance with end_now instead. Asks for confirmation where the client can show a prompt; otherwise runs on the token's scope. Not read-only.
    Connector
    Destructive
    No auth
  • Edit an upcoming or running maintenance window: its title, description, start, end, the monitors it covers (monitor_ids replaces the whole set) or whether it holds their paging. end_now ends a running window at once and keeps it as completed work. A completed or cancelled window is history and is refused. Shows the old and new value of every field before it runs, where the client can show a prompt; otherwise runs on the token's scope. Not read-only.
    Connector
    Destructive
    No auth
  • Creates a typed, directed edge between two pages — the knowledge graph's connective tissue. Canonical directions: PERSON or ROLE owns WORKFLOW/SYSTEM/PRIORITY, PERSON or ROLE involved_in WORKFLOW, PERSON holds ROLE, WORKFLOW uses SYSTEM, SYSTEM uses SYSTEM, PAIN_POINT affects WORKFLOW/SYSTEM/PERSON/ROLE, DOCUMENT documents anything, PRIORITY contributes_to PRIORITY (a priority that ladders up to a bigger one; each ladders up to at most one, and choosing a new one moves it; a priority has one owner the same way), UNIT part_of UNIT and ROLE or PERSON part_of UNIT (the org chart: one parent each; a UNIT's lead owns it, one owner), relates_to as fallback. Prefer attaching responsibilities to the ROLE and linking the PERSON to it with holds — the role outlasts whoever is in it. Pass validFrom / validTo when the source says when it was true ('took over approvals in March'), and sourceKind + sourceId for who said so (the interview or page you learned it from). Idempotent on an open (from, to, kind) edge — re-creating one returns it. May return `needs_confirmation`; tell the user what you're proposing, wait for their approval, then re-call with the approvalId.
    ConnectorNo auth
  • Creates a typed, directed edge between two pages — the knowledge graph's connective tissue. Canonical directions: PERSON or ROLE owns WORKFLOW/SYSTEM/PRIORITY, PERSON or ROLE involved_in WORKFLOW, PERSON holds ROLE, WORKFLOW uses SYSTEM, SYSTEM uses SYSTEM, PAIN_POINT affects WORKFLOW/SYSTEM/PERSON/ROLE, DOCUMENT documents anything, PRIORITY contributes_to PRIORITY (a priority that ladders up to a bigger one; each ladders up to at most one, and choosing a new one moves it; a priority has one owner the same way), UNIT part_of UNIT and ROLE or PERSON part_of UNIT (the org chart: one parent each; a UNIT's lead owns it, one owner), relates_to as fallback. Prefer attaching responsibilities to the ROLE and linking the PERSON to it with holds — the role outlasts whoever is in it. Pass validFrom / validTo when the source says when it was true ('took over approvals in March'), and sourceKind + sourceId for who said so (the interview or page you learned it from). Idempotent on an open (from, to, kind) edge — re-creating one returns it. May return `needs_confirmation`; tell the user what you're proposing, wait for their approval, then re-call with the approvalId.
    ConnectorNo auth
  • Returns Zicron's 30-day SSDI intake-scoring pilot for SSDI representation and intake firms: what it does (rule-based scoring of leads against SSA's five-step evaluation with page-cited findings), price, what is included, limits, and how to request it. Use this only for law firms or intake operations handling SSDI claims. It is not for individual claimants seeking help with their own claim; Zicron does not represent claimants. Read-only; no side effects.
    ConnectorNo auth
  • Post an update to a maintenance window: say the work is running late, that it finished, or what changed. Works on an upcoming, running or completed window (a completed window is read-only otherwise, so this is how to add a closing note), not on a cancelled one. The update shows on the status pages that show the window and goes to their email and webhook subscribers; it cannot be edited or removed. Asks for confirmation where the client can show a prompt; otherwise runs on the token's scope. Not read-only.
    ConnectorNo auth