PlainSignal MCP Server

PlainSignal Official MCP Server

Local serverstdio

What is the PlainSignal MCP server?

Connect PlainSignal to Claude, Cursor or any other MCP client and it stops being a tab you switch to. PlainSignal Official MCP Server. The plainsignal mcp server is what makes that connection.

What the server does

This is a Model Context Protocol (MCP) server implementation for PlainSignal analytics data. It provides tools for retrieving analytics reports and metrics through the MCP protocol.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

  • Installation — The Installation tool exposed by this server
  • getReport — Retrieves an analytics report for a specified domain and time period
  • getSubReport — Retrieves detailed metrics for a specific aspect of analytics data

Installation

Installation goes through your MCP client rather than a global install: point it at plainsignal-mcp on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

Credentials and setup notes

Configuration is passed through the environment: PLAINSIGNAL_TOKEN, API_BASE_URL, YOUR_PLAINSIGNAL_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Where it fits

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. PlainSignal's toolset — Installation, getReport, getSubReport — is a fair guide to whether it matches your workflow. It is maintained by plainsignal; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against PlainSignal's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Worth knowing first

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
InstallationThe Installation tool exposed by this server.
getReportRetrieves an analytics report for a specified domain and time period.
getSubReportRetrieves detailed metrics for a specific aspect of analytics data.

How to install the PlainSignal MCP server

{
  "mcpServers": {
    "plainsignal": {
      "command": "npx",
      "args": ["-y", "plainsignal-mcp"],
      "env": {
        "PLAINSIGNAL_TOKEN": "your-value",
        "API_BASE_URL": "your-value",
        "YOUR_PLAINSIGNAL_TOKEN": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
PLAINSIGNAL_TOKENCredential the server authenticates with.Yes
API_BASE_URLEndpoint or connection string the server talks to.Yes
YOUR_PLAINSIGNAL_TOKENCredential the server authenticates with.Yes

Example prompts to try

  • Use PlainSignal to Installation.
  • Use PlainSignal to getReport.
  • Use PlainSignal to getSubReport.

Frequently asked questions

Provide a PlainSignal access token via the `--token` command-line flag or set the `PLAINSIGNAL_TOKEN` environment variable.