mcp

This MCP server provides a bridge between Inkdrop's Local HTTP Server API and the MCP ecosystem. It exposes a set of note-management tools that can be invoked via the MCP protocol, including reading notes, searching by keyword, listing notes and notebooks, and creating or updating notes and tags. The available tools include read-note, search-notes, list-notes, create-note, update-note, patch-note, list-notebooks, read-book, list-tags, read-tag, create-tag, and update-tag. You can use these tools to programmatically manage Inkdrop notes and notebooks from other MCP-enabled apps or automation pipelines. Ensure your local Inkdrop HTTP server is running and accessible at the configured INKDROP_LOCAL_SERVER_URL before starting the MCP server.

Prerequisites:

• Node.js and npm installed on your machine.
• A running Inkdrop Local HTTP Server instance.

Installation steps:

1. Ensure Inkdrop local server is configured and running, and note the URL, username, and password for authentication.
2. Install and run this MCP server via npx (as configured in the mcp_config):

# Optionally install locally first (if you prefer):
# npm install -g @inkdropapp/mcp-server  (if you want to install globally)

# Start the MCP server via your normal workflow (relying on npx per config):
# The actual startup is managed by Claude/your MCP runner using the mcp_config

3. Configure Claude Desktop (or your MCP runner) with the provided mcpServers inkdrop entry, ensuring the env vars are set to point at your Inkdrop Local Server and credentials.
4. Launch the MCP server and verify connectivity in the MCP Inspector or your application using the standard MCP protocol.

Note: The server is designed to be run via npx @inkdropapp/mcp-server with the environment variables already provided in the mcp_config. Adjust INKDROP_LOCAL_SERVER_URL, INKDROP_LOCAL_USERNAME, and INKDROP_LOCAL_PASSWORD as needed for your environment.

Tips:

• If you encounter authentication issues, verify that INKDROP_LOCAL_USERNAME and INKDROP_LOCAL_PASSWORD are correct for your Inkdrop Local HTTP Server and that the URL (INKDROP_LOCAL_SERVER_URL) is reachable from where the MCP server runs.
• The tools return truncated note bodies (up to 200 characters). Use read-note to fetch full content when needed.
• For debugging, consider using the MCP Inspector to step through tool invocations and inspect responses.
• When upgrading the MCP server package, update the mcp_config accordingly to reflect any changes in command or environment requirements.
• Ensure network access between the MCP server, Inkdrop local server, and any UI consuming the MCP outputs.

Environment variables:

• INKDROP_LOCAL_SERVER_URL: Base URL for the Inkdrop Local HTTP Server API (e.g., http://localhost:19840)
• INKDROP_LOCAL_USERNAME: Local server username
• INKDROP_LOCAL_PASSWORD: Local server password