Latex

app.ofiaPublished by ofia.appOfficial publisherv1.0.0Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableProductivity & WorkflowFiles & Storage

Overview

AI-generated overview

Remote Ofia LaTeX workspace that lets an assistant edit and compile multi-file LaTeX projects and export publication-ready PDFs.

What you can do
  • Edit LaTeX source in a persistent workspace, including multi-file projects.
  • Compile projects and export publication-ready PDFs.
  • Keep work in a persistent workspace rather than a one-off session.
When to use it
Useful when you want an assistant to draft, revise and compile LaTeX documents such as papers, reports or theses, and to produce finished PDFs without a local TeX installation.
Requirements
A remote MCP endpoint at ofia.app over streamable HTTP. An Ofia API key is required, sent as a bearer token in the Authorization header; keys are created in the Ofia developer area.
Before you install
The server requires an Ofia API key as a bearer credential in the Authorization header; keep it secret and scope it as narrowly as the provider allows. Documents are stored in a hosted workspace, so content is sent to a third party. Compiling and exporting write to that workspace.

Installation

In SourceWeft

  1. Open Latex in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/app.ofia%2Flatex/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "latex": {
      "type": "http",
      "url": "https://ofia.app/api/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

56% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.