mcp-for-spotlight
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 |
|---|---|
| spotlight_searchA | Durchsucht den macOS-Spotlight-Index (mdfind) nach Dateien: Volltext und Metadaten. Genau eine Suchart angeben: text (Freitext), name (Dateiname) oder query (rohe Spotlight-Abfrage). Liefert Dateipfade. Hinweis: geschützte Orte wie ~/Library/Mail liefern nur mit Full Disk Access Treffer. |
| spotlight_metadataA | Liest die von Spotlight indexierten Metadaten einer Datei (mdls). Ohne attributes alle, sonst nur die genannten (z. B. kMDItemContentType, kMDItemContentCreationDate). |
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 2 tools
The two tools have clearly distinct purposes: one searches the Spotlight index, the other reads metadata for a specific file. No meaningful overlap exists between search and metadata retrieval.
Both tools follow the consistent 'spotlight_<operation>' convention: spotlight_search and spotlight_metadata. The naming pattern is clear and predictable for a server scoped to Spotlight functionality.
With only 2 tools, the surface feels thin for a domain that could reasonably include other operations (e.g., file info, indexed-item lifecycle ops). However, the two tools cover the core search+metadata workflow reasonably for a Spotlight-focused server.
The pair covers the two primary Spotlight operations (search and metadata retrieval), which is the obvious core workflow. However, there are minor gaps—e.g., no tool for getting indexed status, no way to count results, or handling common variations like filtering by path—though agents can usually compose around these with the search tool.