GravityPort
Related Servers
Alternatives to GravityPort
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to semantically search your entire local conversation history from Claude Desktop, ChatGPT and Claude Code, and to retrieve, browse, ingest and report on those conversations. All embeddings run locally, so no cloud, API keys, or data leave your machine.2MIT
- AlicenseNot gradedqualityDmaintenanceEnables Claude Desktop to search and query personal document collections (PDF, Word, Markdown, text) using semantic search and conversational AI with full context preservation across exchanges.MIT
- FlicenseNot gradedqualityDmaintenanceEnables semantic search and conversational querying across a personal research library of PDFs, DOCX, and other documents using a vector database. It provides tools for document summarization, finding related papers, and high-accuracy retrieval for AI clients like Claude Desktop.-
- AlicenseNot gradedqualityDmaintenanceEnables Claude Code to index and semantically search through PDFs, code, and documents with exact citations and zero hallucinations.MIT

MyAITwin MCPofficial
FlicenseNot gradedqualityCmaintenancePersonal RAG database and semantic search built from inside your AI chat. Store knowledge, voice, and skills; Claude and ChatGPT create work that sounds like you.-- AlicenseNot gradedqualityBmaintenanceEnables saving bookmarks, notes, and files from inside Claude Code or Codex and later finding them from any project or session just by describing what you remember. All storage, indexing, and natural-language search run locally via SQLite and a bundled embedding model, with no accounts, cloud, or API keys.4 npmMIT
TDQS
Scored across 25 tools
Most tools map to a distinct resource+action, with clear groupings around assets, stacks, and generations. The main friction is between asset_version_history, asset_recipe_history, and asset_get, which all read some form of asset history/recipe and could be confused, plus asset_update_metadata vs asset_attach_prompt which both mutate recipe data.
Every tool follows a strict resource-prefix + action pattern (asset_*, stack_*, generation_*) in snake_case with no deviations. The prefixes themselves act as a natural taxonomy, making the surface highly predictable.
25 tools is at the heavy end for a single server and pushes against the comfortable 3-15 range. The three domains (assets, stacks, generations) justify some breadth, but several near-duplicate history/recipe readers suggest the surface could be trimmed.
Coverage is strong: assets have create/import/list/search/get/trash/restore/duplicate/version/prompt/provenance, stacks have full create/add/remove/rename/dissolve/get/list, and generations have record/relation/lineage/list. Minor gaps exist, such as no permanent purge, no stack cover/ordering update, and no generation edit/delete operations.