by yuna0x0
Integrate with HackMD API for secure document management in collaborative markdown environments. Create, update, and sha
Connects to HackMD's API to create, edit, and manage collaborative markdown documents. Lets you work with HackMD notes, teams, and user data through your MCP client.
HackMD is a community-built MCP server published by yuna0x0 that provides AI assistants with tools and capabilities via the Model Context Protocol. Integrate with HackMD API for secure document management in collaborative markdown environments. Create, update, and sha It is categorized under productivity.
You can install HackMD in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
MIT
HackMD is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
Add new capabilities to Claude beyond text generation
Example
Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Automate multi-step workflows combining AI and external tools
Example
Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Share your MCP server with the developer community
HackMD has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
According to our notes, HackMD benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
HackMD is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
I recommend HackMD for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
We wired HackMD into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
Strong directory entry: HackMD surfaces stars and publisher context so we could sanity-check maintenance before adopting.
HackMD is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
HackMD reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
We wired HackMD into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
HackMD reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
showing 1-10 of 43
A Model Context Protocol (MCP) server that interfaces with the HackMD API, allowing LLM clients to access and interact with HackMD notes, teams, user profiles, and history data.
mcp.json / claude_desktop_config.json:{
"mcpServers": {
"hackmd": {
"command": "npx",
"args": ["-y", "hackmd-mcp"],
"env": {
"HACKMD_API_TOKEN": "your_api_token"
}
}
}
}
You may also optionally set the HACKMD_API_URL environment variable if you need to use a different HackMD API endpoint.
Follow the Local Development instructions to set up the project locally, then run:
pnpm run start:http
This will start the server on port 8081 by default. You can change the port by setting the PORT environment variable.
You can deploy this MCP server to any cloud platform that supports Node.js server applications.
You can also deploy via MCP platforms like Smithery.
When using the STDIO transport or hosting the HTTP transport server, you can pass configuration via environment variables:
HACKMD_API_TOKEN: HackMD API Token (Required for all operations)HACKMD_API_URL: (Optional) HackMD API URL (Defaults to https://api.hackmd.io/v1)Environment variables applied only for the HTTP transport server:
ALLOWED_HACKMD_API_URLS: (Optional) A comma-separated list of allowed HackMD API URLs. The server will reject requests if the provide HackMD API URL is not in this list. If not set, only the default URL (https://api.hackmd.io/v1) is allowed.[!CAUTION] If you are hosting the HTTP transport server with token pre-configured, you should protect your endpoint and implement authentication before allowing users to access it. Otherwise, anyone can access your MCP server while using your HackMD token.
When using the HTTP transport, user can pass configuration via HTTP headers:
Hackmd-Api-Token: HackMD API Token (Required for all operations)Hackmd-Api-Url: (Optional) HackMD API URL (Defaults to https://api.hackmd.io/v1)If the user provides the token in the header, while the server also has HACKMD_API_TOKEN set, the header value will take precedence.
To get an API token, follow these steps:
.env file or environment variables.Can you help me manage my HackMD notes?
Please list all my notes.
Create a new note with the title "Meeting Notes" and content:
```
# Meeting Notes
Discussion points:
- Item 1
- Item 2
```
Show me all the teams I'm part of and list the notes in the first team.
This project uses pnpm as its package manager.
Clone the repository and install dependencies:
git clone https://github.com/yuna0x0/hackmd-mcp.git
cd hackmd-mcp
pnpm install
.env file by copying the example:cp env.example .env
.env file and add your HackMD API token:HACKMD_API_TOKEN=your_api_token
You can use the MCP Inspector to test and debug the HackMD MCP server:
npx @modelcontextprotocol/inspector -e HACKMD_API_TOKEN=your_api_token npx hackmd-mcp
# Use this instead when Local Development
pnpm run inspector
Then open your browser to the provided URL (usually http://localhost:6274) to access the MCP Inspector interface. From there, you can:
This is particularly useful for testing your setup before connecting it to MCP clients like Claude Desktop.
Pull from GitHub Container Registry:
docker pull ghcr.io/yuna0x0/hackmd-mcp
Docker build (Local Development):
docker build -t ghcr.io/yuna0x0/hackmd-mcp .
Docker multi-platform build (Local Development):
docker buildx build --platform linux/amd64,linux/arm64 -t ghcr.io/yuna0x0/hackmd-mcp .
To create an MCP Bundle for this server, run:
pnpm run pack:mcpb
This MCP server accepts your HackMD API token in the .env file, environment variable or HTTP header. Keep this information secure and never commit it to version control.
This project is licensed under the MIT License - see the LICENSE file for details.
Prerequisites
Time Estimate
15-60 minutes depending on server complexity
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
Compatibility
✓ Use when
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid when
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.