edge-history-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EDGE_USER_DATA_DIR | No | Override the default Edge user data directory (default is %LOCALAPPDATA%\Microsoft\Edge\User Data). |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_profilesA | List available Microsoft Edge browsing profiles. |
| get_historyA | Get Edge browsing history for a profile on a specific day. |
| get_history_summaryA | Summarize Edge browsing history for a profile on a day, by domain only. |
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 3 tools
The three tools are clearly distinct: list_profiles handles profile enumeration, get_history returns raw detailed visit entries, and get_history_summary provides an aggregated domain-level view. The descriptions explicitly explain when to use each, eliminating ambiguity.
All tool names follow a consistent verb_noun snake_case pattern. list_profiles and get_history use clear action-object phrasing, and get_history_summary extends get_history logically. No mixed conventions or vague verbs.
With only three tools, the server is tightly scoped to browsing history retrieval. Each tool earns its place: profile discovery, raw history access, and summarization. The count is neither too thin nor bloated for the purpose.
The server covers the full read-only lifecycle for Edge history: discovering profiles, fetching detailed history with pagination and time filtering, and obtaining summaries. No obvious gaps exist within the narrow domain; the tools together handle typical use cases.