Latex Mathml Server

Created By
HappyAnya year ago
Overview

what is LaTeX to MathML MCP Server?

LaTeX to MathML MCP Server is a Model Context Protocol (MCP) server that converts LaTeX mathematical expressions into MathML format, facilitating easy integration and access to mathematical content.

how to use LaTeX to MathML MCP Server?

To use the server, clone the repository, install the necessary dependencies, and run the server using Node.js. You can then send LaTeX expressions to the server for conversion.

key features of LaTeX to MathML MCP Server?

  • Converts LaTeX mathematical expressions to MathML format.
  • Supports both tool-based conversion and resource-based access.
  • Implements the standard MCP protocol for seamless integration.
  • Utilizes MathJax-node for lightweight and fast conversion.

use cases of LaTeX to MathML MCP Server?

  1. Converting LaTeX documents into web-compatible MathML for rendering.
  2. Integrating mathematical content into educational platforms.
  3. Providing API services for applications requiring mathematical expression handling.

FAQ from LaTeX to MathML MCP Server?

  • What is the input format for the conversion?

The input format is a LaTeX string representing the mathematical expression.

  • How do I access the converted MathML?

You can access the MathML via a tool-based conversion or by using a resource URI pattern.

  • Is there any specific dependency required to run the server?

Yes, you need to install mathjax-node and @modelcontextprotocol/sdk as dependencies.

Server Config

{
  "mcpServers": {
    "latex-mathml-server": {
      "isActive": true,
      "command": "node",
      "args": [
        "path_to_your_server/index.js"
      ]
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
HappyAny
Star
-
Language
-
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