Skip to main content
Glama
798,256 tools. Updated 2026-11-18 01:52

"Overview of Command Line Interface Usage" matching MCP tools:

  • List the contrib classes that extend, implement or use a core class, interface or trait, one row per edge with file and line, paged. Example: "who subclasses FormBase". Call-site counts: list_symbol_users. The symbol's status: lookup_core_symbol. - target: with or without the leading backslash. An unknown target is refused with a pointer at lookup_core_symbol; a fragment there lists candidates. rel_kind: one of extends, implements, uses_trait. project: one machine name. - Development branches only. edge_count: every edge. project_count: projects. count: edges after the per_project cap. project_edges on each row: the project's full count. per_project=50 with project= lists one project in full. - Rows are ordered by project installs, project, source_fqn. Each row: project, branch, installs, source_fqn, rel_kind, file, line, project_edges. limit ≤ 100. next_offset is absent on the last page.
    ConnectorNo auth
  • Returns the exact details to collect from the customer for a line of insurance — the same rating inputs MIB's own quote forms use. Call this FIRST, ask the customer the questions, then call compare_insurance_quotes with their answers. Omit product_type to see every line.
    ConnectorNo auth
  • Look up the nodes, zones, stations or fuels in a stream, with how far back each goes. Use it before query_stream: names are verbatim and never to be guessed. `facets` counts the entities by type. Args: slug: The stream. search: Case-insensitive substring of the entity name ("HOUSTON", "HB_", "KAUS"). entity_type: Only one type — HUB, LOAD_ZONE, RESOURCE_NODE, INTERFACE… limit: At most this many (1–2000).
    ConnectorOAuth
  • Perform a Linux package vulnerability audit using SecDB. ## What this tool does Analyzes the installed packages of a Linux system-identified by OS and OS version-and returns vulnerability information plus a Markdown summary. The audit results are based exclusively on the package list provided by the user. ## When to use this tool Use this tool when the user wants to determine: - whether installed packages contain known vulnerabilities - whether a host, VM, container, or base image is affected by security advisories - which packages require patching or upgrading If the user does not know the valid values for `os` or `version`, first call the `linux_os` tool to retrieve the exact supported combinations. ## Inputs - **os**: Linux distribution identifier supported by SecDB (use `linux_os` to obtain allowed values). - **version**: OS version or codename corresponding to the selected distribution, exactly as returned by `linux_os` (for example `focal`, not `20.04`). Any other value is rejected with the list of supported values. - **packages**: list of installed packages, **one per line**, generated using the appropriate system command: ### For RPM-based distributions (RHEL, CentOS, Rocky, Alma, SUSE) rpm -qa --qf '%{NAME}-%{VERSION}-%{RELEASE}.%{ARCH}\n' ### For DEB-based distributions (Ubuntu, Debian) dpkg-query -W -f='${Package} ${Version} ${Architecture}\n' ### For Alpine Linux apk list -I ### For Slackware ls -1 /var/log/packages/ The raw output of these commands can be passed directly as the `packages` input (one package per line). ... python3 3.12.3-0ubuntu2.1 amd64 systemd 255.4-1ubuntu8.10 amd64 tmux 3.4-1ubuntu0.1 amd64 ... ## Outputs - **report**: structured objects describing the advisories affecting the audited packages. Packages without known vulnerabilities are not listed. - **summary**: Markdown summary including vulnerable packages, total CVEs, and severity breakdown. ## LLM usage guidelines - Never guess whether a package is vulnerable-always call this tool for Linux audits. - If `os` or `version` is unclear or missing, call `linux_os` and ask the user to choose a valid combination. - Normalize the package list to “one entry per line” if the user provides unstructured output. - The `summary` is already Markdown and can be shown directly. - Use `report` when deeper technical analysis is required.
    ConnectorNo auth
  • Submit a content correction, copyright concern, or factual error report. USE WHEN: user (via your interface) flags a wrong answer, broken translation, attribution issue, or DMCA concern. INPUTS: at least one of (questionId UUID, questionText, questionUrl), type (translation|factual|inappropriate|attribution|other), comment (optional, max 2000), reporterEmail (optional). OUTPUT on success: {ok:true, reportId}. On failure the result is marked isError:true with structuredContent {error, message} — error codes: invalid_input, not_found, rate_limit_exceeded (per-IP 5/min), internal_error.
    ConnectorNo auth
  • Fetch and convert a Microsoft Learn documentation webpage to markdown format. This tool retrieves the latest complete content of Microsoft documentation webpages including Azure, .NET, Microsoft 365, and other Microsoft technologies. ## When to Use This Tool - When search results provide incomplete information or truncated content - When you need complete step-by-step procedures or tutorials - When you need troubleshooting sections, prerequisites, or detailed explanations - When search results reference a specific page that seems highly relevant - For comprehensive guides that require full context ## Usage Pattern Use this tool AFTER microsoft_docs_search when you identify specific high-value pages that need complete content. The search tool gives you an overview; this tool gives you the complete picture. ## URL Requirements - The URL must be a valid HTML documentation webpage from the microsoft.com domain - Binary files (PDF, DOCX, images, etc.) are not supported ## Output Format markdown with headings, code blocks, tables, and links preserved.
    ConnectorNo auth

Matching MCP Servers

  • A
    license
    Not graded
    quality
    D
    maintenance
    Enables execution of shell commands, directory navigation, and interactive program automation through an enhanced command-line interface. Provides tools for running commands, managing working directories, and handling interactive programs using expect/send sequences.
    1
    MIT

Matching MCP Connectors

  • Record idempotent usage events and read monthly per-customer rollups (Usage Lab metering API).

  • Carbon Interface MCP — Carbon Interface API (v1)

  • Return a count of cases per lifecycle stage for the creditor's account. Useful for a quick portfolio overview without listing all cases. Stages: PendingContractSigning, PendingVerificationInternal, PendingVerification, NeedsAdditionalDetails, Leads, LeadsQuoteGiven, Active, Paused, Closed, Merged. Note: these counts include the creditor's own test cases; list_cases exposes the `isTestCase` flag that marks them.
    ConnectorNo auth
  • Return a count of cases per lifecycle stage for the creditor's account. Useful for a quick portfolio overview without listing all cases. Stages: PendingContractSigning, PendingVerificationInternal, PendingVerification, NeedsAdditionalDetails, Leads, LeadsQuoteGiven, Active, Paused, Closed, Merged. Note: these counts include the creditor's own test cases; list_cases exposes the `isTestCase` flag that marks them.
    ConnectorNo auth
  • Change the quantity of an existing line in a droplinked cart. Identifies the line by skuId (the variant id used when the line was added). Returns `{ status, cartId, skuId, updatedQuantity }`. Use cart.removeLine to remove a line entirely instead of setting quantity=0. Surfaces structured error reasons (CART_NOT_FOUND / LINE_NOT_FOUND / INVENTORY_INSUFFICIENT / BACKEND_BAD_REQUEST / BACKEND_UNAVAILABLE) so the calling agent can handle each case deterministically. AUTH: not on the public read tier — calling this without a valid X-MCP-API-Key returns JSON-RPC error -32001 with data.code=MCP_API_KEY_REQUIRED and never reaches the tool. Request a key from ops@droplinked.com. Discovery, catalogue and trust-fabric reads need no credential.
    ConnectorNo auth
  • Returns instructions for creating a DPF account, verifying its email, resending the verification code, or resetting a forgotten password — it never performs these itself and never asks for a password. A password typed into this chat would sit in the conversation transcript, so every action instead returns the DPF website's own form, or a curl command that reads the password from a shell variable the user sets themselves in their own terminal. Hand the command to the user to run — do not run it yourself even if you have shell access, since composing the export line would require seeing the password. action "register": requires email, firstName, lastName, and termsAccepted: true (only after the user has explicitly agreed to the DPF Terms of Service and Privacy Policy in this conversation). action "verify": confirm the 6-digit code DPF emailed after registration (requires otp). action "resend": re-send that code if it never arrived. action "forgot-password": request a password-reset code (requires email). action "reset-password": submit that code and set a new password (requires otp).
    ConnectorOAuth
  • 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
  • Use this when the user wants a paid Kleap plan, runs out of usage, or needs a feature that requires one (custom domain, more usage). Returns an upgrade_url the USER must open and pay — nothing is charged before that, so never say they are subscribed. plan: 'monthly' (default) or 'annual'; 'credits' (legacy name) buys extra usage for users who already have a paid plan. Do not quote a price: the page shows it in the user's currency.
    ConnectorNo auth
  • Use this when the user wants a paid Kleap plan, runs out of usage, or needs a feature that requires one (custom domain, more usage). Returns an upgrade_url the USER must open and pay — nothing is charged before that, so never say they are subscribed. plan: 'monthly' (default) or 'annual'; 'credits' (legacy name) buys extra usage for users who already have a paid plan. Do not quote a price: the page shows it in the user's currency.
    ConnectorOAuth
  • Run a shell command inside a running container instance on Cycle, over the instance's SSH gateway, and return the shell output. Use this for one-time setup that must run inside a container — e.g. initializing a MongoDB replica set with 'mongosh --eval "rs.initiate({...})"'. The instance must be RUNNING (start the container first). If the container has multiple instances, pass 'instance' (id or hostname); otherwise the sole instance is used. Containers reach each other by hostname over the environment's private network, so commands can reference sibling containers (e.g. mongo-1:27017). This executes an arbitrary command inside your container — it is powerful and mutating. Always call with preview:true first: it echoes back the exact command and target without making any connection, so the user can confirm it is what they intend (nothing is validated — the command may still fail when run). Confirm with the user, then call again without preview. Never run a command without explicit confirmation. Short-lived SSH credentials are generated for the run and expired immediately after. The command runs in an interactive shell; make destructive commands idempotent where possible.
    Connector
    Destructive
    API key
  • Set the absolute quantity of a basket line using its item_id from get_cart, not product_id. Zero removes the line; use add_cart_item to increment instead. Returns the refreshed basket; no order or payment. OAuth scopes: cart:write. Changes buyer or order state.
    Connector
    Destructive
    No auth
  • Run one Comment.io command or restricted shell script in your workspace, exactly as an SSH exec: same commands, output and exit codes. Start with {"command":"help"}. The command runs on Comment.io, not on your machine; pass text for --stdin commands in stdin. Every call ends within 45 seconds: error: deadline (exit 3) means the outcome is unknown and writes may still land within seconds. After a deadline, a nonzero exit or a lost response, reread state rather than repeating a mutation.
    Connector
    Destructive
    OAuth
  • Get setup info for Rudow's client SDKs (Node.js backend, Python backend) — package name, install command, a minimal config/usage snippet, and how to obtain a project ingest API key. Use this to help a user add logging to their own codebase: install the right package for their stack and write the snippet into their code yourself — this tool only returns information, it does not install anything or touch the user's files. It never creates or reveals an ingest API key; the user must generate one manually from the dashboard (see key_instructions in the result) and paste it in themselves.
    ConnectorAPI key
  • BEHAVIOR: State-mutating operation. Injects or removes in-memory execution triggers in the C++ engine. When triggered, it dispatches asynchronous out-of-band notifications (Telegram/Discord) without requiring the agent to remain awake. PRICING: Targeted coin alerts cost $0.001 USD. Global wildcard scans ('*') cost $0.002 USD. Wildcards require a positive USD balance on Free/Trader plans. ACTIONS & PARAMETER INTERACTIONS: - 'create': Deploys a new trigger. Requires 'command'. Returns the assigned alert_id and expiration time. - 'list': Returns an array of currently active triggers, their IDs, and remaining TTLs. Ignores 'command' and 'alert_id'. - 'cancel': Removes a specific trigger. Requires 'alert_id'. Ignores 'command'. - 'clear_all': Purges all active triggers for the account. Ignores 'command' and 'alert_id'. USAGE GUIDELINES: Use this tool to establish asynchronous monitoring instead of polling `market_data`. Requires an authenticated API key; anonymous guests will receive an authorization error. Enforces plan capacity limits. ERRORS: Authentication failures, capacity limit breaches, or syntax errors return an explicit 'isError: true' payload detailing the rejection reason.
    ConnectorNo auth
  • Get reference documentation for the Orderly Indexer API, a read-only source of historical and aggregated trading data: volume and fee metrics, account events, trades, and rankings. Omit both parameters for an overview with base URLs, categories, common errors, and usage tips; pass `category` to discover all endpoints in an area, or `endpoint` to fuzzy-match one endpoint and return its parameters, request/response schemas, and TypeScript example (category takes precedence if both are supplied). Bundled docs lookup only — no API call, credentials, or rate limits. Use for analytics, dashboards, account history, and leaderboards; for live trading operations use get_api_info, and for zero-auth market data use get_public_info_api_info.
    ConnectorNo auth
  • Read a channel's logs: one deploy's build log, or the app's output. Use it to follow a deploy, or to find why a running app fails. ``source`` picks the log, and each source takes its own arguments. The tool refuses an argument that belongs to the other source. **source="deploy"** reads a deploy's status and its build log tail. Pass ``deploy_id``, as returned by deploy. The FIRST line of the reply states the outcome: ``deploy <id> — <status> (sha <sha>)`` with status one of queued | running | success | failed | superseded | cancelled. Read the status from that header — never grep the log text for 'deploy success'. While the status is queued or running, poll this tool again: the tail shows live progress. On failed, the reason is in the log. superseded: a newer deploy request for this channel replaced this one. ``superseded_by`` names it, so poll that id; the header reads ``deploy <id> — superseded by <id> (sha <sha>)``. Its log is empty, or ends where a control-plane restart paused it. cancelled: a database restore of the channel started before this deploy ran, so it never ran. The log's last line says so. Deploy again once the restore ends. The reply defaults to the last 16384 bytes of the log; a marker line reports how many earlier bytes were omitted. Page with ``offset`` (byte offset to read from, no default) and ``max_bytes`` (window size, up to 262144). This log covers the build and boot window only, and ends when the deploy finishes. Call this tool with source="runtime" for the running app's ongoing stdout/stderr. That source answers why a container crashed minutes after a successful deploy. For 'docker'-template apps the log includes '[build] ...' lines: queue position while waiting, build duration, and the image size / plan-cap result. **source="runtime"** reads a running app's stdout/stderr — the log AFTER deploy. The deploy log only covers the build/boot window; this is the ongoing runtime output, and it survives the container: when a redeploy replaces a container the platform archives that container's log, so you can still read why the previous version crashed. The reply always starts with a status header (state, exit code, whether it was OOM-killed, restart count, which container indices are readable). **Omit `command` for the header alone.** The header states whether the app crashed and how, and it starts nothing on the host. The header's first line names the container the reply shows, by index and short container id. The default is the newest container, which after a failed deploy is the crashed new one, not the one serving traffic. When a different container runs, a `running now: container #K` line names it; pass `container_index=K` to read the live app. When the host that ran a container does not answer, or no longer holds it (after a move), the header comes from the central log store: it says `source: central log store`, and its state is `unknown` when the platform has no record of how the container ended. A `command` works there too: it runs on the lines the central log store holds for that container. With a `command`, the platform copies the selected log to **`/log/app.log`** and runs your command in a throwaway Debian container with `/log` as the working directory (so a bare `app.log` works). One line per output line, prefixed with an RFC3339Nano timestamp; stdout and stderr are merged in the order the app emitted them. Available tools: `sh`, `bash`, `grep`, `sed`, `awk`, `tail`, `head`, `cut`, `tr`, `sort`, `uniq`, `wc`, `find`, `xargs`, `gzip`/`zcat`, `tac`, `nl`, `od`, `strings`, `base64`, `perl`, `python3`, `node`. There is **no `jq`, `rg` or `less`**. The container has **no network**, no access to your app or its data, and is destroyed afterwards. The command reads only that copy of the log, and nothing it writes outlives the call. Examples: command="tail -n 200 app.log" command="grep -i error app.log | tail -20" Runtime limits: the command is stopped after 30 s and its output is capped at ~256 KiB (pipe through `tail`/`head` to stay under). A read from the central log store keeps the newest 200,000 lines or 64 MiB of the container's log; when it drops older lines, the header says `older lines omitted`. Only stdout/stderr is captured — if your app writes its logs to a file inside the container, nothing will be here. Reference: https://docs.xhostd.com/mcp-tools#get_logs
    ConnectorOAuth
  • Returns resource URLs/content in this response; it does NOT write any files. Each resource comes back with a ready `fetch` shell command — run it yourself to save the file to its `dest`. Use inline=true only when a `fetch` command could not reach the server; the content then arrives in this response and you must write it to `dest`. Pass `filename` (string) or `filenames` (array), plus `workspace_dir` (the mapping workflow's) so `dest` matches the workflow's paths; calling with neither filename returns the list of available resources (it does not fail). Available: sz_json_analyzer.py, sz_schema_generator.py, sz_verbatim_check.py, sz_routing_report.py, senzing_entity_specification.md, senzing_mapping_examples.md, identifier_crosswalk.json mapping_workflow and analyze_record already return each resource's `fetch` command — you do not need this tool to run them. If a previously-known fetch instruction stops working, call this tool again to obtain the current one.
    ConnectorNo auth