retrace-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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_textA | Full-text search across OCR'd screen content. Args:
query: FTS5 match expression, e.g. |
| list_segmentsA | List capture segments (one contiguous stretch in one app window). Args: start: Optional ISO 8601 local lower bound on segment start. end: Optional ISO 8601 local upper bound on segment start. bundle_id: Optional single app bundle ID to filter to. limit: 1-100, default 20. |
| get_frameA | Fetch one frame with its OCR text boxes and parent segment context. Box geometry (leftX, topY, width, height) is expressed as normalised fractions of the frame, in the range 0.0-1.0 — not pixels. Multiply by the video's width/height to get pixel coordinates. Args: frame_id: The frame's numeric id. limit: Max OCR node boxes to return, 1-100, default 20. |
| app_usageA | Time spent per app over a window, from summed segment durations. Args: start: ISO 8601 local start of the window. end: ISO 8601 local end of the window. limit: 1-100, default 20. |
| list_tagsA | List segment tags and how many (visible) segments carry each. Args: limit: 1-100, default 20. |
| segments_by_tagA | List segments carrying a given tag name. Args: tag: Exact tag name, as returned by list_tags. limit: 1-100, default 20. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/calvingunther66/retracemcpclaude'
If you have feedback or need assistance with the MCP directory API, please join our Discord server