parchmark-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PARCHMARK_URL | Yes | API base URL for ParchMark | |
| PARCHMARK_PASSWORD | Yes | Your password | |
| PARCHMARK_USERNAME | Yes | Your username |
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 |
|---|---|
| tasks | {
"list": {},
"cancel": {},
"requests": {
"tools": {
"call": {}
},
"prompts": {
"get": {}
},
"resources": {
"read": {}
}
}
} |
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_notesA | List all notes for the authenticated user. Returns note metadata (id, title, timestamps) without content. Use get_note to retrieve full content for a specific note. |
| get_noteA | Get a specific note by ID with full content. Args: note_id: The unique identifier of the note (e.g., "note-1234567890") |
| create_noteA | Create a new note with markdown content. The note title is automatically extracted from the first H1 heading. Args: content: Markdown content for the note (should start with # Title) |
| update_noteA | Update an existing note's content. The note title is automatically re-extracted from the first H1 heading. Args: note_id: The unique identifier of the note to update content: New markdown content for the note |
| delete_noteB | Delete a note by ID. Args: note_id: The unique identifier of the note to delete |
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 5 tools
Each tool has a completely distinct role: listing metadata, retrieving full content, creating, updating, and deleting. No overlap or ambiguity exists.
All tool names follow a strict verb_noun pattern (list_notes, get_note, create_note, update_note, delete_note), making the API highly predictable.
With exactly 5 tools covering a notes CRUD lifecycle, the server is well-scoped without redundancy or excess.
The full CRUD cycle is present: list/get for reading, create, update, and delete. No essential operation for a notes domain is missing.