mcp-server
Provides an MCP (Model Context Protocol) server that exposes Inkdrop’s Local HTTP Server API as MCP tools, enabling agents to list/search/read/create/update/patche notes, notebooks, and tags via stdio.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Uses username/password for the local HTTP server passed via environment variables. No evidence provided about TLS enforcement, fine-grained scopes, or safe logging practices. Since it connects to a local endpoint, security largely depends on how the local server is configured (HTTPS vs HTTP, network exposure) and whether credentials are protected from logs/process inspection.
⚡ Reliability
Best When
You have Inkdrop running with the Local HTTP Server enabled and you want agent tool access through MCP (e.g., Claude Desktop + MCP Inspector).
Avoid When
You cannot control/secure the local endpoint (host/port, credentials) or you need strong auditability/authorization beyond the local server’s capabilities.
Use Cases
- • Agent-assisted note retrieval and summarization from an Inkdrop local database
- • Keyword search and filtering of Inkdrop notes (with follow-up reads for full content)
- • Automated note creation/updating in Inkdrop from a conversational workflow
- • Tag/book management for structured knowledge organization in Inkdrop
Not For
- • Using as a public remote API service (it is intended to connect to a local Inkdrop Local HTTP Server)
- • Handling sensitive notes without properly securing the local Inkdrop HTTP server and credentials
- • Bulk high-volume operations without considering rate limits and performance constraints
Interface
Authentication
Auth is delegated to the Inkdrop Local HTTP Server. The MCP server configuration passes local username/password via env vars.
Pricing
No pricing information provided; appears to be a local/open-source style integration.
Agent Metadata
Known Gotchas
- ⚠ Tool results like search/list notes appear to include truncated note bodies (200 chars); agents should call read-note for full content.
- ⚠ Some update operations require CouchDB-style MVCC fields (e.g., _rev for update-tag/update-note/patch-note), so agents must first read to get the current revision before updating.
- ⚠ For patch-note, old_string must match exactly one occurrence with sufficient surrounding context; otherwise the patch may fail.
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for mcp-server.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-03-30.