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 | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/TejGandham/parchmark-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server