Bigeye MCP Server

An MCP (Model Context Protocol) server that provides tools for interacting with the Bigeye Data Observability platform.

Local serverstdioPython

What is the Bigeye MCP server?

An MCP (Model Context Protocol) server that provides tools for interacting with the Bigeye Data Observability platform. Exposed over MCP by the bigeye mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

Its toolset

Everything the assistant can do here goes through one of these:

  • Tags — The Tags tool exposed by this server
  • System — The System tool exposed by this server

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

Configuration

You will need 7 environment variables: BIGEYE_API_KEY, BIGEYE_BASE_URL, BIGEYE_WORKSPACE_ID, BIGEYE_DEMO_API_KEY, BIGEYE_DEMO_WORKSPACE_ID, BIGEYE_APP_API_KEY, BIGEYE_APP_WORKSPACE_ID. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

  • Docker (Docker Desktop or Docker Engine)

When to reach for it

Plenty of monitoring and observability servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Bigeye's toolset — Tags, System — is a fair guide to whether it matches your workflow. It is maintained by bigeyedata; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Caveats

  • 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.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the bigeye mcp server does with a few real requests.

Available tools

ToolWhat it does
TagsThe Tags tool exposed by this server.
SystemThe System tool exposed by this server.

How to install the Bigeye MCP server

{
     "mcpServers": {
       "bigeye": {
         "command": "/absolute/path/to/mcp-wrapper.sh"
       }
     }
   }

Configuration as documented by the project. Restart the client after saving.

Configuration

  • Docker (Docker Desktop or Docker Engine)
VariableDescriptionRequired
BIGEYE_API_KEYCredential the server authenticates with.Yes
BIGEYE_BASE_URLEndpoint or connection string the server talks to.Yes
BIGEYE_WORKSPACE_IDConfiguration value read at startup.Optional
BIGEYE_DEMO_API_KEYCredential the server authenticates with.Yes
BIGEYE_DEMO_WORKSPACE_IDConfiguration value read at startup.Optional
BIGEYE_APP_API_KEYCredential the server authenticates with.Yes
BIGEYE_APP_WORKSPACE_IDConfiguration value read at startup.Optional

Example prompts to try

  • Use Bigeye to Tags.
  • Use Bigeye to System.

Frequently asked questions

It connects Bigeye to MCP-compatible AI assistants such as Claude and Cursor, exposing 2 tools (Tags, System) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Bigeye directly.