obsidian-plugins
Related Servers
Alternatives to obsidian-plugins
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables AI agents to search a curated directory of Claude Code agent skills, MCP servers, and plugin marketplaces ranked by community signal.4111 npm2MIT
- FlicenseCqualityFmaintenanceProvides LLM agents with comprehensive access to Obsidian vaults via the official Obsidian CLI bridge. It enables users to read, search, and modify notes, tasks, properties, and plugins while the Obsidian desktop app is running.5416-

plugandship-mcpofficial
AlicenseAqualityCmaintenanceEnables coding agents to search an index of 22k+ MCP servers, agent skills and coding-agent plugins directly from chat, returning matches with stars, install commands and page links, plus trending repos and curated best-of topic lists. Read-only, no API key required, usable via a hosted HTTP endpoint or locally over stdio.4MIT
plugmcpofficial
AlicenseAqualityCmaintenanceEnables agents to search a directory of 70,000+ MCP servers and agent skills, compare candidates side by side, and retrieve ready-to-paste install configs for clients such as Cursor, Claude Code, VS Code, Codex, Gemini CLI, and Grok Bot. It also surfaces recently added servers and skill install commands through read-only tools.9529 npm2MIT- AlicenseBqualityDmaintenanceEnables AI agents to search an index of open source repos and tools by what they do, their callable interface (MCP, CLI, SDK, API, etc.) and OG score, plus fetch repo details, category listings, and weekly trending projects.4339 npm1MIT
- FlicenseNot gradedqualityAmaintenanceEnables natural-language search of 378 curated AI agent frameworks, developer tools, and automation repositories from inside Claude Code, Cursor, Codex, or any MCP-compatible client, returning matching repos with descriptions instead of manual GitHub browsing. Also exposes category listing, stats, and single-repo lookup.-
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.