Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
HEDGEDOC_URLYesThe URL of the HedgeDoc instance (e.g., https://md.example.com).
HEDGEDOC_EMAILNoEmail address for HedgeDoc login. Used for automatic re-authentication.
HEDGEDOC_PASSWORDNoPassword for HedgeDoc login. Used for automatic re-authentication.
HEDGEDOC_SESSION_COOKIENoSession cookie obtained from the login command. Used for authentication.

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
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
hedgedoc_create_noteA

Create a new note on the HedgeDoc instance. Returns JSON with two fields: 'note_id' (the unique identifier / URL slug) and 'url' (the full URL where the note can be viewed or shared). Use alias to assign a human-readable slug such as 'q3-research-notes' — alias-based notes can later be overwritten with hedgedoc_update_note. Notes created without an alias get a random ID and cannot be updated over HTTP. Alias support requires FreeURL mode enabled on the server (CMD_ALLOW_FREEURL=true).

hedgedoc_read_noteA

Fetch the raw markdown content of an existing note by its ID or alias. Returns the note's markdown as a plain string. This is a public endpoint — no authentication is required to read notes on instances that allow public access.

hedgedoc_update_noteA

Overwrite the entire content of an existing note. IMPORTANT: this only works for notes that were originally created with a custom alias (via hedgedoc_create_note's alias parameter). HedgeDoc 1.x has no REST update endpoint for random-ID notes — those can only be edited live in the browser. If the target note was created without an alias, this call will fail. The update is a full overwrite — partial/patch updates are not supported.

hedgedoc_note_infoA

Get metadata for a note. Returns JSON with: 'title' (string), 'description' (string or null), 'viewcount' (integer — total views), 'createtime' and 'updatetime' (ISO 8601 timestamps, e.g. '2026-08-16T10:30:00.000Z'). This is a public endpoint — no authentication required.

hedgedoc_whoamiA

Verify the current session is valid and return the logged-in user's profile. Returns JSON with user info (name, email, photo, provider, etc.). Call this to confirm the server is correctly authenticated before attempting write operations, or to identify which account is active.

hedgedoc_list_historyA

List the logged-in user's recently viewed and pinned notes. Returns a JSON array of note objects. Each object includes: 'id' (note ID or alias), 'text' (note title), 'tags' (array of strings), 'pinned' (boolean), and 'time' (last-viewed timestamp in milliseconds). Requires a valid session — will raise an error if not authenticated.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mrsunglasses-experiments/hedgedoc-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server