MCP Server Inkdropapp MCP Server

Inkdrop Model Context Protocol Server

Local serverstdio

What is the MCP Server Inkdropapp MCP server?

Most planning and project tracking work still happens through a UI a human drives. MCP Server Inkdropapp MCP server moves it into the conversation instead. Inkdrop Model Context Protocol Server.

The short version

  1. Set up a local HTTP server

Getting it running

Installation goes through your MCP client rather than a global install: point it at @modelcontextprotocol/inspector on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

The tools it exposes

The server publishes 14 tools. What each one is for:

  • noteId — The ID of the note to retrieve. It can be found as _id in the note docs. It always starts with note:
  • includeTemplate — When true and the note has a sourceTemplateId, also fetch that template and embed its body (fill-out instructions and examples) as an extra text
  • Note — If the note was created from a template, the response includes a resource link to its source template, whose body holds the fill-out instructions and
  • keyword — Keyword to search for
  • bookId — The notebook ID. It always starts with 'book:'
  • tagIds — An array of tag IDs to filter. Each starts with 'tag:'
  • sort — Sort field (updatedAt, createdAt, or title). Default: updatedAt
  • descending — Reverse the order of output. Default: true
  • title — The note title
  • body — The content of the note in Markdown
  • status — The note status (none, active, onHold, completed, dropped)
  • tags — An array of tag IDs to assign to the note. Each must start with 'tag:'

What it needs from you

Configuration is passed through the environment: INKDROP_LOCAL_SERVER_URL, INKDROP_LOCAL_USERNAME, INKDROP_LOCAL_PASSWORD. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch MCP Server Inkdropapp.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

How it compares

Among the planning and project tracking options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. MCP Server Inkdropapp's toolset — noteId, includeTemplate, Note and 11 more — is a fair guide to whether it matches your workflow. It is maintained by inkdropapp; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against MCP Server Inkdropapp's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Available tools

ToolWhat it does
noteIdThe ID of the note to retrieve. It can be found as _id in the note docs. It always starts with note:.
includeTemplateWhen true and the note has a sourceTemplateId, also fetch that template and embed its body (fill-out instructions and examples) as an extra text block. Default: false.
NoteIf the note was created from a template, the response includes a resource link to its source template, whose body holds the fill-out instructions and examples.
keywordKeyword to search for.
bookIdThe notebook ID. It always starts with 'book:'.
tagIdsAn array of tag IDs to filter. Each starts with 'tag:'.
sortSort field (updatedAt, createdAt, or title). Default: updatedAt.
descendingReverse the order of output. Default: true.
titleThe note title.
bodyThe content of the note in Markdown.
statusThe note status (none, active, onHold, completed, dropped).
tagsAn array of tag IDs to assign to the note. Each must start with 'tag:'.
old_stringThe exact text to find in the note body. Must match exactly one occurrence. Include enough surrounding context to ensure a unique match.
new_stringThe text to replace old_string with. Use an empty string to delete the matched text.

How to install the MCP Server Inkdropapp MCP server

{
  "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"
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
INKDROP_LOCAL_SERVER_URLEndpoint or connection string the server talks to.Yes
INKDROP_LOCAL_USERNAMEConfiguration value read at startup.Optional
INKDROP_LOCAL_PASSWORDConfiguration value read at startup.Optional

Example prompts to try

  • Use MCP Server Inkdropapp to noteId.
  • Use MCP Server Inkdropapp to includeTemplate.
  • Use MCP Server Inkdropapp to Note.

Frequently asked questions

Node.js (installed via `npx`) and a running Inkdrop local HTTP server (requires Inkdrop desktop app with the plugin enabled).