Skip to main content
Glama
Jyzus

hedgedoc-mcp-server

by Jyzus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
HEDGEDOC_URLYesThe URL of the HedgeDoc 1.x instance

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
hedgedoc_create_blankA

Create a blank HedgeDoc note with the instance's default template content.

Useful for quickly starting a new note without providing content upfront. Returns the note ID and URL.

hedgedoc_createA

Create a new HedgeDoc note with a random ID.

  • title: The title of the note (will be added as level-1 heading)

  • content: The markdown body content Returns the note ID and URL. Note: HedgeDoc 1.x does not use API tokens. This tool works anonymously if the instance allows it (CMD_ALLOW_ANONYMOUS).

hedgedoc_create_with_aliasA

Create a new HedgeDoc note with a custom URL alias.

Requires HedgeDoc's FreeURL mode to be enabled on the instance (CMD_ALLOW_FREEURL=true).

  • alias: The custom URL slug (e.g. 'my-diagram')

  • title: The title of the note (will be added as level-1 heading)

  • content: The markdown body content Returns the note ID and URL.

hedgedoc_create_diagramA

Create a HedgeDoc note with a Mermaid diagram.

HedgeDoc 1.x renders Mermaid natively in the editor.

  • title: The title of the diagram note

  • diagram_type: The Mermaid diagram type (e.g. 'graph TD', 'sequenceDiagram', 'flowchart LR', 'classDiagram', 'gantt', 'pie')

  • diagram_code: The Mermaid diagram body (without the type header)

  • description: Optional explanatory text before the diagram Returns the note ID and URL.

hedgedoc_readA

Read the raw markdown content of a HedgeDoc note.

  • note_id: The note ID or alias (the slug from the URL)

hedgedoc_infoA

Get metadata of a HedgeDoc note (title, description, timestamps, viewcount).

  • note_id: The note ID or alias (the slug from the URL)

hedgedoc_list_revisionsA

List all available revisions of a HedgeDoc note.

Each revision entry has an id (Unix timestamp) and a length (chars). The revision-id can be used with hedgedoc_get_revision to retrieve the full content of a specific revision.

  • note_id: The note ID or alias (the slug from the URL) Returns a JSON array of revisions.

hedgedoc_get_revisionA

Get the full content and authorship of a specific revision.

  • note_id: The note ID or alias (the slug from the URL)

  • revision_id: The revision ID (Unix timestamp from hedgedoc_list_revisions) Returns JSON with the note content and authorship data at that revision.

hedgedoc_publish_urlA

Get the published (read-only) URL of a HedgeDoc note.

HedgeDoc's publish mode renders the note without the editor UI — ideal for sharing with viewers who should not edit the content.

  • note_id: The note ID or alias (the slug from the URL) Returns the published URL.

hedgedoc_slide_urlA

Get the slide presentation URL of a HedgeDoc note.

HedgeDoc can render notes designed as slides (using slide breaks) into a full-screen presentation — useful for diagrams in meetings.

  • note_id: The note ID or alias (the slug from the URL) Returns the slide URL.

hedgedoc_statusA

Get the current status of the HedgeDoc instance.

Returns JSON with:

  • note_count: Number of notes stored on the server

  • online_users: Number of (distinct) online users

  • Other instance metrics

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.9/5.0

Scored across 11 tools

Disambiguation4/5

The four create variants are distinct in their parameters (blank, content, alias, diagram), but create and create_with_alias are nearly identical except for the alias parameter, which could cause confusion. The remaining tools (read, info, status, revisions, URLs) are clearly differentiated by action.

Naming Consistency4/5

All tools share the hedgedoc_ prefix, and most follow a verb-based pattern. However, there is inconsistency: some are plain verbs (create, read), some are nouns (info, status), some are verb_noun (publish_url, list_revisions), and the create variants use a create_<variant> pattern. This is mostly predictable but not perfectly uniform.

Tool Count5/5

With 11 tools, the server is well-scoped for its purpose. Each tool covers a distinct aspect of note management, and the count is within the ideal range for a domain-specific MCP server.

Completeness2/5

The server provides strong coverage for creating and reading notes, but lacks update and delete operations, making it impossible to modify or remove notes. Additionally, there is no list-notes tool, so agents must know note IDs in advance, leaving significant gaps in the note lifecycle.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources