Skip to content

Update MCP overview with token usage details #68

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
CandiceChislett merged 1 commit into from
Oct 27, 2026
Merged

Update MCP overview with token usage details #68

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 14 additions & 4 deletions docs/Monitor-your-data/MCP/mcp-overview.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,3 @@


# MCP: the Model Context Protocol

**MCP** - the [Model Context Protocol](https://modelcontextprotocol.io/introduction) - is a standardized way for software vendors to make their applications interface to AI tooling. Using MCP, AI models can get up-to-date information to augment their training models.
Expand All @@ -17,14 +15,26 @@ MCP is used by many providers, including Claude Desktop, to help AI tooling acce
The OpsPilot MCP is an integration of the [Grafana MCP](https://github.com/grafana/mcp-grafana) project.

!!! note
The OpsPilot MCP is a **read-only** data source – you can’t make changes to your account using it.
The OpsPilot MCP is **read-only** for your telemetry data – you can’t change your account, dashboards, or data using it. The one exception is saving memories to the OpsPilot Coworker (see [Token usage](#token-usage)).

### Key capabilities

- Perform queries against Metrics (Mimir/Prometheus) and Logs (Loki).
- Get dashboards, panels, and the queries behind those panels – and run them directly (Prometheus and Loki only).
- Save information to the OpsPilot Coworker's memory using the `submit_memory` tool, so it can be used across the application.

### Token usage

When Claude is connected to OpsPilot through MCP, it interacts directly with your data using the tools exposed by the OpsPilot MCP. In most cases, this does **not** consume OpsPilot tokens.

- **Data queries:** Claude can access and query your data through the available MCP tools without incurring OpsPilot token charges. Claude handles the reasoning and processing of these requests, so the OpsPilot Coworker doesn't need to do the work.
- **Saving memories:** The main exception is the `submit_memory` tool. It saves information to the OpsPilot Coworker's memory so it can be accessed and used across the application. This operation consumes a small number of OpsPilot tokens.

In summary, connecting Claude through MCP lets you query and interact with your OpsPilot data without the standard OpsPilot AI token charges, except for specific operations such as saving memories.

!!! note
Any token usage charged separately by your Claude provider remains subject to your agreement with that provider.


!!! info "Learn more"
[Installing the OpsPilot MCP](/Monitor-your-data/MCP/MCP/)

Loading