Matra

com.matrajsPublished by matrajs.comv1.1.6Updated Oct 24, 2026

The Matra rich text editor's documentation as an MCP server: every extension, command and API.

VerifiedSTDIODesktop onlyKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

Serves the Matra rich text editor's documentation to an AI assistant, letting it list, read and search every extension, command and API page.

What you can do
  • List every documentation page with its slug and one-line description
  • Read a single page as Markdown by slug
  • Search the docs and get ranked pages with snippets
  • Expose each page as a resource under a docs URI scheme
  • Answer questions about Matra from the shipped documentation instead of model memory
When to use it
Useful when building with the Matra rich text editor and you want the assistant to answer from the official docs, engine notes, benchmarks, security notes and changelog rather than guessing. It is a documentation lookup server, not an editor control tool.
Requirements
Runs as a local process via npx from the npm package @matrajs/mcp; Node.js and network access for the initial package download. Defaults to stdio, with an optional HTTP mode on localhost port 3333. No accounts, API keys or environment variables are declared.
Before you install
Read-only documentation access; the docs are bundled at build time and nothing is fetched at runtime. The package is installed and executed locally through npx, so you are trusting the published package. No credentials or write actions are involved.

Installation

In SourceWeft

  1. Open Matra in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

@matrajs/mcp

The Matra documentation as a Model Context Protocol server, so any AI tool can read it. Zero dependencies, like every other Matra package.

sh
npx -y @matrajs/mcp            # stdio · what a desktop client spawnsnpx -y @matrajs/mcp --http     # http://localhost:3333/mcp

Connect it, step by step

Claude Code

sh
claude mcp add matra -- npx -y @matrajs/mcp

Claude Desktop — in claude_desktop_config.json:

json
{  "mcpServers": {    "matra": { "command": "npx", "args": ["-y", "@matrajs/mcp"] }  }}

Cursor — in .cursor/mcp.json, the same object under "mcpServers".

Codex — in ~/.codex/config.toml:

toml
[mcp_servers.matra]command = "npx"args = ["-y", "@matrajs/mcp"]

Anything that speaks HTTP — run npx -y @matrajs/mcp --http 3333 and point the client at http://localhost:3333/mcp.

Then ask the tool something about Matra. It will call search_docs, read the page it needs, and answer from the documentation rather than from memory.

What it serves

ToolDoes
list_docsEvery page, with its slug and a one-line description.
read_doc { slug }One page, as Markdown.
search_docs { query, limit? }Ranked pages with a snippet each.

Every page is also a resource at matra://docs/<slug>.

The pages are the repository's Markdown — README, the engine notes, benchmarks, security, the changelog — and every page of matrajs.com/docs, converted to Markdown at build time and shipped inside the package. Nothing is fetched at runtime.

Use it from code

ts
import { createServer } from '@matrajs/mcp'
const server = createServer(docs)server.handle({ jsonrpc: '2.0', id: 1, method: 'tools/list' })

createServer is the protocol without a transport: one message in, one reply out. Put it behind whatever transport you already have.

Source: packages/mcp/README.md at commit 4077a82

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.1.6LatestSep 16, 2026

Score

50% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

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

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts