compy-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COMPY_FILE | No | Path to the Compy export JSON file (can also be set via --file flag) | ~/Downloads/compy/compy-export.json |
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 | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_notesA | Search the highlights, notes and tasks the user captured on the web. Pass keywords from what you're working on to pull the relevant ones. Returns ranked matches with note text, highlighted quote, tag, URL and origin. |
| list_tasksA | List captured notes/tasks, optionally filtered by site or tag. Use when you want the full set rather than a keyword search. |
| list_sitesA | List the sites the user has notes on, with a count each. Good first call to see what's available. |
| get_noteA | Fetch a single note/task by its id (as returned by search_notes / list_tasks). |
| get_markdownC | Render the notes as a ready-to-read Markdown task list, optionally scoped to one site. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| sites | Sites with captured notes and their counts |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: rendering a markdown list, fetching a single note by ID, listing sites with counts, listing tasks with filters, and searching notes by keywords. No overlap or ambiguity.
All tool names follow a consistent verb_noun pattern using snake_case: get_markdown, get_note, list_sites, list_tasks, search_notes. This pattern is predictable and clear.
With 5 tools covering listing, searching, fetching, and rendering, the count is well-scoped for a read-only note retrieval server. It is neither too few nor too many.
The tool set provides complete coverage for reading and searching notes (list, search, get, render). However, it lacks any write operations (create, update, delete), which may be intentional but represents a gap for full note management.