Latex MCP Server

by ofia Your server? Claim it

answering

Latex is answering right now. Last checked 14 min ago.

Persistent AI LaTeX workspace: edit and compile multi-file projects, export publication-ready PDFs.

Uptime history 48 days of history · worst day 99%

48 days agonow

100.0%

Uptime 24h

91 of 91 checks

—

Tools

hidden behind auth

502 ms

Response time

average over 24h

authentication required

Access

streamable-http

Latex missed one check this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 14 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add latex --transport http https://ofia.app/api/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "latex": {
      "url": "https://ofia.app/api/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.latex]
url = "https://ofia.app/api/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "latex": {
      "url": "https://ofia.app/api/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "latex": {
      "url": "https://ofia.app/api/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, but it did not say what kind of credentials it expects.

Endpoints

URL	Transport	State	Latency	Checked
https://ofia.app/api/mcp	streamable-http	needs auth	321 ms	14 min ago

Alternatives to Latex

same job, measured the same way

LetX

by letx

Collaborative LaTeX editor: search 1000+ templates, edit projects, and compile them to PDF.

answering

Snapstate

by timbassler88

Persistent state for AI agent workflows. Save, resume, and replay multi-step workflows.

28 installs/wk local only

sayou

by pixell-global

Persistent knowledge workspace for AI agents. Versioned files, search, and MCP tools.

52 installs/wk local only

Writespace MCP

by write-space

Persistent docs and memory for AI agents — read, write, organize & search a shared workspace.

answering

Clarik MCP Server

by mikerichardmail

Clarity and memory persistent workspace context manager for Claude.

36 installs/wk local only

Hushvert

by hushvert

File conversion for AI agents: office docs, PDF to Word, video, and LLM-ready markdown via API.

50 installs/wk local only

.FAF Context

by faf

.FAF Context — persistent project context for Cursor, VS Code and every MCP-compatible IDE.

2 140 installs/wk local only

OpenProject

by alex13slem

Manage OpenProject projects, work packages, files, relations, boards, users, and notifications.

34 installs/wk local only

Latex — questions

Answers built from our own checks of this server.

Why is there no tool list for Latex?

The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.

Is Latex working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 502 ms. The bar chart above shows every period we have measured.

How do I connect Latex?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own credentials: it refuses anonymous clients.

Does Latex need an API key?

Yes. Every time we knock, Latex answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.

How fast is Latex?

It answers our handshake in 502 ms on average, which is faster than 29% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.