HackMD MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HACKMD_API_URL | No | HackMD API Endpoint URL | https://api.hackmd.io/v1 |
| HACKMD_API_TOKEN | Yes | Your HackMD API token obtained from HackMD settings |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_user_infoB | Get information about the authenticated user |
| list_user_notesB | List all notes owned by the user |
| get_noteC | Get a note by its ID |
| create_noteC | Create a new note |
| update_noteC | Update an existing note |
| delete_noteC | Delete a note |
| get_historyC | Get user's reading history |
| list_teamsB | List all teams accessible to the user |
| list_team_notesC | List all notes in a team |
| create_team_noteC | Create a new note in a team |
| update_team_noteC | Update an existing note in a team |
| delete_team_noteC | Delete a note in a team |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
Every tool has a clearly distinct purpose with no ambiguity. The tools are well-organized around specific resources (notes, teams, user info, history) and actions (create, get, list, update, delete), making it easy for an agent to select the correct tool without confusion.
All tool names follow a consistent verb_noun pattern (e.g., create_note, list_teams, get_user_info). The naming is uniform across the set, with no deviations in style or convention, ensuring predictability and readability.
With 12 tools, the count is well-scoped for a HackMD server, covering core operations for notes, teams, and user management. Each tool earns its place by addressing specific needs without being excessive or insufficient for the domain.
The tool set provides complete CRUD/lifecycle coverage for notes (including team-specific variants) and teams, along with user info and history. There are no obvious gaps, enabling agents to handle all essential workflows without dead ends.