MCP Server for Perses

What is MCP Server for Perses?

The MCP Server for Perses is a local Model Context Protocol (MCP) server that enables LLM hosts (OpenCode, Claude Desktop, VS Code, Cursor) to interact with the Perses Application in a standardized way.

How to use MCP Server for Perses?

Download the binary from the releases page, make it executable, create a YAML configuration file specifying the Perses server URL and authentication, then add the server to your MCP client’s configuration (e.g., Claude Desktop, VS Code, or OpenCode). Run the server with perses-mcp-server --config /path/to/config.yaml.

Key features of MCP Server for Perses

• Supports stdio and Streamable HTTP transport modes
• Configurable read-only mode for safe exploration
• Multiple authentication methods: basic (username/password) and Bearer token
• Environment‑variable override of all configuration values
• Register specific resources (e.g., dashboards, projects, datasources) or all available ones

Use cases of MCP Server for Perses

• List all projects and retrieve project details via natural language
• Create, list, and get dashboards for a specific project
• Manage global and project‑level datasources
• Administer roles, global roles, and role bindings
• Create and query project‑level and global variables

FAQ from MCP Server for Perses

What does the MCP Server for Perses do?

It provides a set of MCP tools that allow LLM hosts to perform operations on a Perses server, such as listing projects, creating dashboards, and managing datasources.

What are the prerequisites to run it?

A running Perses instance is required. The server binary must be downloaded from the releases page and made executable.

How can I authenticate with the Perses server?

You can use either basic authentication (login/password) or a Bearer token obtained via percli whoami --show-token. Sensitive values can be passed as environment variables.

What transport modes are supported?

Two transport modes: stdio (default) for local setups and http (Streamable HTTP) for remote hosting or multi‑client connections.

Can I run the server in read‑only mode?

Yes. Set read_only: true in the configuration file. In this mode, only tools that retrieve information are enabled; write operations like create_project or create_dashboard are disabled.