"Information about Proxmox virtualization and server management" matching MCP tools:

• search_contentA

  flevyA

  Search Flevy's marketplace of consulting frameworks, PowerPoint templates, Excel financial models, business toolkits, and management case studies. Use this whenever a user needs a best-practice framework, methodology, template, financial model, or real-world case example on any business or management topic (strategy, digital transformation, supply chain, pricing, operational excellence, M&A, etc.). Returns up to 10 relevance-ranked recommendations across two content types: "document" (premium documents authored by management consultants) and "case_study" (management case studies). ALWAYS include each recommended item's url as a clickable link when you mention it in your reply — never reference a document without its link, because the link is the only way the user can open it. Each result carries a content_id for get_content_details. Filters: topic (single, or "topics" for documents covering ALL of several topics), author (list more documents from an author seen in results), filetype (including tier1_consulting_deck for McKinsey-style strategy decks), content_type. Topic-filtered responses also list related_topics to pivot to. Provide at least one of query, topic(s), or author; use list_topics to map user phrasing to a canonical topic.

  ConnectorNo auth

• update_password_policyA

  The BridgeA

  Set the session token lifetimes on the Bridge app: accessTokenTTL and refreshTokenTTL, both in SECONDS. Only the fields you pass are changed. IMPORTANT — despite the name (kept for parity with `bridge auth password-policy`), this sets token TTLs and NOTHING about passwords: Bridge exposes no password-complexity, rotation or reuse policy on the management API, so if the user asked for password rules, say so instead of calling this. The access token TTL controls how often a client silently refreshes (short is safer, e.g. 900 = 15 minutes); the refresh token TTL controls how long a user stays logged in without re-authenticating (e.g. 2592000 = 30 days). Read the current values with get_auth_config. Before writing app code that consumes this, call get_integration_guide with topic=auth and the framework the app uses.

  ConnectorOAuth

• get_wedding_informationA

  The Hill KinabaluA

  Retrieve The Hill Kinabalu’s official public wedding venue and 2026/2027 package information, including capacity, event sizes, starting package prices, key inclusions, add-ons without prices, payment structures, and enquiry links. Use this when someone asks about weddings, wedding packages, the event venue, guest capacity, package pricing, or how to enquire. This tool does not check date availability or submit an enquiry.

  ConnectorNo auth

• create_project_tokenA

  EchoRelayA

  Mint a PROJECT-scoped management token (`er_mcp_`) for MCP and REST; it cannot authenticate relay traffic. Use it after create_project to configure a fresh project, or for any project you already own. Attenuated by design: the scopes must be a subset of THIS management token's own grant (`read` is always included), expiry is mandatory (1–90 days, default 30, never "never"), and the minted management token (being project-scoped) can never mint management tokens itself. `spend` is human-granted only: no management token, of any scope, can mint one carrying it. Mint a spend-scoped token from the project's panel instead. Requires an ACCOUNT-scoped management token and the `config` scope. Returns the plaintext exactly once; only its hash is stored.

  ConnectorNo auth

• migrate_to_propelauth_fullstackA

  PropelAuth Integration MCP ServerA

  Returns instructions for migrating from an existing auth provider to PropelAuth in a fullstack Nextjs App Router or Nextjs Pages Router application. If the user is using Next.js as just a frontend (e.g. client-side rendered with or without server routes), use the migrate_to_propelauth_frontend tool. Guidance includes installation and configuration, retrieving user or org information, logging users out, redirecting users to login, and more. Make sure to use the 'Installation' guidance first. It is important to call every guidance to ensure a successful integration. Do not update a component/hook/etc from the auth provider until you receive guidance about that component/hook/etc

  ConnectorNo auth

• get_product_detailA

  Easyparser — Amazon Product & Seller DataA

  Fetch complete, structured information about a single Amazon product: title, brand, images, feature bullets, description, Buy Box price and availability, Prime eligibility, rating and review count, Best Sellers Rank, category path, variants, specifications, and top reviews. This is the primary tool for product analysis, listing enrichment, and price monitoring. Use this tool when you need a full product profile. If you only need competing seller prices, use get_product_offers instead (cheaper context). If you only need the sales rank, use get_bestseller_rank. If you only need shipping dimensions or the FBA fee category, use get_package_dimensions. Provide EITHER the identifier field OR url — never both. Costs 1 credit; set a_plus_content to true only when the user explicitly asks about enhanced brand content, as it costs 1 extra credit.

  ConnectorNo auth

• create_conversationA

  ISMS CopilotA

  Ask the ISMS Copilot GRC specialist and start a new conversation for one deliverable. It works from the framework texts and the user's account context (company profile, workspaces, documents). Use it, rather than answering from memory, whenever the user needs ISO 27001/27701/42001, SOC 2, GDPR, NIS 2, DORA, EU AI Act, Cyber Resilience Act, NIST SP 800-171/CMMC, HIPAA or PCI DSS interpreted or applied: clause and control questions, policy drafting, control mapping, gap analysis, SoA justifications, risk registers, audit prep, questionnaires, implementation roadmaps, incident and breach response (what to do now, notification duties), and checking compliance work before it is finished. You do the work and read the files; ISMS Copilot judges. Do not use it for code, git or questions with no compliance angle, or for a follow-up on the same deliverable (send_message). Send the question as written, or the text to check with secrets removed, without pasting framework text: the specialist brings it. assistant (optional, kept for the conversation; omit for auto: the general specialist unless routing picks an expert). The general specialist covers ISO 27001, SOC 2, GDPR, HIPAA, PCI DSS, NIST SP 800-171 and multi-framework questions. Rule: a task to do takes the job id even when it names a framework; a question about one framework takes that framework's id; else omit assistant. - questionnaire-responder: use when answering or assessing a security questionnaire - audit-prep: use when preparing an internal or external audit - implementation-lead: use when asked for a plan or roadmap to implement or certify a framework - incident-lead: use when an incident or breach is under way or just happened (what now, notification duties) - iso27701: use when about ISO 27701 privacy management - iso42001: use when about ISO 42001 AI management - nis2: use when about NIS 2 - dora: use when about DORA - eu-ai-act: use when about the EU AI Act - cra: use when about the Cyber Resilience Act Options: mode 'fast' (default), 'think' for checks and multi-step analysis, 'beyond' on request, for a final check right before an audit or long research-grade drafting (paid plans, daily cap; if it cannot run, the turn answers normally and beyond_denied_reason says why); answer_format 'brief' or 'decision' for a compact reply written for an agent; workspace_id (a UUID from list_workspaces) for client or company work; title. Returns conversation_id, message_id and status: 'complete' with response, or 'generating': then poll get_reply. Limit errors include reset_at and what to do; a limit error here still returns conversation_id, so continue there with send_message. Relay docgen_notice to the user when present. ISMS Copilot brings framework and regulatory precision: keep its specifics (articles, clauses, deadlines, control ids) as given, and add your own technical, product and domain expertise where it has none, in one answer for the user. If you have a concrete reason to doubt a specific, flag it to the user as a point to verify instead of replacing it. Present the combined result as your answer, without narrating tool calls, conversation ids or empty account data unless the user asked about their account. Do not include passwords, API keys, payment card numbers, health records or government ID numbers. Answers are informational, not legal advice.

  ConnectorAPI key

• flow_lookup_pos_apiA

  Final POS – Custom POS BuilderA

  Look up the Final POS REST API (https://api.finalpos.com) — endpoint method/path, request fields, response shape, and a worked fetch example. This is the ONLINE-ONLY fallback for admin/management operations command-frame cannot express (creating products/variants/categories, customer management, outlets/stations/tax tables, webhooks). Command-frame is ALWAYS first choice for live POS data — it works offline and the host owns money/totals. A call to this API is network egress from the station: it fails whenever connectivity does, so never put one in the sale path — use it for setup/admin work and degrade gracefully. Pass resource to list a domain, operation for one endpoint, or query for fuzzy search.

  ConnectorOAuth

• get_earnings_call_summaryA

  TipRanksA

  Returns the most recent earnings call summary for a ticker — management guidance text, overall call sentiment (positive / neutral / negative with a one-line rationale), and AI-extracted highlights and lowlights from the call as {title, content} bullets. This is a structured summary derived from the call, not the raw transcript text. Useful for "what did management say about X on the last call", "was the most recent call bullish or bearish", or "summarise the highlights from MSFT's latest earnings". Only the most recent quarter is stored per ticker; for historical EPS actual-vs-estimate series use get_earnings_history. Args: ticker: Stock ticker (e.g. 'AAPL', 'NVDA'). Returns: { ticker, fiscal_year, fiscal_quarter, guidance, sentiment: { label, summary }, highlights: [ { title, content }, ... ], lowlights: [ { title, content }, ... ] }

  ConnectorNo auth

• searchA

  Vascue Public Knowledge SearchA

  Hybrid keyword + semantic search over the public pages of vascue.io: healthcare-operations guides, Vascue Front Desk for clinics, provider-side insurance-claims automation, practice-management integrations (two-way sync with Cliniko and Nookal; Jane, Mindbody, PracticeHub, HexaHealth, Halaxy, Clinicea, ClinicOffice, Semble, Plato Medical and JERA in progress), security and compliance pages, case studies, pricing and blog posts. Use it to answer questions about what Vascue offers, how its products work and what it has published. One topic per call; cite the returned page URL for every excerpt you use. Returns a JSON text payload: result.chunks[] ordered by relevance, each with text (a Markdown excerpt), score (0-1, higher is better) and item.metadata.url (the canonical https://www.vascue.io/... page). Off-topic queries still return the nearest chunks, so treat scores below about 0.5 as weak evidence and say so when the site does not cover a topic. Read-only and idempotent; no authentication; 60 requests per minute per client. Public content only: never send patient information, claim documents, clinic credentials or booking requests. It cannot book appointments or look up clinic data.

  ConnectorNo auth

• searchA

  Vascue Public Knowledge SearchA

  Hybrid keyword + semantic search over the public pages of vascue.io: healthcare-operations guides, Vascue Front Desk for clinics, provider-side insurance-claims automation, practice-management integrations (two-way sync with Cliniko and Nookal; Jane, Mindbody, PracticeHub, HexaHealth, Halaxy, Clinicea, ClinicOffice, Semble, Plato Medical and JERA in progress), security and compliance pages, case studies, pricing and blog posts. Use it to answer questions about what Vascue offers, how its products work and what it has published. One topic per call; cite the returned page URL for every excerpt you use. Returns a JSON text payload: result.chunks[] ordered by relevance, each with text (a Markdown excerpt), score (0-1, higher is better) and item.metadata.url (the canonical https://www.vascue.io/... page). Off-topic queries still return the nearest chunks, so treat scores below about 0.5 as weak evidence and say so when the site does not cover a topic. Read-only and idempotent; no authentication; 60 requests per minute per client. Public content only: never send patient information, claim documents, clinic credentials or booking requests. It cannot book appointments or look up clinic data.

  ConnectorNo auth

• transcript_searchA

  aether-developerA

  Search earnings-call transcripts and earnings press-release exhibits by speaker turn (CEO/CFO prepared remarks, analyst Q&A, press releases). Returns verbatim quotes as agent-ready payloads: speaker name/role, fiscal year + quarter, call date, source_type (asr_call = our own ASR of the real call vs press_release), sec.gov source URL and citation string. Use for guidance, management tone and forward-looking color that filings don't capture; pair with financial_search to back narrative with filed numbers. ALWAYS pass `issuer` (the ticker whose calls you mean) plus `fiscal_year` when you know it — a named call is scoped to that issuer's calls, fast and precise. A call with no issuer runs as scope=cross_company: slower, ranked by relevance only, and the response sets `quality_caveat` — check for that field. Use scope=cross_company deliberately, only for questions genuinely about many companies ("which management teams talked about tariff pass-through"). Narrow further with speaker_role, lookback_quarters or source_type. FETCH MODE: omit `query` entirely and pass issuer.ticker plus fiscal_year / quarter / date_from / date_to to get that call's segments back in call-date-desc then spoken order, with no ranking and in tens of milliseconds — the right tool when you already know WHICH call you want. For onset/"first mention" questions (when did a topic first come up), bound with date_from/date_to and set order='earliest' — a date pair, not a fiscal year, is the right tool there. Fetch mode pages: pass the response's `next_offset` as `offset` to read past `limit`. Returned windows overlap; counts of a term over returned text are not document counts. `partial: true` means retrieval degraded; an empty result is then not proof of absence. A cross_company call that times out returns a clean 503 telling you to name an issuer.

  ConnectorNo auth

• list_referencesA

  Cloud FinOps Skill & MCPA

  See what FinOps guidance is available: billing mechanics, commitment strategy, allocation and chargeback, AI cost management, and per-provider cost handbooks (AWS, Azure, GCP, OCI, Databricks, Snowflake, ...). Use this to discover what the library covers before deciding what to fetch. When the question already names a FinOps domain, phase, persona or maturity, call ``find_references`` instead of scanning this full list. Returns a dict shaped ``{"references": [...], "total": N}`` where each entry includes ``name``, ``title``, a one-line ``description``, the discriminating FCP facets (``fcp_domain``, ``fcp_capability``, ``fcp_phases``, ``fcp_personas_primary``, ``fcp_maturity_entry``) and ``approx_tokens``. Read ``approx_tokens`` before fetching: the library runs from about 2,000 to about 15,000 tokens per file. Above roughly 10,000, prefer ``get_reference(name, section=...)`` and pull the part you need.

  ConnectorNo auth

• get_page_linkA

  SequencerC

  Get information about a page and provide a clickable link the user can optionally click. ⚠️ DO NOT USE THIS TOOL when users explicitly ask to "go to", "take me to", "open", "show me", or "navigate to" a page. For those requests, use navigate_to_page instead - it will automatically navigate them. USE THIS TOOL ONLY when: - Answering questions ABOUT a page (e.g., "what can I do on the billing page?") - Suggesting a page the user MIGHT want to visit (but didn't explicitly ask to go there) - Providing reference links in your response The tool returns a NAV_OFFER tag that renders as a clickable button (user must click to navigate). Available pages by category: MARKETING: home, studio, pricing, about, careers, feedback, extension, branding DASHBOARD: projects, images, videos, audio, workflows, billing EDITOR: editor, workflowEditor, flowRunner, publicFlow MODEL ARENA: compare, compareImageToVideo, compareTextToVideo, compareTextToImage, compareElementToVideo, challenges COMMUNITY: explore, jobBoard, tutorials, tutorialShortcut TUTORIALS: tutorial3DRepositioning, tutorialVoiceNormalization, tutorialBlending, tutorialCharacters, tutorialUpscaling, tutorialHooks, tutorialWriting, tutorialRealEstate EVENTS: events, filmFestival LEGAL: privacy, terms CODES: affiliate, codes, claimCode ADMIN: admin, adminArena, adminFestival, adminNewsletters

  ConnectorAPI key

• get_account_statusA

  OneQAZ Trading IntelligenceA

  Purpose: Show which OneQAZ account (or API key) this connection uses, its plan and its rate limits. Requires a connected OneQAZ account — calling it without one prompts your AI app to connect (free, no API key needed; Pro users can use their key). All other tools work without an account. Triggers: "is my OneQAZ account connected?", "what plan am I on?", "내 OneQAZ 계정 상태", "남은 호출 한도". When to call: only when the user asks about their own account or limits. Output: full_data { principal (oauth|api_key), plan, usage {daily_limit, daily_used, minute_limit, ...}, account_id & connected_app (oauth only) }. Output nature: Service status and catalog information.

  ConnectorNo auth

• ssh_repair_nodeA

  AnkraB

  Repair one Kubernetes node of an Ankra-provisioned cluster (Hetzner, OVH, UpCloud, DigitalOcean, or Scaleway) at the OS level over SSH-via-bastion: restarts the node's Kubernetes service unit (k3s / k3s-agent / kubelet) wrapped in Ankra's node-recovery engine, which classifies the failure and applies the matched curated fix (clear a failed unit, extend a start timeout, kill stale listeners, unblock the apiserver firewall, re-bootstrap the kubelet), verifies, and retries once. This is a privileged, not-cleanly-reversible action on a production node and briefly disrupts its workloads, so it requires confirmation. It does NOT run arbitrary commands - only the curated recovery plan. Always call ssh_diagnose_node first to confirm the node is broken at the OS level (not merely unreachable via bastion, which a node reboot - restart_node - addresses instead). Identify the node with node_id (preferred) or node_name. Not available for imported or managed-Kubernetes clusters, nor (yet) Proxmox/HPE Morpheus.

  Connector

  Destructive

  OAuth

• scale_workersA

  AnkraB

  Scale the workers of an Ankra-provisioned self-managed cluster (Hetzner, OVH, UpCloud, DigitalOcean, Scaleway, Proxmox VE, or HPE Morpheus). With node_group_name, scales that node group to worker_count (0-100; the target is clamped into the group's autoscaling bounds when autoscaling is enabled); without it, performs the legacy whole-cluster scale to worker_count (1-10; refused while any node group has autoscaling enabled - scale the group directly instead). The cluster must be online and free of in-progress operations. New workers provision in the background. On scale-down the highest-index workers drain one at a time through the eviction API, honouring PodDisruptionBudgets, and are then terminated; a worker whose drain a PodDisruptionBudget refuses is kept in service and the scale-down is withdrawn for it, so the group can settle above worker_count. Call list_node_groups first to see the current counts, and again afterwards to confirm them.

  ConnectorOAuth

• change_control_planeA

  AnkraB

  Change the control plane of an Ankra-provisioned self-managed cluster. Provide exactly ONE of: count (1 or 3; additionally 5 on Proxmox VE - etcd quorum needs an odd number) or instance_type (resizes every control plane node). GROWING the count (1 -> 3, 3 -> 5) happens LIVE on a running cluster: the new control planes provision and join etcd without downtime, and the answer carries the operation to follow. REDUCING the count is applied offline: stop the cluster (the stop preserves its state and the start restores it), apply the change, then start_cluster. instance_type changes roll one controller at a time on a running cluster with 3 or more controllers. On a RUNNING cluster with a SINGLE controller (Hetzner), changing instance_type resizes that one server in place and TAKES THE KUBERNETES API DOWN for a few minutes (typically 3 to 8) while it reboots: workloads already running on workers keep running, but kubectl, deployments, controllers and the Ankra agent pause until it is back. That call REQUIRES accept_api_downtime=true and is refused without it; only set it when the user has explicitly accepted the API downtime, and tell them about it first. The alternatives are growing to 3 controllers first (no downtime) or applying the change offline on a stopped cluster. Call list_node_groups first - its control_plane section reports the current count/instance type, whether a change is possible right now, and in which mode.

  Connector

  Destructive

  OAuth

• request_provider_quota_increaseA

  AnkraB

  Raise a cloud-provider limit for a credential, or produce the exact request a person has to submit when the provider has no API for it. Call get_provider_quotas first: it names the dimensions and says whether the provider is automatable. Azure is the only provider Ankra can submit to (through the Microsoft.Quota API); for Hetzner, OVH, UpCloud, DigitalOcean, Scaleway, Proxmox VE and HPE Morpheus this call still SUCCEEDS and returns status manual_action_required with a manual_action object holding the console URL, the navigation path and a ready-to-paste request_text pre-filled with the live numbers - relay that to the user rather than retrying. One call may at most double a limit (or add 16 to a small one); ask for more by repeating the call. The limit can only go up: this tool will not lower one.

  Connector

  Destructive

  OAuth

• check_cluster_mesh_readinessA

  AnkraB

  Check whether the given clusters could form one mesh, with the failing checks spelled out per cluster. Takes CLUSTER ids, not a mesh id. Read 'eligible' before 'ready': ready means the cluster can join right now, eligible means it can join now OR after make_cluster_mesh_ready prepares it in place, and only an ineligible cluster has to be rebuilt. Each check also reports 'remediable' individually - a failing identity or transport check on an upcloud or proxmox kubeadm Cilium cluster is remediable, so reach for make_cluster_mesh_ready; the cloud, the distribution and the container network are not, and no operation on a running cluster changes them. Always run this before create_cluster_mesh so you can tell the user which clusters actually qualify. Read-only.

  ConnectorOAuth

• send_messageA

  ISMS CopilotA

  Continue a conversation with the ISMS Copilot GRC specialist on the same deliverable: refine the same policy, extend the same gap analysis, or ask the next question. Use it with the conversation_id that create_conversation returned. Do not use it to start a new deliverable (create_conversation), or while the previous turn is still generating: wait for get_reply, since a send then is rejected. assistant (optional): switches the assistant from this turn on; omit to keep it, 'general' for the general specialist. Rule: a task to do takes the job id even when it names a framework; a question about one framework takes that framework's id; else omit assistant. - questionnaire-responder: use when answering or assessing a security questionnaire - audit-prep: use when preparing an internal or external audit - implementation-lead: use when asked for a plan or roadmap to implement or certify a framework - incident-lead: use when an incident or breach is under way or just happened (what now, notification duties) - iso27701: use when about ISO 27701 privacy management - iso42001: use when about ISO 42001 AI management - nis2: use when about NIS 2 - dora: use when about DORA - eu-ai-act: use when about the EU AI Act - cra: use when about the Cyber Resilience Act Options: mode and answer_format as on create_conversation. Returns conversation_id, message_id and status: 'complete' with response, or 'generating': then poll get_reply. Limit errors include reset_at and what to do; when one carries fallback_available: true, resend the same message with overflow_consent: true only on the user's explicit go-ahead (no duplicate message is saved). Relay docgen_notice to the user when present. Do not include passwords, API keys, payment card numbers, health records or government ID numbers. Answers are informational, not legal advice.

  ConnectorAPI key