Marimo Documenation MCP Server

Created By
StevenBtwa year ago
A Model Context Protocol (MCP) server that provides programmatic access to the Marimo Documentation.
Overview

What is Marimo Documentation MCP Server?

Marimo Documentation MCP Server is a Model Context Protocol (MCP) server that provides programmatic access to the Marimo Documentation, allowing users to fetch and search through API documentation for various Marimo components.

How to use Marimo Documentation MCP Server?

To use the server, install the necessary dependencies, build the server, and configure it with your application (e.g., Claude Desktop or VSCode Cline Extension) to access the documentation.

Key features of Marimo Documentation MCP Server?

  • Fetch detailed API documentation for any Marimo UI element or component.
  • Search functionality across all Marimo API documentation.
  • Access to structured documentation for various components, including inputs, layouts, and media elements.
  • Organized error handling and debugging tools.

Use cases of Marimo Documentation MCP Server?

  1. Developers can quickly find API documentation for UI components while building applications.
  2. Teams can integrate the server into their development environment for easy access to documentation.
  3. Debugging and error handling can be streamlined with organized error messages and logs.

FAQ from Marimo Documentation MCP Server?

  • What programming language is used for the server?

The server is built using TypeScript.

  • How can I install the server?

You can install it by running npm install and following the configuration instructions for your platform.

  • Is there a way to debug the server?

Yes, the server outputs detailed logs to stderr, and you can use the MCP Inspector for additional debugging tools.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
StevenBtw
Star
0
Language
JavaScript
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