edge-favorites-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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_favoritesA | Search Edge browser favorites/bookmarks by keyword. Matches against name, URL, and folder path. Tip: after getting results, use read_favorite_content on interesting URLs to get more context about what each link contains. |
| list_favoritesB | List all Edge browser favorites, optionally filtered by folder path. |
| list_foldersA | List all unique folder paths in Edge favorites. |
| read_favorite_contentA | Fetch the content of a favorite's URL to get more context about the page. Best effort: may fail for pages requiring authentication. Returns extracted text content. |
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 clear, distinct purpose: listing favorites (optionally filtered by folder), listing folders, reading content of a favorite's URL, and searching favorites. There is no ambiguity or overlap between them.
All tool names follow a consistent verb_noun pattern in snake_case (list_favorites, list_folders, read_favorite_content, search_favorites), making it easy for an agent to infer functionality.
With 4 tools, the server is well-scoped for browsing and searching Edge favorites. Each tool serves a distinct need without unnecessary redundancy or missing essential operations for the stated purpose.
The tools cover core exploration use cases (list, search, read content) but lack editing capabilities (add, delete, update favorites). For a read-only exploration server, this is a minor gap; however, full CRUD would be more complete.