hedgedoc-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HEDGEDOC_URL | Yes | The URL of the HedgeDoc instance (e.g., https://md.example.com). | |
| HEDGEDOC_EMAIL | No | Email address for HedgeDoc login. Used for automatic re-authentication. | |
| HEDGEDOC_PASSWORD | No | Password for HedgeDoc login. Used for automatic re-authentication. | |
| HEDGEDOC_SESSION_COOKIE | No | Session 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
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| 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 |
| 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 |
| 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
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
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