HackMD MCP server

HackMD MCP Server

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.

Features

• Get user profile information
• Create, read, update, and delete notes
• Manage team notes and collaborate with team members
• Access reading history
• List and manage teams
• Dual transport support: Both HTTP and STDIO transports
• Cloud deployment ready: Support Smithery and other platforms

Requirements

• Node.js 18+

Local Installation (STDIO Transport)

1. Add this server to your mcp.json / claudedesktopconfig.json:

{
  "mcpServers": {
    "hackmd": {
      "command": "npx",
      "args": ["-y", "hackmd-mcp"],
      "env": {
        "HACKMD_API_TOKEN": "your_api_token"
      }
    }
  }
}

You may also optionally set the HACKMDAPIURL environment variable if you need to use a different HackMD API endpoint.

1. Restart your MCP client (e.g., Claude Desktop)
2. Use the tools to interact with HackMD

Server Deployment (HTTP Transport)

Self-Hosting

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.

Cloud Deployment

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.

Configuration

Environment Variables (STDIO Transport and HTTP Transport server where host provides the config)

When using the STDIO transport or hosting the HTTP transport server, you can pass configuration via environment variables:

• HACKMDAPITOKEN: HackMD API Token (Required for all operations)
• HACKMDAPIURL: (Optional) HackMD API URL (Defaults to https://api.hackmd.io/v1)

Environment variables applied only for the HTTP transport server:

• ALLOWEDHACKMDAPI_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.

HTTP Headers (HTTP Transport where user provides the config)

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 HACKMDAPITOKEN set, the header value will take precedence.

Get a HackMD API Token

To get an API token, follow these steps:

1. Go to HackMD settings.
2. Click on "Create API Token".
3. Copy the generated token and use it in your .env file or environment variables.

Available Tools

Profile Tools

• getuserinfo: Get information about the authenticated user

Teams Tools

• listteams**: List all teams accessible to the user

History Tools

• gethistory**: Get user's reading history

Team Notes Tools

• listteamnotes: List all notes in a team
• createteamnote: Create a new note in a team
• updateteamnote: Update an existing note in a team
• deleteteamnote: Delete a note in a team

Shortened. The full README is on GitHub.