MCP Server for Groundlight
MCP Server for Groundlight. The groundlight mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 4 defined tools rather than through you.
The functionality and available tools are subject to change and expansion as we continue to develop and improve this server.
A Model Context Protocol (MCP) server for interacting with Groundlight. This server provides tools to create, list and customize Detectors, submit and list ImageQueries, create, list and delete Alerts, and examine detector evaluation metrics.
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.
Everything the assistant can do here goes through one of these:
Description — Create a detector based on the specified configuration. Supports three modes:Input — config (DetectorConfig object with name, query, confidence_threshold, mode, and mode-specific configuration)Returns — Detector objectTools — The following tools are available in the Groundlight MCP server:You will need one environment variable: GROUNDLIGHT_API_TOKEN. 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.
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. Groundlight's toolset — Description, Input, Returns and 1 more — is a fair guide to whether it matches your workflow. It is maintained by groundlight; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Description | Create a detector based on the specified configuration. Supports three modes: |
| Input | config (DetectorConfig object with name, query, confidence_threshold, mode, and mode-specific configuration) |
| Returns | Detector object |
| Tools | The following tools are available in the Groundlight MCP server: |
"mcpServers": {
"groundlight": {
"command": "docker",
"args": ["run", "--rm", "-i", "-e", "GROUNDLIGHT_API_TOKEN", "groundlight/groundlight-mcp-server"],
"env": {
"GROUNDLIGHT_API_TOKEN": "YOUR_API_TOKEN_HERE"
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| GROUNDLIGHT_API_TOKEN | Credential the server authenticates with. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.