Skip to main content
Glama
sandraschi

openbci-mcp

by sandraschi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
OPENBCI_PROBENoRun synthetic probe at startup0
OPENBCI_BOARD_IDNoBrainFlow board id hint0
OPENBCI_MCP_PORTNoBackend port10759
OPENBCI_OSC_HOSTNoDefault OSC trigger target127.0.0.1
OPENBCI_OSC_PORTNoDefault OSC UDP port (osc-mcp / VRChat)9000
OPENBCI_SERIAL_PORTNoDefault COM port
OPENBCI_TRIGGERS_FILENoPersisted trigger rules~/.openbci-mcp/triggers.json

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}
logging
{}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
extensions
{
  "io.modelcontextprotocol/ui": {}
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
openbci_boardB

Manage OpenBCI hardware connections via BrainFlow.

OPERATIONS:

  • connect: Open session to Cyton, Ganglion, Galea, synthetic, or streaming board.

  • disconnect: Release session and stop streams.

  • status: Current connection and channel metadata.

  • list_ports: Enumerate serial COM ports (Windows/macOS/Linux).

  • list_boards: Supported board keys and BrainFlow IDs.

  • probe: Quick synthetic-board smoke test.

openbci_exportA

Route live EEG to external consumers via BrainFlow streamers.

OPERATIONS:

  • streamer_add: Pass raw BrainFlow streamer params (see BrainFlow docs).

  • streamer_file: Record to CSV via file:// streamer.

  • streamer_multicast: Forward to multicast for OpenBCI GUI / custom listeners.

Examples (BrainFlow streamer syntax):

  • file://C:/recordings/session.csv

  • streaming_board://225.1.1.1:6677

openbci_helpA

Discovery and usage guide for openbci-mcp.

OPERATIONS:

  • overview: Tool catalog and board keys.

  • quickstart: Typical Cyton USB workflow.

  • ports: Fleet port assignments.

openbci_signalA

Real-time EEG signal analysis via BrainFlow DataFilter.

OPERATIONS:

  • band_power: Delta/theta/alpha/beta/gamma per channel from latest buffer.

  • filter: Apply bandpass, lowpass, highpass, or 60Hz notch to one channel.

openbci_streamA

Control EEG data streaming from a connected OpenBCI board.

OPERATIONS:

  • start: Begin streaming samples into BrainFlow buffer.

  • stop: Stop streaming (session stays connected).

  • snapshot: Return latest EEG samples per channel (requires active stream).

  • marker: Insert timestamped marker into stream (P300/speller experiments).

openbci_triggerC

OSC triggers for BCI neurofeedback and osc-mcp downstream apps.

OPERATIONS:

  • send_osc: Fire a one-shot OSC message (VRChat, Reaper, osc-mcp listener).

  • list_rules: List persisted threshold rules.

  • add_rule: Create band-power rule that emits OSC when matched.

  • remove_rule: Delete rule by id.

  • evaluate: Run rules against current stream band power.

  • history: Recent trigger firings.

  • fire_test: Test OSC path for a rule or custom address.

Default target: 127.0.0.1:9000 (configure osc-mcp or app listener).

agentic_openbci_workflowA

Multi-step OpenBCI workflows via FastMCP sampling (SEP-1577).

Example: agentic_openbci_workflow( workflow_prompt="Connect synthetic board, start stream, compute band power", available_tools=["openbci_board", "openbci_stream", "openbci_signal"], )

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
Prefab Renderer (openbci_help)
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

A3.7/5.0

Scored across 7 tools

Disambiguation5/5

Each tool targets a distinct aspect of OpenBCI operation: board management, streaming, signal analysis, export, triggers, help, and high-level workflow orchestration. No two tools have overlapping primary purposes.

Naming Consistency4/5

Most tools follow the pattern 'openbci_<function>', all lowercase with underscores. However, 'agentic_openbci_workflow' deviates with the prefix 'agentic', and 'openbci_help' is a noun instead of a verb, slightly breaking consistency.

Tool Count5/5

With 7 tools, the server covers the essential functions for BCI data acquisition and processing without being bloated. Each tool has a clear role, and the count feels well-scoped for the domain.

Completeness4/5

The core workflow (connect, stream, analyze, export, trigger) is fully covered. Minor gaps exist, such as lacking advanced signal processing (e.g., artifact removal, epoch extraction) and hardware configuration details, but the set is sufficient for typical use cases.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources