Inkdropapp Mcp Server

Created By
andyciggya year ago
Overview

what is Inkdrop MCP Server?

Inkdrop MCP Server is a server implementation for the Model Context Protocol, designed to work with the Inkdrop Local HTTP Server API, enabling users to manage their notes effectively.

how to use Inkdrop MCP Server?

To use the Inkdrop MCP Server, set up a local HTTP server and configure the server settings in the Claude Desktop application. Follow the installation guide to add the necessary configurations.

key features of Inkdrop MCP Server?

  • Retrieve, create, update, and list notes using various commands.
  • Advanced search capabilities to find notes by keywords and tags.
  • Debugging support through the MCP Inspector for better troubleshooting.

use cases of Inkdrop MCP Server?

  1. Managing personal notes and to-do lists.
  2. Organizing research notes with tags and notebooks.
  3. Collaborating on notes with team members using shared configurations.

FAQ from Inkdrop MCP Server?

  • What is the Model Context Protocol?

It is a protocol designed to facilitate communication between applications and services, particularly for managing context-aware data.

  • Is the Inkdrop MCP Server free to use?

Yes! The server is open-source and free to use.

  • How can I debug issues with the server?

You can use the MCP Inspector for debugging and monitoring server logs.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
andyciggy
Star
0
Language
JavaScript
License
Apache-2.0 license
Category
note-taking

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago