"How to create Grafana dashboards" matching MCP tools:

• cabgo_aboutA

  Cabgo BuilderA

  Public (no auth): describe what Cabgo is. Returns the full product catalog — what kinds of apps an operator can launch, pricing, who Cabgo is for, and how to onboard. Use ONLY when the user explicitly asks what Cabgo is, what it does, or wants an overview. **Do NOT call this as a pre-step before cabgo_create_my_app** — when the user wants to create / launch an app, go directly to cabgo_create_my_app without fetching context first.

  ConnectorNo auth

• teams-createA

  hjarniA

  Create a new team owned by the user (they become the owner). Required: name (string). Optional: ref — set to "assistant_suggestion" ONLY when creating in response to the me → suggestions.create_team offer, so the creation is attributed to that surface; omit it when the user asked to create a team unprompted. A user can own at most 3 free teams: at that limit this returns an error naming the teams they own and asking them to delete one — relay it rather than retrying. Returns join_url: a shareable link that lets teammates join themselves, with join_link_expires_at and join_link_uses_remaining. Offer that link FIRST — most people cannot recall a colleague's address mid-conversation — and use teams-invite when the user names a specific address.

  ConnectorOAuth

• create-credit-noteA

  OsomeA

  Create a draft credit note for the whole of an issued sales invoice (any status except draft). It is how an invoice is reversed, since issued invoices can't be deleted. Returns creditNote with its id, status draft, no number or issue date yet, and an invoice summary. Fails if the invoice already has a credit note that isn't cancelled. Nothing is applied until submit-credit-note; check it with get-credit-note. To reissue a corrected invoice, copy it with duplicate-invoice. Requires the invoice:write scope.

  ConnectorOAuth

• create-document-partyA

  fynk MCPA

  Adds a party to a document, alongside any parties it already has. Use this tool when: - A contracting party is missing from a document, e.g. the counterparty of a contract created from scratch - A signatory has to be added for a party the document does not have yet: create the party first, then add the signatory with create-document-signatory Pass party_account_party_uuid to add one of the account's saved parties (list-account-parties), usually the user's own company. A saved party can be on a document only once, and is always internal. For any other party, give party_entity_name, party_address and party_scope instead. Parties cannot be added while the document is archived, in the signing stage or an approved stage, going through an approval checkpoint, or bound by a preemptive signature.

  ConnectorOAuth

• create-document-partyA

  fynk MCPA

  Adds a party to a document, alongside any parties it already has. Use this tool when: - A contracting party is missing from a document, e.g. the counterparty of a contract created from scratch - A signatory has to be added for a party the document does not have yet: create the party first, then add the signatory with create-document-signatory Pass party_account_party_uuid to add one of the account's saved parties (list-account-parties), usually the user's own company. A saved party can be on a document only once, and is always internal. For any other party, give party_entity_name, party_address and party_scope instead. Parties cannot be added while the document is archived, in the signing stage or an approved stage, going through an approval checkpoint, or bound by a preemptive signature.

  ConnectorOAuth

• create_api_keyA

  Algenta MCP ServerA

  Create a new API key for the current organization and return its raw_key value exactly once — it is never shown again, so store it immediately. expires_at optionally sets an ISO-8601 expiry and device_limit caps how many devices the key may register (validated against the plan ceiling, invalid_device_limit on excess). Key creation is rate-limited per organization (api_key_create_rate_limited). Use list_api_keys to see existing keys and revoke_api_key to retire one.

  ConnectorNo auth

• how-toA

  Fast.ioA

  Built-in product help — a natural-language "how do I…" question about Fastio returns a grounded, product-aware answer (or a short clarifying question) in one call. EXPLAIN-ONLY / ADVISORY: it returns GUIDANCE TEXT and performs NO platform action (it will not create shares, move files, or change anything); the actions themselves are on the other tools. Answers are grounded in Fastio's own how-to knowledge AND phrased in terms of these MCP tools — they name the concrete `<tool> action="…"` calls, in place of guessed endpoints or exploratory calls. Q&A over the user's uploaded files (RAG) is the `ai_manage` tool; `how-to` answers questions about Fastio ITSELF. Costs no credits; needs only an authenticated user (no org needed). action='describe' gives the full action/param reference.

  ConnectorNo auth

• searchA

  Costory: Your Finops MCPA

  Unified search across your entire Costory workspace — dimension values, events, alerts, dashboards (with their conditionsCel), dashboard templates, reports, virtual dimensions, and budgets. PRIMARY tool for discovering CEL field names: each dimensions result includes `dimension` (the exact CEL/groupBy name, e.g. cos_sub_account_id), `label`, and `topMatches`. Use type: ["dimensions"] to focus on dimensions only. An empty query (query: "") with type: ["dimensions"] returns every dimension with its top values — use this when you need the full field catalog before building filterCel. Keys that are not imported yet are invisible here — use list_dimension_candidates for those. With a keyword, results are filtered to matching values (e.g. query: "prod" finds production values across dimensions). Use this when a user mentions a product, team, project, or service name and you need to discover where it appears in the cost data before querying. Returns matching dimension values, related events, alerts, dashboards, dashboardTemplates, reports, virtualDimensions, budgets. Virtual dimension hits include id, name, bqName (immutable query field — set at create, never changes), status, and description. Each dashboard result carries a "conditionsCel" string — the dashboard's CEL filter (empty when none) — so before calling update_dashboard you can decide whether to set "extendDashboardConditions: true" on your new widget. Budget results include id (parent budget id for URLs) and name/year; call get with the budget id to obtain the budgetVersionId needed for query. IMPORTANT: Use short, concise search terms — e.g. if the user says 'my kubernetes dashboard', just search for 'kubernetes', not the full phrase. Optional "type" array restricts results to specific entity buckets (dashboards, reports, alerts, budgets, dimensions, virtual_dimensions, events). FOLLOW-UP: After calling search, use get to fetch full details for dashboards, budgets, reports, virtual dimensions, and cost alerts by ID. For dimension values, use "query" to query data grouped by or filtered on the matched dimensions. When the user wants to add to a dashboard, use the id from the dashboards bucket as input to update_dashboard. EXAMPLES: • "List all CEL dimensions" → { query: "", type: ["dimensions"] } • "Find account-related dimensions" → { query: "account", type: ["dimensions"] } • "Show me kubernetes costs" → { query: "kubernetes" } • "Find the data team dashboard" → { query: "data team" }

  ConnectorOAuth

• create_dashboardA

  Costory: Your Finops MCPA

  Create a dashboard with one or more widgets. New dashboards are creator-only (you get Admin). To share, call set_object_permissions after create — do not send PRIVATE/PUBLIC or teamId. Call get_skill with skillId: "dashboards" first — see skill for context-first workflow and inheritance rules. Put shared settings in `dashboardContext` (period required when chart widgets are present: prefer datePreset when possible, otherwise startDate/endDate; for a forecast chart use CURRENT_YEAR / CURRENT_QUARTER / CURRENT_MONTH — same Forecast group as Explore, not YTD; text-only dashboards may omit period; plus metricId, common groupBy, currency, optional conditionsCel). Chart widgets inherit by default and should only specify overrides. Cost may omit metricId, currency, and groupBy. Usage requires its own metricId (from suggest_usage_metrics, not a cost column) and has no currency; omit groupBy to inherit. Budget groupBy is explicit (the budget VD bqName) and does not inherit dashboardContext.groupBy. Both inherit conditionsCel. Hide formula inputs with visible: false. Do not repeat from/to or datePreset when they match dashboardContext. The legacy `context` alias is temporarily accepted but deprecated; never send both. Text widgets use `{ type: "text", title, textContent }` — no queries or period. Comparison widgets add compare: omit its from/to to compare against the preceding period automatically (preset-aware), and set compare.chartType to WATERFALL (default), TABLE, or KPI_BREAKDOWN. Widgets auto-pack into aligned grid rows; set per-widget `w`/`h` to override default sizing, or `x`/`y` together to pin a widget at an exact grid position. Optional `tags`: existing IDs from list_tags and/or `{ name, color? }` for new tags; color defaults to #6366F1; missing tags are created. Omit and `[]` both leave the dashboard untagged. Returns a URL — you MUST include it in your response. EXAMPLE: "AWS overview dashboard" → see skill dashboards Workflow A.

  ConnectorOAuth

• preview_virtual_dimension_draftA

  Costory: Your Finops MCPA

  Preview per-rule costs or a groupBy breakdown (read-only BigQuery). `virtualDimensionId` in inputs equals `id` from list/get/search. Operates on the latest **pending** draft if one exists (`draftPersisted: true`); otherwise previews published rules in memory **without creating a draft** (`draftPersisted: false` — not publishable). To publish changes after editing published-only state, call update_virtual_dimension_draft for an existing virtualDimensionId (or create_virtual_dimension_draft for a brand-new VDIM) — preview alone does not persist. Call after a successful create/update. Read the "summary" field first. Both modes share the same time window: optional `datePreset` (official presets — TRAILING_30_DAYS default, same enum as dashboards) or explicit `from`/`to` (YYYY-MM-DD, same shape as query); mutually exclusive. mode "costs": per-rule costs with totals.namedRulesSharePercent / totals.leftoverSharePercent, each rule's conditionCel and allocatesTo, plus howToRead. mode "breakdown": spend inside a target rule (ruleId or ruleIndex) split by groupBy — returns period (datePreset or from/to), scope.explanation, topValues[{ value, cost, percentOfScope }], and dailyTotals (not raw chart JSON). Discover valid `groupBy` values via search with `type: ["dimensions"]`. `position` (from get and preview costs output) and `ruleIndex` (preview/overlap input) refer to the same 0-based ordinal in the ordered rule list [...rules, leftover]. Prefer `ruleId` over `ruleIndex`. Target leftover via `ruleId` of `leftoverRule` or `ruleIndex: rules.length`. Optional `currency` (default USD) — pass the same value as query cost queries to align totals. costMetric selects the cost column (default cost); valid ids: cost, effective_cost, list_cost, contracted_cost (also accepts contracted_costs), unblended_cost, net_unblended_cost, amortized_cost, net_amortized_cost. EXAMPLES: • "Preview Environment VDIM draft costs" → { virtualDimensionId: "<virtualDimensionId from create/list>", mode: "costs" } • "What cos_region values sit inside Production?" → { virtualDimensionId: "<virtualDimensionId from create/list>", mode: "breakdown", ruleId: "<from get/preview costs>", groupBy: "cos_region", datePreset: "TRAILING_30_DAYS" } • "Preview costs in EUR to match earlier queries" → { virtualDimensionId: "<virtualDimensionId from create/list>", mode: "costs", currency: "EUR", from: "2025-01-01", to: "2025-03-31" }

  ConnectorOAuth

• create_alertmanager_silenceA

  AnkraB

  Create a silence in the cluster's Prometheus Alertmanager so matching alerts stop notifying (Slack, email, ...) until the silence ends. Matchers come from the alert's own labels - always anchor on an exact alertname matcher (e.g. alertname=KubeVersionMismatch) and add narrowing labels like cluster or namespace when known; at least one exact (non-regex) matcher is required. Duration accepts '30m', '2h', '24h', '14d', '2w' (default 2h, maximum 30d - longer suppressions need a human in Alertmanager/Grafana). A comment is required: it is the operator-visible reason shown next to the silence. The silence starts immediately (backdated one minute so it never sits pending) and the response carries the silence id - relay it so the silence can be expired early with expire_alertmanager_silence. The Alertmanager service is auto-discovered; pass namespace/service/port only for non-standard installs.

  ConnectorOAuth

• create-projectA

  MemocoreA

  Create a project — a shared space whose memories are visible to all members (you become its owner). First run search-projects and reuse a matching one — create only when none fits, to avoid duplicates. Give a clear `description` of what belongs in it: search-projects shows it and uses it to route future memories here. To create it INSIDE a company (corporate, shared with the whole team, not just you), pass `company_id` from search-companies; omit it for a personal project. Pass `type: "table"` (company projects only) for a TABLE: its memos are rows with typed `columns` — give every column a `description` of what it means, so agents fill it right. The type cannot change later. Returns the new project, including its id.

  ConnectorOAuth

• CreateApiKeyA

  GraphOS MCP ServerA

  Create an API key for an organization. The response contains the new key's value in token. It is a live credential, so give it to the user to store in a secret manager, and do not repeat it, log it, or pass it to another tool. Which key types you can create depends on how you authenticate. With the GraphOS sign-in (OAuth), you can create OPERATOR, SCIM, and GATEWAY keys. SUBGRAPH and VARIANT keys need a personal API key in the x-api-key header. With an operator key in x-api-key, you can create only GATEWAY keys, and a graph key can create none. No credential can create ROUTER keys. OPERATOR, SCIM, and GATEWAY keys also require the Org Admin role. GATEWAY keys are used by Apollo Gateway instances. Choose the narrowest type that does the job, and confirm the type and its resources with the user before you call this tool. Provide the organization ID, the key name, and the type. For a SUBGRAPH key, list each graphId, variantName, and subgraphName in resources.subgraphs. For a VARIANT key, list each graphId and variantName in resources.variants.

  ConnectorNo auth

• propose_create_invoice_paymentA

  More AI - ChatGPT & Claude MCP (Fortnox)B

  Create an invoice payment. Fortnox API POST /3/invoicepayments (https://api.fortnox.se/apidocs). Records in the bookkeeping a payment that has already been made; it does not move any money. Only prepares the change for the person to approve; this tool sends NOTHING to Fortnox, and the answer says how the approved change is sent. Body: {"InvoicePayment": {…}}; required: InvoiceNumber.

  ConnectorAPI key

• list_skillsA

  Costory: Your Finops MCPA

  List available Costory MCP workflow skills (skillId, name, description) from the remote skill catalog. Call this when you are unsure which skillId to load, then call get_skill with the chosen skillId. If already known (virtual-dimensions, dashboards, reports, query, recipes), you may skip this and call get_skill directly. EXAMPLE: "Which workflow guides can I load?" → {}

  ConnectorOAuth

• cogdepot_get_startedA

  cogDepotA

  Explains, in order, how to obtain a cogDepot API key and become able to trade. Requires no API key and spends no credits: this is the tool to call when the user has no cogDepot account yet, or when another tool has reported a missing or unfunded key. Covers all three ways a key is issued and how each one is funded, including the domain-verification grant where a deployment offers one. Returns instructions for a human or agent to follow. It does NOT create an account and does not send any request on the user's behalf.

  ConnectorNo auth

• how_to_startA

  HOTLIKESHOP MCPA

  Onboarding guide for NEW users: how to start buying on hotlikeshop through this MCP (create account -> get api_key -> top up -> search & buy). Read-only, no api_key required. WHEN TO USE: the very FIRST call for a new / international user, or whenever someone lacks an api_key or asks "how does this work". Lists which tools are free vs. which need an api_key. PREFER INSTEAD: topup_guide for deposit specifics, quote_order + buy_product to actually purchase, search_products to browse. Pass lang="en" (default) or lang="vi". Hướng dẫn bắt đầu cho người mới: tạo tài khoản -> lấy api_key -> nạp tiền -> tìm & mua.

  ConnectorNo auth

• count_mentionsA

  RedReplierA

  Count mentions matching the same filters as list_mentions, returning { total } and no rows. The same defaults apply: REJECTED excluded unless statuses includes it, and scores below the website's minimum (30 by default) hidden unless includeLowRelevance is true. Use it for dashboards, to size a triage batch, or to decide whether paging list_mentions is worthwhile; list_mentions already returns total with its rows, so skip this when you fetch rows anyway. Takes no sort, limit, or offset.

  ConnectorOAuth

• how_to_startA

  HOTLIKESHOPA

  Onboarding guide for NEW users: how to start buying on hotlikeshop through this MCP (create account -> get api_key -> top up -> search & buy). Read-only, no api_key required. WHEN TO USE: the very FIRST call for a new / international user, or whenever someone lacks an api_key or asks "how does this work". Lists which tools are free vs. which need an api_key. PREFER INSTEAD: topup_guide for deposit specifics, quote_order + buy_product to actually purchase, search_products to browse. Pass lang="en" (default) or lang="vi". Hướng dẫn bắt đầu cho người mới: tạo tài khoản -> lấy api_key -> nạp tiền -> tìm & mua.

  ConnectorNo auth

• set_primary_brandA

  CleoticA

  Create or edit the brand being tracked: its name, domain, and aliases. Pass at least one; what you leave out stays as it is. To add a competitor use save_competitor; to rename a brand or study, or pause it, use update_brand. A change to how answers name the brand re-reads existing answers automatically; it returns pending until that finishes. Free.

  ConnectorOAuth

• create-test-scenarioA

  TestChimpB

  Create a test scenario linked to a user story and allocate a real TS-<ordinalId>. Response includes content: canonical stub markdown already containing id: TS-<ordinalId> and story: US-<n>. BLOCKING workflow: call this FIRST → Write the returned content to the repo plans/scenarios path (edit body as needed but keep id: and story:) → call update-test-scenario with the full markdown. Never write scenario markdown that omits id. update-test-scenario rejects missing id/story with a clear error. platformFilePath must be under plans/scenarios/ and end with .md. userStoryOrdinalId is the numeric part of the parent US-<n> id. Optional agentTraceability records Activity inline (no separate report-agent-action for this create).

  ConnectorAPI key