obsidian-plugins
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_pluginsA | Search the official Obsidian community plugin directory (~9000 plugins) by keyword over name, id, author, and description. Use this BEFORE building or proposing any Obsidian plugin or feature, to check whether it already exists, and whenever someone asks which plugin to use. Returns the total number of matches plus the top results with downloads, latest version and last-update date (an old date means possibly abandoned), sorted by downloads. |
| search_themesA | Search the official Obsidian community theme directory (~900 themes) by keyword over name and author. Use this before designing a new theme, or to recommend one. Returns the total number of matches plus repo links, supported modes (dark/light), and screenshot URLs. |
| get_pluginA | Look up one plugin by exact id (as used in the directory) and return its entry plus downloads, latest version, last-update date and number of releases. Use this to judge whether an existing plugin is alive (recent updates, many releases) or abandoned, before deciding to build, fork, or contribute. |
| top_pluginsA | List the most-downloaded community plugins, optionally filtered by keyword. Use this to see which plugins dominate a category before entering it. |
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 targets a distinct resource+action: top_plugins ranks plugins, search_plugins finds plugins by keyword, search_themes finds themes, and get_plugin fetches one plugin by exact id. The only soft overlap is between top_plugins and search_plugins, since the latter also sorts by downloads, but the descriptions clarify the ranking-overview vs existence-check use cases.
All names follow a consistent snake_case verb/qualifier + plural-noun pattern (top_plugins, search_plugins, search_themes, get_plugin). The minor deviation is the singular 'plugin' in get_plugin versus the plural elsewhere, which is a natural singular-lookup convention and still readable.
Four tools is slightly lean but well-scoped for a plugin/theme directory lookup server, with each tool earning its place. One more detail-oriented tool (e.g. get_theme) would round it out without bloat.
Plugins have full coverage (rank, search, detail lookup), but the theme side is asymmetric: there is no get_theme or way to fetch a single theme's full details, and no browsing by author or category. These are workable-around gaps via search, but notable for the stated directory domain.