groundlight-mcp-server

Created By
groundlighta year ago
MCP Server for Groundlight
Overview

What is Groundlight MCP Server?

Groundlight MCP Server is a Model Context Protocol (MCP) server designed for interacting with Groundlight, providing tools to create and manage Detectors and ImageQueries.

How to use Groundlight MCP Server?

To use the Groundlight MCP Server, you can run it using Docker with the provided configuration. You can interact with the server through its API to create detectors and submit image queries.

Key features of Groundlight MCP Server?

  • Create and manage binary classification detectors.
  • Submit images for analysis and receive labels with confidence scores.
  • List all detectors and image queries associated with the user.
  • Get detailed information about specific detectors and image queries.

Use cases of Groundlight MCP Server?

  1. Developing image classification applications.
  2. Automating image analysis tasks in various domains.
  3. Enhancing machine learning models with user feedback through detectors.

FAQ from Groundlight MCP Server?

  • What is a Detector?

A Detector is a model that analyzes images and provides responses based on binary classification.

  • How do I submit an image for analysis?

You can submit an image by providing its path, URL, or raw bytes to the submit_image_query tool.

  • Is the Groundlight MCP Server open-source?

Yes, the Groundlight MCP Server is available on GitHub and is open for contributions.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
groundlight
Star
1
Language
Python
License
Apache-2.0 license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago