@memlane/mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MEMLANE_API_KEY | Yes | Your Memlane API key | |
| MEMLANE_API_URL | No | The Memlane API URL | https://api.memlane.io |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_savesC | Semantic search over your saved links and notes in Memlane |
| list_savesC | List saved links and notes, newest first |
| get_saveB | Get a saved link or note by id, optionally including full markdown content |
| capture_urlB | Save a URL to Memlane (background enrichment: extract, embed, classify) |
| create_noteC | Create a markdown note in Memlane |
| update_noteB | Update a note's title and/or markdown body |
| list_projectsA | List Memlane projects |
| list_topicsB | List Memlane topics (general and project-scoped) |
| add_topic_to_saveC | Attach a topic to a saved link or note |
| remove_topic_from_saveC | Remove a topic from a saved link or note |
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 10 tools
Each tool targets a distinct action (capture, create, update, get, list, search, add/remove topic) on distinct resources (saves, notes, topics, projects). No overlap or ambiguity.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., capture_url, list_saves, remove_topic_from_save). No mixing of conventions.
With 10 tools covering core operations for save/note management, topic organization, and project listing, the count is well-scoped and appropriate for the server's purpose.
Notable gaps: no delete tool for saves/notes, no create or update tools for topics or projects. The surface covers basic CRUD for notes and saves but misses lifecycle operations.