Search History MCP Server
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_historyA | Search browser history for URLs and titles containing the search term. Args: search_term: The text to search for in URLs and page titles limit: Maximum number of results to return (default: 50, max: 500) browser: Which browser to search ("brave", "safari", "chrome", "firefox", "edge", "arc", "opera", or "duckduckgo") Returns: Formatted list of matching history entries with titles, URLs, and visit times |
| get_recent_historyA | Get the most recent browsing history entries. Args: limit: Maximum number of results to return (default: 50, max: 500) browser: Which browser to query ("brave", "safari", "chrome", "firefox", "edge", "arc", "opera", or "duckduckgo") Returns: Formatted list of recent history entries with titles, URLs, and visit times |
| get_most_visitedA | Get the most frequently visited sites from browser history. Args: limit: Maximum number of results to return (default: 20, max: 100) browser: Which browser to query ("brave", "safari", "chrome", "firefox", "edge", "arc", "opera", or "duckduckgo") Returns: Formatted list of most visited sites with visit counts |
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
Each tool has a clearly distinct purpose: get_most_visited retrieves frequently visited sites by visit count, get_recent_history retrieves entries by recency, and search_history performs keyword searches. There is no overlap in functionality, making tool selection unambiguous for an agent.
All tool names follow a consistent verb_noun pattern (get_most_visited, get_recent_history, search_history) using snake_case throughout. The naming is predictable and readable, with no deviations in style or convention.
Three tools are reasonable for a search history server, covering core use cases: frequency analysis, recency retrieval, and search. However, it feels slightly thin as it lacks tools for operations like deleting history or getting specific entries by ID, which could enhance completeness.
The tools cover basic querying (frequency, recency, search) but lack update or delete operations, which are common in history management. There is no tool for getting a specific entry by URL or ID, creating potential dead ends for agents needing precise retrieval beyond search.