Toskar
Related Servers
Alternatives to Toskar
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceA local MCP server that lets AI hosts like Claude Desktop, Cursor, or Cline query a hybrid vector + BM25 index of your scattered notes, project docs, PDFs, and chat exports, returning answers with section-level citations. It exposes eight tools, resources, and prompts so agents can search, ask, and walk links across all your source directories at once.-
- AlicenseNot gradedqualityAmaintenanceLocal-first knowledge base MCP server. Lets AI agents (Claude Code, Cursor, etc.) read and write your personal knowledge base through 20 MCP tools. Zero cloud dependency — all files stay on your machine.1,758 npm679MIT
- AlicenseNot gradedqualityDmaintenanceA private, local-first MCP server that gives any AI long-term memory — its own diary. Zero models, zero network, zero subscription; smarter search than Notion, running entirely on your machine.MIT
- FlicenseNot gradedqualityCmaintenanceMCP server that provides a portable personal knowledge layer for AI tools, enabling cross-LLM continuity and personalized context across clients like Claude, ChatGPT, and Cursor.-
- FlicenseNot gradedqualityDmaintenanceMCP server that enables AI to read, search, and edit local files securely without external data exposure, using local LLMs via Ollama and integrating with Open WebUI or Claude Desktop.-
- AlicenseNot gradedqualityDmaintenanceA local-first MCP server that indexes all your local files (text, code, images, audio, video) and provides hybrid search (BM25+embeddings) to retrieve only relevant chunks for AI tools, reducing token usage by over 57%.23AGPL 3.0
TDQS
Scored across 3 tools
Each tool has a distinct core action: ask (query the AI), list (enumerate models), search (retrieve passages). There is some overlap because ask_local_ai may internally read connected knowledge, which an agent could confuse with search_my_knowledge, but the descriptions clarify the intended split.
All three tools use a consistent snake_case verb_noun pattern (ask_local_ai, list_local_models, search_my_knowledge), making the set highly predictable.
Three tools is on the lean side but fits the narrow scope of a local AI assistant: query, enumerate models, and search knowledge. Nothing feels redundant, though the surface is minimal.
The core lifecycle (ask, list models, search knowledge) is covered, but there are notable gaps: no way to inspect a specific model's details, list connected knowledge sources, or manage them. Agents can partly work around this via ask_local_ai, but coverage feels thin.