board-local
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@board-locallist the Board models"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Local Board MCP
Working read-only MCP for local Board, using your authenticated Firefox session. Version 1.2.0 is registered in Codex as board-local; Node 22+ required. No npm packages required.
Use
Run Open-BoardFirefox.ps1 in your normal Windows account. It opens a separate Firefox profile under %LOCALAPPDATA%/BoardMCP/firefox-profile.
Sign in to Board with your regular account and leave that Firefox window open. Sign in again there if the session expires.
Restart Codex if board-local tools are not loaded. Ask it to list Board models, entities, members, relationships, cubes, or read cube values from existing capsule screens.
The connector navigates that dedicated window. Use your usual browser for other work during reads. Firefox automation listens on 127.0.0.1:9228, verified 2026-09-24. Session information stays in Firefox; the connector does not extract passwords or tokens.
Related MCP server: MCP Snowflake Reader
Tools and limits
list_models: model links rendered on the authenticated Data Models page.
list_entities(model): entity grid metadata, including member counts and physical names.
list_cubes(model): cube grid metadata, including types, versions and file sizes.
list_entity_members(model, entity?): member codes, descriptions, and additional rendered fields; omit entity to read each Entity.
list_relationships(model): parent-child hierarchy edges from the Relationships tree.
read_cube_data(model, cube): values returned by existing capsule DataView screens for the selected Cube, along with screen dimensions and row/column labels.
Column labels follow the Board session language. Grid reads report detected filters, paging, and possible additional rows. Cube values come from existing DataView layouts and can reflect their filters, selections, aggregations, and visible dimensions; they are not a guaranteed dump of every stored cell. A Cube with no matching screen returns no view results, which does not by itself prove the Cube is empty. No model edits or procedures are exposed. Requests are serialized within each MCP process; avoid simultaneous reads from multiple MCP processes.
Future plan: read-only Firefox scan and report
The next planned stage is a user-controlled, read-only Firefox scanning flow. It will first show the available Data Models and Capsules. The user can select which ones to inspect, then run a deeper scan of the selected scope. The scan should collect the available model and capsule structure, Entity members, hierarchy and occurrence relationship analysis, Cube dimensions, and values shown in capsule DataViews.
The scan should export a human-readable Markdown report and a structured JSON snapshot. The report should identify its scan time and scope, and mark each section complete, partial, or unavailable. DataView values can be filtered, aggregated, or limited by Board's rendered layout, so the report must retain those limits instead of claiming a full stored-cell export. This scan and export flow is not implemented yet.
The JSON snapshot should preserve Board identifiers, selections, relationships, and completeness details so a future MCP edit workflow can use the scan as context. Any future edit capability will be a separate addition; the current connector remains read-only.
Verification
Run: node Test-Mcp.cjs
This tests MCP stdio initialization, tool discovery, the original three live metadata reads, and invalid model rejection. Verified 2026-09-24: Leonardo; six entities (Fornitori, Materia Prima, Regione, Tipologia fornitore, Prodotti, Negozi); two cubes (Ordini, Fatturato). Both grids reached bottom without detected filters or extra pages. The expanded reads use the same authenticated Firefox profile.
Original Public API
The Board 15.1 Public API still fails with HTTP 500 due to unresolved IImpersonificationService. The MCP now uses Firefox. See BOARD-API-ISSUE.md. Original PowerShell setup/diagnostic scripts remain for retesting after a Board repair. Their DPAPI credentials under LocalAppData/BoardMCP/client.xml are unused by the Firefox connector. Test-BoardMcp.ps1 tests the original API; Test-Mcp.cjs tests the working MCP.
License
MIT. See LICENSE.
This server cannot be deployed
Maintenance
Related MCP Connectors
Read-only MCP access to sessions, funnels, campaigns, errors, live visitors, and anomalies.
Read-only finance and operations controls for AI agents with evidence and safe next actions.
Services, case studies, 169 data and AI guides, and AI readiness scoring. Read-only, keyless.
Read-only access to your Citlyze workspace: AI search visibility, citations, and recommendations.
Related MCP Servers
- FlicenseBqualityDmaintenanceEnables read-only access to FileMaker databases through the Data API, allowing users to retrieve records, analyze metadata, search across layouts, and infer relationships while maintaining data security.16-
- AlicenseNot gradedqualityCmaintenanceProvides secure, read-only access to Snowflake databases through the Model Context Protocol. It allows users to query data while strictly prohibiting destructive SQL commands like INSERT, UPDATE, or DELETE.MIT
- AlicenseCqualityCmaintenanceEnables browsing and querying Smartsheet data through read-only MCP tools, allowing MCP-compatible clients to explore sheets, reports, dashboards, and more.66MIT
- FlicenseBqualityDmaintenanceProvides read-only EspoCRM access for AI assistants, enabling record retrieval and preparation of signed change sets without direct modification or deletion.7-