Markdrop MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MARKDROP_API_KEY | Yes | Your Markdrop API key for authentication. | |
| MARKDROP_API_URL | No | The base URL of the Markdrop API. | http://localhost:3000 |
| MARKDROP_PROJECT_ID | No | Optional project ID to filter searches to a specific project. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_pastesA | Search through Markdrop pastes by content, title, tags, or topics. Returns matching pastes with metadata. |
| get_pasteA | Retrieve full content and metadata for a specific paste by ID |
| list_tagsA | List all available tags with their counts and categories. Useful for discovering what topics are documented. |
| get_recent_pastesA | Get recently created or modified pastes, optionally filtered by project or type |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a distinct purpose: searching, retrieving by ID, listing tags, and listing recent pastes. There is no overlap or ambiguity between them.
All tool names follow a consistent snake_case verb_noun pattern (e.g., search_pastes, get_paste, list_tags, get_recent_pastes). The naming is predictable and coherent.
With 4 tools, the server is well-scoped and focused on read/search operations. The count is within the ideal range and each tool contributes to the server's purpose.
The server only provides read and search operations; there are no create, update, or delete tools. This is a significant gap for a paste management service, as agents cannot write or manage pastes.