Inkdrop

Inkdrop Model Context Protocol Server
  • javascript

49

GitHub Stars

javascript

Language

6 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

You run an MCP server that exposes Inkdrop’s Local HTTP Server API through a Model Context Protocol interface. This lets your MCP clients read and manage Inkdrop notes, notebooks, and tags from the local Inkdrop server in a structured, programmable way.

How to use

Launch the Inkdrop MCP Server as a local stdio process and connect your MCP client to the provided local URL. You can perform typical operations like listing notebooks, searching notes, reading and updating notes, and managing tags and tag colors. The server runs locally and exposes endpoints for the Inkdrop data model through the MCP interface.

How to install

Prerequisites: ensure you have Node.js and npm installed on your machine.

  1. Set up a local HTTP server as Inkdrop runs a local API.

  2. Add the MCP server configuration to your client so it can start and route requests to Inkdrop.

  3. Create or update the MCP client configuration file with the following JSON snippet. This config runs the MCP server locally via npx and provides the local Inkdrop server URL and credentials for access.

{
  "mcpServers": {
    "inkdrop": {
      "command": "npx",
      "args": ["-y", "@inkdropapp/mcp-server"],
      "env": {
        "INKDROP_LOCAL_SERVER_URL": "http://localhost:19840",
        "INKDROP_LOCAL_USERNAME": "your-local-server-username",
        "INKDROP_LOCAL_PASSWORD": "your-local-server-password"
      }
    }
  }
}

Additional sections

Configuration details show how to run and access the Inkdrop MCP Server locally, how to debug, and how to observe logs. Use the local URL provided in the environment variables to connect your MCP client.

Debugging and logs help you diagnose issues during development. You can run the MCP Inspector to debug the server and watch logs for real-time information.

# Start the MCP Inspector for debugging
npx @modelcontextprotocol/inspector "./dist/index.js"

To monitor runtime logs for Inkdrop MCP Server, tail the log file used by your client environment.

tail -n 20 -f ~/Library/Logs/Claude/mcp-server-inkdrop.log

Available tools

read-note

Retrieve the complete contents of a note by its ID from the database. Requires noteId starting with note:.

search-notes

List all notes containing a given keyword. Results include truncated bodies; use read-note for full content. Supports qualifiers like book:, tag:, status:, title:.

list-notes

List notes within a specified notebook with optional tag filters, keyword, and sorting options. Bodies are truncated in results; use read-note for full content.

create-note

Create a new note in a specified notebook or trash with a title and Markdown body. Optional status and tags may be provided.

update-note

Update an existing note by ID and revision, including title, body, and optional status and tags.

list-notebooks

Retrieve a list of all notebooks.

read-book

Retrieve a single notebook by its ID.

list-tags

Retrieve a list of all tags.

read-tag

Retrieve a single tag by its ID.

create-tag

Create a new tag with a name and optional color.

update-tag

Update an existing tag by ID and revision, including its name and optional color.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational