com.mcparmory/grafana
OCI · GHCR.IO/MCPARMORY/GRAFANA:1.0.3 · 2 COMPONENTS · SCANNED SEP 20
Manage dashboards, users, teams, alerts, data sources, and access control
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security0
- Malware scan not yet available for this package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
Provenance & Transparency32
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 130 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 20635 tokens (~94/item across 218 items; 218 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety97
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 37 of 42 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "query_metrics" implies "execute" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Partial
- An AI judge read all 218 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
How do I install the com.mcparmory/grafana MCP server?
com.mcparmory/grafana runs locally as a container image, launched with docker run --rm -i ghcr.io/mcparmory/grafana:1.0.3. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/mcparmory/grafana:1.0.3
claude mcp add com-mcparmory-grafana -- docker run --rm -i ghcr.io/mcparmory/grafana:1.0.3
{
"mcpServers": {
"com-mcparmory-grafana": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/grafana:1.0.3"
]
}
}
} {
"servers": {
"com-mcparmory-grafana": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/grafana:1.0.3"
]
}
}
} codex mcp add com-mcparmory-grafana -- docker run --rm -i ghcr.io/mcparmory/grafana:1.0.3
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-mcparmory-grafana": {
"type": "local",
"command": [
"docker",
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/grafana:1.0.3"
],
"enabled": true
}
}
} mcp_servers:
com-mcparmory-grafana:
command: "docker"
args: ["run", "--rm", "-i", "ghcr.io/mcparmory/grafana:1.0.3"] {
"McpServers": {
"com-mcparmory-grafana": {
"Transport": "stdio",
"Command": "docker",
"Arguments": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/grafana:1.0.3"
]
}
}
} {
"mcpServers": {
"com-mcparmory-grafana": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/grafana:1.0.3"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 −2
- Stability: pass → 0.80 functional
- 19 Sept 26 0
- Stability: 0.97 → pass security
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 −3
- Stability: pass → 0.77 functional
- 11 Sept 26 0
- Stability: 0.97 → pass security
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed oci/ghcr.io/mcparmory/grafana:1.0.3
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
add_group_to_team Add Group to Team ~69
Add an external group to a team, enabling group-level access and collaboration within the team.
| Name | Type | Req | Description |
|---|---|---|---|
| groupId | string | – | The unique identifier of the external group to add to the team. |
| teamId | string | yes | The unique identifier of the team to which the group will be added. |
No output schema declared.
No examples provided.
add_organization_user Add Organization User ~140
Add an existing global user to the current organization with an optional role assignment. Requires the `org.users:add` permission with `users:*` scope in Grafana Enterprise with Fine-grained access control enabled.
| Name | Type | Req | Description |
|---|---|---|---|
| loginOrEmail | string | – | The login username or email address of the global user to add to the organization. |
| org_id | string | yes | The unique identifier of the organization to which the user will be added. Must be a positive integer. |
| role | string | – | The role to assign to the user within the organization. Valid options are: None, Viewer, Editor, or Admin. If not specified, defaults to None. |
No output schema declared.
No examples provided.
add_team_member Add Team Member ~81
Add a user to a team by their user ID. The user will gain access to the team's resources and collaboration features.
| Name | Type | Req | Description |
|---|---|---|---|
| team_id | string | yes | The unique identifier of the team to which the member will be added. |
| userId | string | yes | The unique identifier of the user to add to the team, specified as a 64-bit integer. |
No output schema declared.
No examples provided.
add_user_to_organization Add User to Organization ~106
Adds an existing global user to the current organization with a specified role. Requires the `org.users:add` permission with `users:*` scope in Grafana Enterprise with Fine-grained access control enabled.
| Name | Type | Req | Description |
|---|---|---|---|
| loginOrEmail | string | – | The login username or email address of the global user to add to the organization. |
| role | string | – | The role to assign to the user within the organization. Must be one of: None, Viewer, Editor, or Admin. |
No output schema declared.
No examples provided.
assign_resource_permissions Assign Resource Permissions ~139
Assign or update permissions for a resource (datasource, team, dashboard, folder, or service account) by specifying the resource type and ID along with the desired permission assignments.
| Name | Type | Req | Description |
|---|---|---|---|
| permissions | array | – | An array of permission assignment objects that define who has access and what actions they can perform. Refer to the resource description endpoint to see valid permission types for the specified reso… |
| resource | string | yes | The type of resource to assign permissions for. Must be one of: datasources, teams, dashboards, folders, or serviceaccounts. |
| resourceID | string | yes | The unique identifier of the specific resource instance for which permissions are being assigned. |
No output schema declared.
No examples provided.
assign_team_role Assign Team Role ~87
Assign a role to a team. Requires permission to delegate team roles within your organization.
| Name | Type | Req | Description |
|---|---|---|---|
| roleUid | string | – | The unique identifier of the role to assign to the team. Identifies which role permissions and capabilities the team will receive. |
| teamId | string | yes | The unique identifier of the team to which the role will be assigned. Must be a valid 64-bit integer. |
No output schema declared.
No examples provided.
cancel_snapshot Cancel Snapshot ~71
Cancel an in-progress snapshot within a cloud migration session. This operation will halt the snapshot processing at any stage of its execution pipeline.
| Name | Type | Req | Description |
|---|---|---|---|
| snapshotUid | string | yes | The unique identifier of the snapshot to cancel. |
| uid | string | yes | The unique identifier of the cloud migration session containing the snapshot to be cancelled. |
No output schema declared.
No examples provided.
check_datasource_health Check Datasource Health ~71
Performs a health check on a plugin datasource to verify its connectivity and operational status. Returns the health status of the datasource identified by the provided UID.
| Name | Type | Req | Description |
|---|---|---|---|
| uid | string | yes | The unique identifier of the datasource to check. This UID is used to locate and verify the health status of the specific plugin datasource. |
No output schema declared.
No examples provided.
clear_help_flags Clear Help Flags ~31
Clear all help flags for the current user. This resets any tutorial or onboarding prompts that may have been dismissed.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
configure_datasource_cache Configure Data Source Cache ~261
Configure caching behavior for a specific data source, including TTL settings for queries and resources. Use this to optimize performance by controlling how long cached data persists.
| Name | Type | Req | Description |
|---|---|---|---|
| dataSourceID | string | – | The numeric identifier of the data source. Used as an alternative or supplementary identifier for the data source. |
| dataSourceType | string | – | The type of data source (e.g., Prometheus, Graphite, InfluxDB). Used to identify the data source category. |
| dataSourceUID | string | yes | The unique identifier of the data source to configure caching for. |
| enabled | boolean | – | Enable or disable caching for this data source. When disabled, cached data will not be used or stored. |
| ttlQueriesMs | string | – | Time-to-live for cached queries in milliseconds. Specifies how long query results remain in the cache before expiration. Only used if UseDefaultTTL is disabled. |
| ttlResourcesMs | string | – | Time-to-live for cached resources in milliseconds. Specifies how long resource data remains in the cache before expiration. Only used if UseDefaultTTL is disabled. |
| useDefaultTTL | boolean | – | When enabled, ignores the TTLQueriesMs and TTLResourcesMs values and uses the default TTL settings from the Grafana configuration file instead. |
No output schema declared.
No examples provided.
convert_prometheus_rule_group Convert Prometheus Rule Group ~395
Converts a Prometheus rule group into a Grafana-compatible rule group and creates or updates it within the specified namespace. Existing groups that were not originally imported from a Prometheus source will not be replaced and will return an error.
| Name | Type | Req | Description |
|---|---|---|---|
| NamespaceTitle | string | yes | The name of the namespace where the rule group will be created or updated. |
| interval | string | – | The evaluation interval for the rule group, specified in nanoseconds as a 64-bit integer. Represents the elapsed time between rule evaluations. |
| labels | object | – | Custom labels to attach to all rules in the group, specified as key-value pairs. |
| limit | string | – | Maximum number of rules to process from the Prometheus rule group, specified as a 64-bit integer. |
| query_offset | string | – | Time offset for query evaluation, specified as a duration string (e.g., ISO 8601 format). |
| rules | array | – | Array of Prometheus rules to convert. Each rule is converted to Grafana's rule format and included in the group. |
| x-grafana-alerting-alert-rules-paused | boolean | – | Whether to pause all alert rules in the converted rule group. |
| x-grafana-alerting-datasource-uid | string | – | The unique identifier of the Grafana datasource to use for alerting rules. |
| x-grafana-alerting-folder-uid | string | – | The unique identifier of the Grafana folder where the rule group will be stored. |
| x-grafana-alerting-notification-settings | string | – | Configuration for notification settings applied to the rule group, specified as a JSON string. |
| x-grafana-alerting-recording-rules-paused | boolean | – | Whether to pause all recording rules in the converted rule group. |
| x-grafana-alerting-target-datasource-uid | string | – | The unique identifier of the target datasource for rule evaluation. |
No output schema declared.
No examples provided.
convert_prometheus_rule_group_config Convert Prometheus Rule Group Config ~393
Converts a Prometheus rule group into a Grafana-compatible rule group and creates or updates it in the specified namespace. Existing groups that were not originally imported from Prometheus sources will not be replaced and will return an error.
| Name | Type | Req | Description |
|---|---|---|---|
| NamespaceTitle | string | yes | The title of the namespace where the rule group will be created or updated. |
| interval | string | – | The evaluation interval for the rule group, specified in nanoseconds as a 64-bit integer. Represents the elapsed time between rule evaluations. |
| labels | object | – | Custom labels to attach to all rules in the group as key-value pairs. |
| limit | string | – | Maximum number of rules to process from the Prometheus rule group, specified as a 64-bit integer. |
| query_offset | string | – | Time offset for query evaluation, specified as a duration string (e.g., ISO 8601 format). |
| rules | array | – | Array of Prometheus rules to convert. Each rule is converted to Grafana's rule format and included in the group. |
| x-grafana-alerting-alert-rules-paused | boolean | – | Whether to pause all alert rules in the converted rule group. |
| x-grafana-alerting-datasource-uid | string | – | The unique identifier of the Grafana datasource to use for alerting rules. |
| x-grafana-alerting-folder-uid | string | – | The unique identifier of the Grafana folder where the rule group will be stored. |
| x-grafana-alerting-notification-settings | string | – | Configuration for notification settings applied to the rule group, specified as a JSON string. |
| x-grafana-alerting-recording-rules-paused | boolean | – | Whether to pause all recording rules in the converted rule group. |
| x-grafana-alerting-target-datasource-uid | string | – | The unique identifier of the target datasource for rule evaluation. |
No output schema declared.
No examples provided.
convert_prometheus_rules Convert Prometheus Rules ~31
Converts Prometheus rule groups into Grafana-Managed Rules format, enabling centralized rule management within Grafana.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
convert_prometheus_rules_to_grafana Convert Prometheus Rules to Grafana ~38
Converts Prometheus or Cortex rule groups into Grafana-Managed Rules format for use within Grafana's alerting system.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
create_annotation Create Annotation ~226
Creates an annotation in Grafana that can be scoped to a specific dashboard and panel, or created as an organization-wide annotation. For region annotations spanning a time period, include both time and timeEnd properties.
| Name | Type | Req | Description |
|---|---|---|---|
| dashboardUID | string | – | The unique identifier of the dashboard where this annotation will be created. If omitted, the annotation is created at the organization level and can be queried from any dashboard using the Grafana a… |
| tags | array | – | An array of tag strings to categorize and organize the annotation for easier filtering and discovery. |
| text | string | yes | The annotation text content that will be displayed. This is the primary descriptive information for the annotation. |
| time | string | – | The start time of the annotation as an epoch timestamp in millisecond resolution. Required for all annotations; use timeEnd to create a region annotation spanning a time period. |
| timeEnd | string | – | The end time for a region annotation as an epoch timestamp in millisecond resolution. When specified, creates a region annotation spanning from time to timeEnd instead of a point-in-time annotation. |
No output schema declared.
No examples provided.
create_contact_point Create Contact Point ~198
Create a new contact point for alert notifications. Specify the contact point type and configure its settings to enable routing of alerts to external services.
| Name | Type | Req | Description |
|---|---|---|---|
| disableResolveMessage | boolean | – | Whether to disable the resolve message when alerts are resolved. Defaults to false, meaning resolve messages are sent. |
| name | string | – | Name is used as grouping key in the UI. Contact points with the same name will be grouped in the UI. |
| settings | object | yes | Configuration settings for the contact point. The structure and required fields depend on the selected type (e.g., webhook URL, email address, API credentials). |
| type | string | yes | The type of contact point to create. Choose from supported integrations including alertmanager, dingding, discord, email, googlechat, kafka, line, opsgenie, pagerduty, pushover, sensugo, slack, teams… |
No output schema declared.
No examples provided.
create_correlation Create Correlation ~206
Create a correlation link between two data sources, enabling navigation from a field in the source to related data in a target source or query.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Optional human-readable description of the correlation's purpose (e.g., 'Logs to Traces'). |
| field | string | yes | The field name in the source data that will serve as the attachment point for the correlation link (e.g., 'message'). |
| label | string | – | Optional label to identify and organize the correlation within the data source. |
| sourceUID | string | yes | The unique identifier of the source data source where the correlation will be attached. |
| target | object | yes | The target data query definition as a key-value object that specifies what data to correlate to. |
| targetUID | string | – | The unique identifier of the target data source for the correlation. Required when the correlation type is a query. |
| transformations | array | – | Optional array of transformations to apply to the correlation data before display or processing. |
No output schema declared.
No examples provided.
create_datasource Create Data Source ~259
Create a new data source in Grafana. Sensitive credentials like passwords are automatically encrypted and stored securely in the database. Requires `datasources:create` permission in Grafana Enterprise with Fine-grained access control enabled.
| Name | Type | Req | Description |
|---|---|---|---|
| access | string | – | Access mode for the data source, determining how Grafana communicates with it (e.g., direct browser access or server-side proxy). |
| database | string | – | Database name or identifier for the data source connection. |
| isDefault | boolean | – | Whether this data source should be the default for new panels and queries. |
| jsonData | object | – | Additional JSON configuration specific to the data source type, such as timeout settings, SSL options, or type-specific parameters. |
| secureJsonData | object | – | Sensitive credentials stored as encrypted JSON, such as `password` and `basicAuthPassword`. These fields are encrypted at rest and returned as `secureJsonFields` in the response. |
| url | string | – | Connection URL or endpoint for the data source (e.g., database host, API endpoint). |
| user | string | – | Username for authenticating with the data source. |
| withCredentials | boolean | – | Whether to send credentials (cookies, authorization headers) with cross-origin requests to the data source. |
No output schema declared.
No examples provided.
create_graphite_annotation Create Graphite Annotation ~128
Creates an annotation using Graphite-compatible event format. The annotation timestamp defaults to the current time if not specified, and tags can use either modern or pre-0.10.0 Graphite formats.
| Name | Type | Req | Description |
|---|---|---|---|
| tags | – | – | Space-separated list of tags to associate with the annotation. Supports both modern and legacy Graphite tag formats (pre-0.10.0). |
| what | string | – | Human-readable description or title of the annotation event. |
| when | string | – | Unix timestamp (in seconds) indicating when the annotation occurred. If omitted, the current server time will be used. |
No output schema declared.
No examples provided.
create_library_element Create Library Element ~110
Creates a new library element that can be reused across dashboards and other resources. Optionally specify a folder location and provide the element configuration as a JSON model.
| Name | Type | Req | Description |
|---|---|---|---|
| folderUid | string | – | The unique identifier of the folder where this library element will be stored. If not provided, the element will be created in the default location. |
| model | object | – | The JSON configuration object defining the library element's properties, type, and settings. This object structure depends on the type of library element being created. |
No output schema declared.
No examples provided.
create_license_token Create License Token ~59
Generate a new license token for the specified instance. Requires licensing:write permission to perform this operation.
| Name | Type | Req | Description |
|---|---|---|---|
| instance | string | – | The instance identifier for which to create the license token. If not specified, the token is created for the default instance. |
No output schema declared.
No examples provided.
create_migration_session Create Migration Session ~38
Initiate a new cloud migration session to begin the migration process. This creates a session that can be used to manage and track migration activities.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
create_migration_snapshot Create Migration Snapshot ~78
Initiates the creation of an instance snapshot for a cloud migration session. Returns the snapshot UID upon successful initialization.
| Name | Type | Req | Description |
|---|---|---|---|
| resourceTypes | array | – | Optional list of resource types to include in the snapshot. Specifies which resource categories should be captured. |
| uid | string | yes | The unique identifier of the migration session for which to create a snapshot. |
No output schema declared.
No examples provided.
create_organization Create Organization ~35
Create a new organization in Grafana. This operation requires the allow_org_create configuration setting to be enabled by your Grafana administrator.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
create_public_dashboard Create Public Dashboard ~123
Create a public dashboard link for an existing dashboard, enabling external sharing with configurable access controls and features.
| Name | Type | Req | Description |
|---|---|---|---|
| annotationsEnabled | boolean | – | Enable or disable annotations visibility in the public dashboard. |
| dashboardUid | string | yes | The unique identifier of the dashboard to make public. |
| isEnabled | boolean | – | Enable or disable the public dashboard link. |
| share | string | – | Access level or sharing mode for the public dashboard (e.g., view-only, edit permissions). |
| timeSelectionEnabled | boolean | – | Enable or disable time range selection controls in the public dashboard. |
No output schema declared.
No examples provided.
create_recording_rule Create Recording Rule ~234
Create and register a new recording rule that automatically starts collecting metrics according to the specified query and interval configuration.
| Name | Type | Req | Description |
|---|---|---|---|
| active | boolean | – | Whether the recording rule is enabled and actively collecting metrics upon creation. |
| count | boolean | – | Whether to return the count of matching time series instead of the series data itself. |
| description | string | – | A human-readable description of the recording rule's purpose and behavior. |
| dest_data_source_uid | string | – | The unique identifier of the destination data source where recorded metrics will be stored. |
| interval | string | – | The evaluation interval in milliseconds at which the recording rule queries will be executed. |
| prom_name | string | – | The name to assign to the recorded metric in the Prometheus data source. |
| queries | array | – | An array of metric queries to execute for this recording rule. Order matters and determines query execution sequence. |
| range | string | – | The time range in milliseconds over which each query will look back when evaluating the recording rule. |
| target_ref_id | string | – | The reference identifier of the target query within the queries array that produces the final recorded metric. |
No output schema declared.
No examples provided.
create_remote_write_target Create Remote Write Target ~87
Create a remote write target for Prometheus recording rules. Requires an existing Prometheus data source to be configured, otherwise returns a 422 error.
| Name | Type | Req | Description |
|---|---|---|---|
| data_source_uid | string | – | The unique identifier of the Prometheus data source to associate with this remote write target. |
| remote_write_path | string | – | The endpoint path where Prometheus will send remote write requests for this target. |
No output schema declared.
No examples provided.
create_report Create Report ~558
Create a scheduled or on-demand report with customizable formatting, delivery options, and distribution settings. Requires organization admin privileges and a valid license with the `reports.admin:create` permission.
| Name | Type | Req | Description |
|---|---|---|---|
| dashboards | array | – | Array of dashboard IDs to include in the report. Dashboards will be rendered in the order specified. |
| dayOfMonth | string | – | Day of the month for monthly recurring reports (1-31). Only applicable when frequency is set to monthly. |
| enableCsv | boolean | – | Enable CSV export format for the report output. |
| enableDashboardUrl | boolean | – | Include direct URLs to dashboards in the report for easy navigation. |
| endDate | string | – | End date for the report schedule in ISO 8601 format. Report will stop being generated after this date. |
| formats | array | – | Array of output formats for the report (e.g., PDF, PNG, CSV). Specifies which file formats to generate. |
| frequency | string | – | Frequency of report generation (e.g., once, daily, weekly, monthly, yearly). |
| intervalAmount | string | – | Number of intervals between report generations. Used with intervalFrequency to define custom schedules. |
| intervalFrequency | string | – | Time unit for the interval (e.g., hours, days, weeks, months). Defines the period between recurring reports. |
| layout | string | – | Page layout for PDF rendering (e.g., portrait, landscape, grid). |
| message | string | – | Custom message to include in the report body or email delivery. |
| orientation | string | – | Page orientation for PDF output (portrait or landscape). |
| pdfCombineOneFile | boolean | – | Combine all PDF pages into a single file instead of separate files per dashboard. |
| pdfShowTemplateVariables | boolean | – | Include template variable definitions and values in the PDF output for reference. |
| recipients | string | – | Comma-separated list of email addresses to receive the report. |
| replyTo | string | – | Reply-to email address for report delivery notifications. |
| scaleFactor | string | – | Scale factor for rendering dashboard content in the report. Specified as an integer representing the scaling percentage. |
| startDate | string | – | Start date for the report schedule in ISO 8601 format. Report generation begins on this date. |
| state | string | – | Current state of the report (e.g., draft, active, paused, archived). Controls whether the report is actively generated. |
| subject | string | – | Subject line for report email delivery. |
| timeZone | string | – | Time zone for scheduling report generation and delivery (e.g., UTC, America/New_York). Affects when scheduled reports run. |
| workdaysOnly | boolean | – | Generate reports only on business days, excluding weekends and holidays. |
No output schema declared.
No examples provided.
create_service_account Create Service Account ~99
Create a new service account in Grafana for programmatic access. Requires Grafana Admin privileges and basic authentication.
| Name | Type | Req | Description |
|---|---|---|---|
| isDisabled | boolean | – | Whether the service account should be created in a disabled state. Defaults to false (enabled). |
| name | string | – | – |
| role | string | – | The role to assign to the service account. Must be one of: None, Viewer, Editor, or Admin. Defaults to None if not specified. |
No output schema declared.
No examples provided.
create_service_account_token Create Service Account Token ~103
Generate a new authentication token for a service account. The token can be configured with an optional expiration time in seconds.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | – |
| secondsToLive | string | – | Optional token lifetime in seconds. If specified, the token will automatically expire after this duration. If omitted, the token will not expire. |
| serviceAccountId | string | yes | The unique identifier of the service account for which to create the token. Must be a positive integer. |
No output schema declared.
No examples provided.
create_snapshot Create Dashboard Snapshot ~176
Create a snapshot of a dashboard for sharing or archival. Requires either public snapshot mode to be enabled or valid authentication credentials.
| Name | Type | Req | Description |
|---|---|---|---|
| dashboard | object | yes | The complete dashboard model object to snapshot. |
| deleteKey | string | – | A unique key that grants deletion permissions for this snapshot. Required when storing the snapshot externally. Only the snapshot creator should have access to this key. |
| expires | string | – | The number of seconds before the snapshot automatically expires and becomes unavailable. Omit or set to 0 to keep the snapshot indefinitely. |
| external | boolean | – | When enabled, stores the snapshot on an external server instead of locally. Requires both `key` and `deleteKey` to be provided. |
| key | string | – | A unique identifier for this snapshot. Required when storing the snapshot externally. Used to reference and retrieve the snapshot. |
No output schema declared.
No examples provided.
create_team Create Team ~80
Create a new team with a required name and optional email contact. This establishes a new team entity that can be used to organize users and resources.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | Email address associated with the team for contact and notifications purposes. | |
| name | string | yes | The name of the team. This is a required identifier used to distinguish the team from others. |
No output schema declared.
No examples provided.
create_user Create User ~124
Create a new user in Grafana. Requires the `users:create` permission in Grafana Enterprise with Fine-grained access control enabled. Optionally assign the user to a different organization using the OrgId parameter when `auto_assign_org` is enabled.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | Email address for the new user. Used for user identification and communication. | |
| login | string | – | Login username for the new user. Used for authentication and user identification within Grafana. |
| password | string | – | Initial password for the new user account. Should meet Grafana's password security requirements. |
No output schema declared.
No examples provided.
delete_annotation Delete Annotation ~40
Permanently deletes an annotation by its unique identifier. This action cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| annotation_id | string | yes | The unique identifier of the annotation to delete. |
No output schema declared.
No examples provided.
delete_annotations Delete Annotations ~87
Delete one or more annotations from dashboards. Specify either annotation IDs or a dashboard UID to remove annotations in bulk.
| Name | Type | Req | Description |
|---|---|---|---|
| annotationId | string | – | The unique identifier of a specific annotation to delete. Provide one or more annotation IDs to target specific annotations across dashboards. |
| dashboardUID | string | – | The unique identifier of a dashboard. When provided, all annotations associated with this dashboard will be deleted. |
No output schema declared.
No examples provided.
delete_contact_point Delete Contact Point ~42
Permanently delete a contact point by its unique identifier. This action cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| UID | string | yes | The unique identifier of the contact point to delete. |
No output schema declared.
No examples provided.
delete_correlation Delete Correlation ~58
Remove a correlation from a datasource. This permanently deletes the specified correlation relationship.
| Name | Type | Req | Description |
|---|---|---|---|
| correlationUID | string | yes | The unique identifier of the correlation to delete. |
| uid | string | yes | The unique identifier of the datasource containing the correlation to delete. |
No output schema declared.
No examples provided.
delete_datasource Delete Data Source ~57
Permanently delete a data source by its unique identifier. Requires datasources:delete permission with appropriate scopes in Grafana Enterprise with Fine-grained access control enabled.
| Name | Type | Req | Description |
|---|---|---|---|
| uid | string | yes | The unique identifier of the data source to delete. |
No output schema declared.
No examples provided.
delete_library_element Delete Library Element ~65
Permanently delete a library element by its unique identifier. This action cannot be undone and will fail if the library element is currently connected to other resources.
| Name | Type | Req | Description |
|---|---|---|---|
| library_element_uid | string | yes | The unique identifier of the library element to delete. Must reference an unconnected library element. |
No output schema declared.
No examples provided.
delete_migration_session Delete Migration Session ~49
Permanently delete a cloud migration session by its unique identifier. This action removes the migration session and its associated data.
| Name | Type | Req | Description |
|---|---|---|---|
| uid | string | yes | The unique identifier of the migration session to delete. |
No output schema declared.
No examples provided.
delete_mute_timing Delete Mute Timing ~54
Delete a mute timing configuration by name. This removes the specified mute timing rule from the provisioning system.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | The name of the mute timing to delete. Must match an existing mute timing configuration. |
No output schema declared.
No examples provided.
delete_notification_template Delete Notification Template ~56
Delete a notification template group by name. This operation permanently removes the template group and all associated configurations.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | The name of the notification template group to delete. Must be an exact match to an existing template group. |
No output schema declared.
No examples provided.
delete_organization Delete Organization ~49
Permanently delete an organization and all associated data. This action cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| org_id | string | yes | The unique identifier of the organization to delete, specified as a 64-bit integer. |
No output schema declared.
No examples provided.
delete_prometheus_rule_group Delete Prometheus Rule Group ~101
Deletes a specific rule group from Prometheus-compatible alerting rules. This operation only succeeds if the rule group was originally imported from a Prometheus-compatible source.
| Name | Type | Req | Description |
|---|---|---|---|
| Group | string | yes | The name of the rule group to delete. This identifies the specific group of alert rules within the namespace. |
| NamespaceTitle | string | yes | The namespace title that contains the rule group to delete. This identifies the logical grouping or project under which the rules are organized. |
No output schema declared.
No examples provided.
delete_prometheus_rule_group_config Delete Prometheus Rule Group ~77
Deletes a specific rule group from a Prometheus-compatible source. This operation only succeeds if the rule group was originally imported from Prometheus.
| Name | Type | Req | Description |
|---|---|---|---|
| Group | string | yes | The name of the rule group to delete within the specified namespace. |
| NamespaceTitle | string | yes | The namespace title that contains the rule group to be deleted. |
No output schema declared.
No examples provided.
delete_prometheus_rules_by_namespace Delete Prometheus Rules by Namespace ~75
Permanently deletes all rule groups that were imported from Prometheus-compatible sources within a specified namespace. This operation removes the entire namespace and its associated rules.
| Name | Type | Req | Description |
|---|---|---|---|
| NamespaceTitle | string | yes | The name of the namespace containing the Prometheus-compatible rule groups to delete. This identifier specifies which namespace's rules will be removed. |
No output schema declared.
No examples provided.
delete_prometheus_rules_namespace Delete Prometheus Rules Namespace ~73
Deletes all rule groups that were imported from Prometheus-compatible sources within a specified namespace. This operation removes the entire namespace and its associated rules.
| Name | Type | Req | Description |
|---|---|---|---|
| NamespaceTitle | string | yes | The name of the namespace containing the Prometheus-imported rule groups to delete. This identifier specifies which namespace's rules will be removed. |
No output schema declared.
No examples provided.
delete_public_dashboard Delete Public Dashboard ~69
Remove a public dashboard link from a dashboard, preventing public access to the dashboard's shared view.
| Name | Type | Req | Description |
|---|---|---|---|
| dashboardUid | string | yes | The unique identifier of the dashboard that contains the public dashboard link to be deleted. |
| uid | string | yes | The unique identifier of the public dashboard link to be removed. |
No output schema declared.
No examples provided.
delete_query_history Delete Query History ~48
Permanently removes a query from the query history by its unique identifier. This action cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| query_history_uid | string | yes | The unique identifier of the query history entry to delete. |
No output schema declared.
No examples provided.
delete_recording_rule Delete Recording Rule ~61
Permanently delete a recording rule from the registry and stop its execution. The rule will no longer be active after deletion.
| Name | Type | Req | Description |
|---|---|---|---|
| recordingRuleID | string | yes | The unique identifier of the recording rule to delete. Must be a valid 64-bit integer. |
No output schema declared.
No examples provided.
What is the com.mcparmory/grafana MCP server?
com.mcparmory/grafana is an MCP server listed in the public MCP registry as com.mcparmory/grafana. Manage dashboards, users, teams, alerts, data sources, and access control. This page covers its container image (ghcr.io/mcparmory/grafana:1.0.3).
Is the com.mcparmory/grafana MCP server safe to use?
com.mcparmory/grafana scores 50 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the com.mcparmory/grafana MCP server expose?
com.mcparmory/grafana exposes 218 tools: list_roles, get_role, list_role_assignments, list_team_roles_search, list_team_roles, and 213 more. Their descriptions and schemas cost roughly 20,635 tokens of context every time the server is loaded.
Is the com.mcparmory/grafana MCP server still maintained?
com.mcparmory/grafana is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.