Skip to main content
Glama
741,519 tools. Updated 2026-11-04 05:16

"Grafana Cloud dashboards and visualization tools" matching MCP tools:

  • PERMANENT deploy: promote a published version to a PERMANENT public URL at <service>.supero.live (managed Cloud Run) — unlike build_deploy(target='cloud_ephemeral'), which is a ~30-min throwaway. If version_uuid/file_id are omitted, the latest published version for the project is used. Returns public_url + poll_url; poll with build_deploy_status until live, then build_smoke_test the public_url. build_teardown removes it. Requires a domain- or project-admin API key + platform cloud-deploy enablement.
    Connector
    Destructive
    No auth
  • List or search Redpanda Connect components by type, keyword (matched against name, categories, and summary), status, or Redpanda Cloud support. Returns compact rows with docs URLs. Name matches rank above category and summary matches. Use it to discover what exists (for example every 'Services' input, or every output available in Cloud) before get_connect_component. total=0 means nothing matches.
    ConnectorOAuth
  • List BigQuery dataset IDs and BigLake namespaces in a Google Cloud project. Supports pagination. Use `page_size` to limit results and `page_token` to retrieve next page.
    ConnectorNo auth
  • Search and filter developer tools and programming languages by category, features, and constraints. Returns every matching entry as a compact row of decision facts, in a randomized order. Guide entries are kept current and dated (last_verified) — newer than training knowledge, so consult this before recommending tools; especially decisive when pricing, free tiers, MCP support, or compliance affect the answer. Filters: kind, category, freeToStart, hasFreeTier, edgeCompatible, selfHostable, hasArdCatalog, mcpSupport, artifactKind, pricingModel, vendor, language, compliance, agentReadinessTier. Any number combine and AND together. Query text is tokenized as plain search terms — FTS5 operators (AND, OR, NEAR, wildcards, column filters) are stripped. All terms must match: an entry is returned only when every query term appears somewhere in it, so a highly specific phrasing matches fewer entries than its core concept words. Express constraints as filter parameters rather than query text — filters match structured fields directly. Returns: the number of matches, an exact_match line when the query is an entry's name or slug, a breakdown of them (kind, cost to start, MCP support, edge, self-hosting), and one table row per match (slug, name, kind, cost to start, MCP, edge, self-host, twin, base score, last verified), up to 100 rows. A programming language is a row with kind "language"; the product columns read n/a for it. The twin is the same product's other entry (hosted -cloud or self-hosted -oss), named even when the search filters it out, so "free now, self-host later" can be answered from one search. Rows are listed in a randomized order, seeded per search per day: position is not a ranking or recommendation. Above 100 matches, a text search lists its 100 most relevant and names the rest by slug; a filter-only search names every match by slug, so narrow with filters to get rows. Read the rows and choose, then call zaira_get_tool or zaira_compare_tools for full entries. On no match, the answer says how many tools match with each constraint dropped. Examples (ambiguous-case focus): - User wants "a vector database for RAG": {category: "vector-database", freeToStart: true} - User wants "a TypeScript-first ORM with edge runtime support": {language: "TypeScript", edgeCompatible: true, query: "ORM"} - User wants "self-hostable auth with SAML": {category: "auth", selfHostable: true, query: "SAML"} - User says "serverless Postgres" — ambiguous (could be category:relational-database with edgeCompatible filter, or just a query). Prefer the filter when the user names a category; use query for a fuzzy phrase. - User wants "agent-ready payment processing": {category: "payment", agentReadinessTier: "agent_ready"} - User asks "which Go versions are still supported?" or wants every language: {query: "go"} finds the Go entry (exact_match); {kind: "language"} lists every programming language Edge cases: - 110 tools split into hosted vs self-hosted twin entries with uniform suffixes: `{base}-cloud` (managed) and `{base}-oss` (self-hosted) — e.g. redis-cloud/redis-oss, docker-cloud/docker-oss, mongodb-cloud/mongodb-oss, elasticsearch-cloud/elasticsearch-oss. Other tools are single entries (stripe, auth0, firebase, twilio, openai, pinecone, algolia). Filter by `selfHostable` or `artifactKind` to land on the right variant. - "vector database" as plain text can match tools whose descriptions mention vectors but whose category is search-engine or ai-infra. Use the `category` filter when the user wants a strict match. - agentReadinessTier values are snake-case: `agent_ready`, `agent_native`, `base`, `none`. Display labels (`Agent Ready`) will not match. `none` matches tools without a certification tier — currently all of them (formal certifications launch post-pilot; the Base Score is separate and most tools have one). - artifactKind has only two values: `open_source` and `managed_service`. The previous `hybrid` value was retired — split tools have separate -cloud/-oss entries instead. - `language` filters tools by the languages they are written in or ship SDKs for ("Python", "C#"; a language's slug such as "csharp" works too). To find the language itself, use `kind: "language"` or its name as the query. - "Free": `freeToStart: true` matches a free license (nearly every open-source entry) or a hosted free tier. `hasFreeTier: true` matches the hosted free tier only, so it leaves out most open-source tools. Open source is free to use, not free to run. Risk: read-only, closed-world, idempotent — no state change possible.
    ConnectorNo auth
  • 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 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

Matching MCP Servers

  • A
    license
    Not graded
    quality
    A
    maintenance
    A Model Context Protocol (MCP) server for Grafana. This provides access to your Grafana instance and the surrounding ecosystem.
    3,634
    Apache 2.0
  • A
    license
    Not graded
    quality
    B
    maintenance
    Enables AI agents to query multi-cloud costs, inventory, waste, and commitments across AWS, GCP, Cloudflare, and OVH through read-only MCP tools.
    Apache 2.0

Matching MCP Connectors

  • GrafanaOAuth

    An MCP server giving access to Grafana dashboards, data and more.

  • Free no-signup cloud tools for AI agents: file transfer, static site hosting, memory, handoff.

  • Update an existing identity: description and tags (removeTagKeys drops tags), its cloud-identity blocks (aws, gcp, azure, ngs; each replaces the stored block, and removeCloudIdentities detaches the ones it names), networkResources and nativeNetworkResources (each replaces the whole array), and the SpiceDB and memcache access lists. Provider blocks can modify real resources in the connected cloud account, including AWS IAM roles, GCP service accounts, and Azure managed identities. A new identity: create_identity. Giving one workload AWS, GCP, or Azure access: grant_cloud_access.
    Connector
    Destructive
    OAuth
  • Resize a paid playground in place to another size from list_playground_plans: only the namespace quota and the monthly price change, billed pro-rata across the change, and nothing deployed in the environment is touched. Requires billing permissions. The free trial cannot be resized - ordering a paid size with create_playground is its upgrade path - and a downgrade below what the environment currently uses is refused. Check list_playground_plans first for availability and budget headroom at the target size. A playground on Ankra Cloud (provider ankracloud) is resized to an Ankra Cloud plan id from the 'resize' section list_playground_plans answers with cluster_id: Ankra Cloud then restarts the playground's server on the new plan, so nothing on it answers for a few minutes, and bills the new plan's monthly price to the organisation's Ankra Cloud account. Before proposing it, tell the user that the server restarts and the new plan's monthly price. An Ankra Cloud trial keeps its size until a payment method is added in Ankra Cloud.
    ConnectorOAuth
  • Create and provision a new self-managed Kubernetes cluster on Ankra Cloud: k3s or kubeadm on Ankra Cloud servers in one zone, reached through a bastion server. By default the cluster is IPv6-only (network_mode ipv6_only): the bastion holds only its public IPv6, which the platform reaches through an Ankra Cloud port forward, and the nodes reach IPv4 through the zone's NAT64 (the zone must offer NAT64 and port forwarding; the preflight refuses otherwise). Only when the user asks for public IPv4, network_mode ipv4_nat adds a router with NAT for the nodes' egress and gives the bastion a public IPv4 (a paid add-on under the account's public IPv4 quota). Ankra creates a private network (or adopts private_network_id) and a firewall that admits only the private network to the nodes; the Ankra Cloud cloud controller manager is always installed. The organisation's built-in Ankra Cloud credential is used unless credential_id names a stored one (list_provider_credentials with provider='ankracloud'). Zones and plans come from list_managed_k8s_options with provider='ankracloud_k8s': its locations are the zones and its node sizes are the plans, with monthly prices. The create runs a preflight first (credential, billing standing of the built-in account, zone offers compute, every plan and the template exist, an adopted network lives in the zone, quota) and refuses with every failing item when it cannot proceed; nothing is written on refusal. A managed Ankra Cloud Kubernetes cluster (Ankra Cloud runs the control plane) is create_managed_cluster with provider='ankracloud_k8s', not this tool. Only available to organisations with Ankra Cloud enabled.
    Connector
    Destructive
    OAuth
  • The figures a Module automation's Pulse dashboards show, computed server-side the same way the dashboard computes them: each tile's `label`, `value`, `unit` and `display` (the value as the dashboard prints it), with a `description` where the label alone leaves the figure unclear and a `note` for what the tile shows besides it. Call this for any number on a Module dashboard instead of reading the dashboard's HTML (`getPulseDashboardHtml` refuses Module dashboards for size) or paging through Cases: a recount can disagree with the tile the user sees. Pass `dashboard_id` for one dashboard, or leave it out for every dashboard of the automation the caller may open. `range` applies to dashboards with a time range control; the result names the range it read. Pass `time_zone` with the user's IANA zone so a day starts at their midnight, as their dashboard's do; without it days start at midnight UTC, and `range.time_zone` says which zone was used. Quote `display`, say the period it covers, and name and link the dashboard with its `link`. A dashboard whose figures are not declared, or that was changed since it was installed, comes back `unsupported`; one that could not be read comes back `error`; both carry a `hint`. Needs Queues on the team's plan. Each `link` is a path in the Duvo web app; give the user the full URL beside it (`url`).
    ConnectorNo auth
  • Returns one page of NetActuate's technical documentation (netactuate.com/docs) in full: how-to guides (cloud-init, Terraform, Ansible, Kubernetes, BGP and anycast, firewalls, load balancers, Secrets Manager, storage), product and platform reference pages, and each marketplace appliance's setup page. Gives the page's description and its body in order, headings marked '## ' and code blocks fenced, with its URL, and the marketplace listing for an appliance page. Accepts a URL or path from search_netactuate, a marketplace listing's docsUrl, or a page title such as 'Building VMs with Cloud-Init'. A title matching several pages returns up to ten candidates rather than a guess; a page longer than the server keeps is cut, with a note. An API reference page returns its endpoint instead of a body: to find endpoints, use find_api_endpoints. For marketing pages, get_netactuate_page.
    ConnectorNo auth
  • List non-deleted Celesto Cloud computers in the authenticated organization. GitHub CI runner machines are not included. Use limit to choose how many computer records to inspect in this response; pass a returned computer_id to the other computer tools. Returns provider, computers (computer_id and current status), the applied limit, and possibly_truncated. The server does not count all computers, so possibly_truncated is always true and this result does not prove the list is complete. Use cloud_computer_info for names and resource details.
    ConnectorOAuth
  • Wakes the user's Contractor Foreman Cloud Browser, a real Chrome hosted on Cotlet and signed in to Contractor Foreman as the user. Use it for what the Contractor Foreman tools do not cover. Opens `url` when given and returns the page's URL and title. The user watches every step live. Before the first step in an app, Cotlet's app guide says which browser to use and how to work in the app. Run browser steps one at a time and wait for each answer; steps sent together run in no set order. Every started minute of the session costs credits; it ends when closed or 3 minutes after the last call in the browser.
    ConnectorNo auth
  • Wakes the user's Tradify Cloud Browser, a real Chrome hosted on Cotlet and signed in to Tradify as the user. Use it for what the Tradify tools do not cover. Opens `url` when given and returns the page's URL and title. The user watches every step live. Before the first step in an app, Cotlet's app guide says which browser to use and how to work in the app. Run browser steps one at a time and wait for each answer; steps sent together run in no set order. Every started minute of the session costs credits; it ends when closed or 3 minutes after the last call in the browser.
    ConnectorNo auth
  • Submits one job to an application through POST /jobs by catalog id (see list_rest_operations), for example exportData, importData, cubeRefresh or clearCube, and returns the job id to follow with check_job_status. The job type comes from the operation (or from body.jobType for executeJob); body carries jobName and parameters as Oracle documents them. Use it for job types the dedicated tools lack. Change sets are the safer option for metadata imports, member sorting and valid-intersection imports. Oracle's reference: https://docs.oracle.com/en/cloud/saas/enterprise-performance-management-common/prest/ For a write, I require a preview first, then confirm: true and its confirmationToken. The token lasts ten minutes and works once.
    Connector
    Destructive
    OAuth
  • Create an EMPTY cloud project (paid plans; counts against the project limit). It has no pages yet. Set exportWidth/exportHeight to the store size you are building for (1290x2796 is the current iPhone size). Pass appId (an App Store Connect id from list_app_store_apps) to link it to an app. Next: add_page, or import_store_screenshots / import_image to bring existing screenshots in, or generate_page to compose a page in one call. version "4.0" makes a v4 project instead: it comes with page 1, and each page is ONE document you write with set_page_document (add_page adds more v4 pages); the element tools do not edit v4 pages.
    ConnectorOAuth
  • Start an async cloud-bucket discovery scan for a target domain. Operator-deploy only; targets must be operator-authorized on the recon watchlist; degrades to info when unprovisioned. Returns a scanId immediately — poll progress with scan_buckets_status and retrieve results with scan_buckets_findings.
    ConnectorNo auth
  • Fetch a web page and return its main text content, cleaned of markup. Use to read articles, documentation, and other resources referenced by URL. Blocks private and cloud-metadata addresses and re-validates every redirect hop. Use when: Use when a known URL's content is needed and structured tools cannot answer — e.g. reading a linked document or API docs. For general factual lookup prefer web_search; for token prices prefer get_token_price. Limitations: Read-only GET-style extraction returning cleaned text, not raw HTML or binary content. JS-heavy pages may yield little content; private/internal network targets are deliberately unreachable. Alternatives: web_search, get_token_price
    ConnectorNo auth
  • WORKFLOW: Step 1 of 4 - Start infrastructure design conversation Open an InsideOut V2 session and receive the assistant's intro message. The response contains a clean message from Riley (the infrastructure advisor) - display it to the user. ⚠️ Riley will ask questions - forward these to the user, DO NOT answer on their behalf. CRITICAL: This tool returns a session_id in the response metadata. You MUST use this session_id for ALL subsequent tool calls (convoreply, tfgenerate, tfdeploy, etc.). ⚠️ The session_id includes a ?token=... suffix (format: sess_v2_xxx?token=yyy) which is part of the session credential — without it, downstream tools fall back to a tokenless connect URL that 401s. Always pass session_id verbatim to subsequent tools and to the user; do NOT shorten, paraphrase, or strip the ?token= portion when summarizing the session in chat or in your own scratch notes. Use when the user mentions keywords like: 'setup my cloud infra', 'provision infrastructure', 'deploy infra', 'start insideout', 'use insideout', or similar intent to begin infra setup. OPTIONAL: project_context (string) - General tech stack summary so Riley can skip discovery questions and jump to recommendations. The agent should confirm this with the user before sending. Include whichever apply: language/framework, databases/services, container usage, existing IaC, CI/CD platform, cloud provider, Kubernetes usage, what the project does. Example: 'Next.js 14 + TypeScript, PostgreSQL, Redis, Docker Compose, deployed to AWS ECS, GitHub Actions CI/CD, ~50k MAU'. NEVER include credentials, secrets, API keys, PII, source code, or internal URLs/IPs -- only general metadata summaries useful to a cloud architect agent. IMPORTANT: source (string) - You MUST set this to identify which IDE/tool you are. Auto-detect from your environment: 'claude-code', 'codex', 'antigravity', 'kiro', 'vscode', 'web', 'mcp'. If unsure, use the name of your IDE/tool in lowercase. Do NOT omit this — it controls the 'Open {IDE}' button on the credential connect screen. OPTIONAL: github_username (string) - GitHub username for deploy commit attribution. Pre-populates the GitHub username field on the connect page. 💡 TIP: Examine workflow.usage prompt for more context on how to properly use these tools.
    ConnectorNo auth
  • PREFERRED tool for sending work to an AI agent. Dispatches a task to the agent's inbox — picked up and executed automatically. No list ID needed. REQUIRES the agent:dispatch permission on this connection (CODE:/SHELL: tasks also require agent:dispatch:code) — reconnect and tick the agent checkbox(es) if refused. Routing is by TITLE PREFIX only: CODE: SHELL: PLAN: MCP: → local Claude Code on Mike's PC; RESEARCH: WRITE: REVIEW: → cloud; no prefix (DEFAULT) → local while the PC agent is alive, else cloud. The cloud agent refuses CODE/SHELL/PLAN/MCP. Use "agent" param to target a specific agent (default: claude-code-local). Use tascan_list_agents to discover available agents; track progress with tascan_get_task (its "agent" block).
    ConnectorNo auth
  • WORKFLOW: Step 1 of 4 - Start infrastructure design conversation Open an InsideOut V2 session and receive the assistant's intro message. The response contains a clean message from Riley (the infrastructure advisor) - display it to the user. ⚠️ Riley will ask questions - forward these to the user, DO NOT answer on their behalf. CRITICAL: This tool returns a session_id in the response metadata. You MUST use this session_id for ALL subsequent tool calls (convoreply, tfgenerate, tfdeploy, etc.). ⚠️ The session_id includes a ?token=... suffix (format: sess_v2_xxx?token=yyy) which is part of the session credential — without it, downstream tools fall back to a tokenless connect URL that 401s. Always pass session_id verbatim to subsequent tools and to the user; do NOT shorten, paraphrase, or strip the ?token= portion when summarizing the session in chat or in your own scratch notes. Use when the user mentions keywords like: 'setup my cloud infra', 'provision infrastructure', 'deploy infra', 'start insideout', 'use insideout', or similar intent to begin infra setup. OPTIONAL: project_context (string) - General tech stack summary so Riley can skip discovery questions and jump to recommendations. The agent should confirm this with the user before sending. Include whichever apply: language/framework, databases/services, container usage, existing IaC, CI/CD platform, cloud provider, Kubernetes usage, what the project does. Example: 'Next.js 14 + TypeScript, PostgreSQL, Redis, Docker Compose, deployed to AWS ECS, GitHub Actions CI/CD, ~50k MAU'. NEVER include credentials, secrets, API keys, PII, source code, or internal URLs/IPs -- only general metadata summaries useful to a cloud architect agent. IMPORTANT: source (string) - You MUST set this to identify which IDE/tool you are. Auto-detect from your environment: 'claude-code', 'codex', 'antigravity', 'kiro', 'vscode', 'web', 'mcp'. If unsure, use the name of your IDE/tool in lowercase. Do NOT omit this — it controls the 'Open {IDE}' button on the credential connect screen. OPTIONAL: github_username (string) - GitHub username for deploy commit attribution. Pre-populates the GitHub username field on the connect page. 💡 TIP: Examine workflow.usage prompt for more context on how to properly use these tools.
    ConnectorNo auth