bagel — Watchlist | MCP100 Index

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Monitor this implementation for changes in adoption, MCP interface, maintenance and permission boundary.

Reviewed Oct 10, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Query robotics, drone and IoT streams through an edge-data reduction MCP interface

What we know

Query robotics, drone, and IoT data in plain English through an MCP server, with an intelligent edge data reduction pipeline that keeps only the data that matters. Query robotics, drone and IoT streams through an edge-data reduction MCP interface.

Maintenance / activity evidence

GitHub REST pushed_at 2026-10-09T20:27:41Z

Tracking evidence observed Oct 10, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: medium.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Scoped by connected account, local OS, and configuration; verify exact permissions before installation. Complete write authority is not verified.
Edge deployment, data source and MCP client configuration
Telemetry and fleet data

Remote IoT data may be sensitive; edge reduction affects retained records; write commands not verified.

Full authority, access and evidence limits are available in Review context and Access & risk.

Popularity

398 repository stars

Stars observed Oct 9, 2026.

Repository total for Extelligence-ai/bagel.

All limitations / Review context

Has bagel changed its specific MCP integration, install method or privilege scope, and does it justify shortlist promotion?

High-impact permissions explicitly documented; no known blocker to an accurately caveated public Radar listing in limited first-party review.

Remote IoT data may be sensitive; edge reduction affects retained records; write commands not verified.
Scoped by connected account, local OS, and configuration; verify exact permissions before installation.
Edge deployment, data source and MCP client configuration
Telemetry and fleet data
Complete write authority is not verified.
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
No exhaustive advisory or runtime review performed; never infer installation safety.
Write actions/tool inventory not confirmed against exact tool documentation; listed action classes remain illustrative or context-dependent. Empty inventory does not establish read-only.
Setup and runtime permissions are implementation- and account-specific; follow linked upstream documentation.
Repository pushed_at explicitly observed

Original activity observations

GitHub REST pushed_at 2026-10-09T20:27:41Z

Technical identity

github.com/Extelligence-ai/bagel

Exact implementation source: https://github.com/Extelligence-ai/bagel ↗
Reviewed resource type: MCP Server
Repository identity: Extelligence-ai/bagel

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 10, 2026 · Latest source observation Oct 10, 2026

GitHub repository ↗
extelligence-ai/bagel
Recorded repository material and project history.

Setup · Watchlist

Install & Agents

Claude Code

Publisher instructions with a documented client setup path.

Source evidence observed Oct 12, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
Use the publisher-documented command or connection method below; complete the prerequisites and client configuration before expecting a usable MCP connection.
claude mcp add bagel -- uvx --from "bagel-mcp[ros]" bagel-mcp --transport stdio

Configure / authenticate

Publisher instructions

Requires uvx; ROS features and Docker/robot integrations have extra dependencies and separate setup.

Advanced configuration · claude desktop json

{
  "mcpServers": {
    "bagel": {
      "args": [
        "--from",
        "bagel-mcp[ros]",
        "bagel-mcp",
        "--transport",
        "stdio"
      ],
      "command": "uvx"
    }
  }
}

Check connection
Suggested check
Restart the configured Claude Code client and inspect the bagel MCP entry (claude mcp get bagel) and its available tools. The ROS/Docker/robot bridge requires distinct deployment prerequisites; do not move actuators or mutate robot data to test registration.
Remove / uninstall / revoke
MCP100 setup guide
Remove the matching MCP configuration from the client. This does not uninstall the local package or revoke provider credentials. Client disconnect (claude-code, only if registered using the name `bagel`): `claude mcp remove bagel`. This unregisters the client entry; it does not uninstall packages or revoke remote service credentials.
claude mcp remove bagel

Official Documentation & Sources

What it does

Query robotics, drone, and IoT data in plain English through an MCP server, with an intelligent edge data reduction pipeline that keeps only the data that matters. Query robotics, drone and IoT streams through an edge-data reduction MCP interface.

Capability: Data & Databases
Resource type: MCP Server
Industry: Manufacturing & Industrial
Best fit: Query robotics, drone and IoT streams through an edge-data reduction MCP interface

Representative uses

Query device telemetry in natural language
Analyze edge-collected windows
Investigate sensor anomalies
Query robotics, drone and IoT streams through an edge-data reduction MCP interface

Limitations

Remote IoT data may be sensitive; edge reduction affects retained records; write commands not verified.
Setup and runtime permissions are implementation- and account-specific; follow linked upstream documentation.
Repository pushed_at explicitly observed

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Edge deployment, data source and MCP client configuration
Permissions: Scoped by connected account, local OS, and configuration; verify exact permissions before installation.
Data handling: Telemetry and fleet data
Cost: may incur external API or infrastructure charges; unverified
Risk and cautions: Remote IoT data may be sensitive; edge reduction affects retained records; write commands not verified.

Access scope and cautions

Write actions: Not verified
Risk level: moderate
Security notes: Remote IoT data may be sensitive; edge reduction affects retained records; write commands not verified.

The reviewed evidence does not establish the complete write authority of this MCP. Consult the unresolved evidence before granting write access.

FAQ

Based on reviewed evidence as of 2026-10-09. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Query device telemetry in natural language; Analyze edge-collected windows; Investigate sensor anomalies; Query robotics, drone and IoT streams through an edge-data reduction MCP interface.

What setup and authentication are documented?

A complete connection procedure is not verified. Client notes: Command provided only where first-party command or package existence is established; verify the client configuration against upstream documentation. Installation/authentication detail is incomplete; do not infer settings from package name. These facts do not supply missing installation commands, credentials or a verified authentication procedure. Authentication: Edge deployment, data source and MCP client configuration

Can it modify data or perform write operations?

Not verified. The available evidence does not establish the complete write authority. Recorded permission context: Scoped by connected account, local OS, and configuration; verify exact permissions before installation.

What data-handling boundary should I consider?

Telemetry and fleet data

What limitations and risks should I check before use?

Remote IoT data may be sensitive; edge reduction affects retained records; write commands not verified. Setup and runtime permissions are implementation- and account-specific; follow linked upstream documentation. Repository pushed_at explicitly observed. No exhaustive advisory or runtime review performed; never infer installation safety.