Skip to main content
Glama
nimbusbci

nimbus-mcp

Official
by nimbusbci
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to nimbus-mcp

No user-submitted related servers found.

    Related Servers

    • neuro-mcp

      AImplifier
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that gives AI agents a unified interface to clinical/research EEG workflows: signal processing, source imaging, persistent dataset/EHR storage, and web visualization.
      59 PyPI
      1
      BSD 3-Clause

    • MNE-MCP

      Exekiel179
      A
      license
      B
      quality
      C
      maintenance
      An MCP server that gives AI assistants conversational access to MNE-Python for analyzing neurophysiology data (EEG, MEG, sEEG, ECoG, fNIRS). Enables plain-language analysis pipelines, from loading recordings to generating figures and explanations.
      41
      8
      MIT

    • lyra-mcp

      Ralf090102
      F
      license
      A
      quality
      C
      maintenance
      Enables Claude to inspect, configure, run, and modify individual RAG/agent pipeline stages (retrieve, rerank, generate, eval) as structured typed tool calls, and execute the full pipeline end to end.
      5
      -

    • eeg-mcp

      AImplifier
      A
      license
      A
      quality
      C
      maintenance
      A Model Context Protocol server that provides AI agents with a unified interface for real-time EEG acquisition, replay, processing, visualization, recording, and stimulation from over 66 BrainFlow boards.
      47
      2
      BSD 3-Clause

    • Gumloop MCP Server

      thenavidm
      A
      license
      B
      quality
      A
      maintenance
      Enables AI agents to inspect saved flows and their input schemas, start and monitor runs, and manage agents, sessions, skills, Brain knowledge, artifacts and account administration through 92 tools. Operations are confirmation-gated and use explicitly selected private credential profiles for account and team access.
      92
      463 npm
      AGPL 3.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.2/5.0

    Scored across 32 tools

    Disambiguation4/5

    Most tools target distinct actions/resources, but a few pairs overlap: stream_status vs get_live_session both poll a live session, and inspect_dataset vs inspect_file give near-identical exploratory summaries for different sources. Descriptions help disambiguate, but an agent may still hesitate between them.

    Naming Consistency4/5

    Names are predominantly consistent snake_case verb_noun (list_nodes, get_template, run_pipeline). Minor deviations like whoami and stream_status break the exact verb_noun pattern but remain readable and conventional.

    Tool Count2/5

    32 tools is heavy for a single MCP server; several subdomains (streaming, pipelines, datasets, projects, artifacts) could be consolidated. While each tool has a purpose, the set exceeds the 25-tool threshold where navigation becomes cumbersome.

    Completeness4/5

    The surface covers major workflows: device streaming, pipeline building/validation/execution, experiments, datasets, projects, and artifacts. Minor gaps exist (no delete/update for projects, pipelines, or artifacts), but agents can work around them.

    Resources