A personal RAG database you build from chat, so AI creates work that sounds like you.
If you already use MyAITwin, the myaitwin mcp server is the piece that lets your assistant work with it directly. A personal RAG database you build from chat, so AI creates work that sounds like you.
A personal RAG database and semantic search engine you build and control from inside your AI chat. Store your knowledge, voice, and skills as you work. Retrieve them in seconds, source always cited. Your AI then creates output that is recognisably you, in every conversation.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
add_knowledge — Store a typed, tagged knowledge itemadd_voice_note — Store a voice note transcript with automatic extractionadd_document — Store a long document with automatic chunkingadd_from_url — Fetch and store a web pageadd_reference_record — Store a creation event linking knowledge and skills usedsearch_twin — Semantic search across all knowledgesearch_for_creation — Dual search returning skills and knowledge separatelyget_by_type — Retrieve all items of a specific typeget_by_tag — Retrieve all items with a specific taglist_recent — List recently added itemsget_schema — Overview of your types and how many items you haveget_sources — List all source documentsSetup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.
Among the database access options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. MyAITwin's toolset — add_knowledge, add_voice_note, add_document and 11 more — is a fair guide to whether it matches your workflow. It is maintained by com.lutolearn; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| add_knowledge | Store a typed, tagged knowledge item |
| add_voice_note | Store a voice note transcript with automatic extraction |
| add_document | Store a long document with automatic chunking |
| add_from_url | Fetch and store a web page |
| add_reference_record | Store a creation event linking knowledge and skills used |
| search_twin | Semantic search across all knowledge |
| search_for_creation | Dual search returning skills and knowledge separately |
| get_by_type | Retrieve all items of a specific type |
| get_by_tag | Retrieve all items with a specific tag |
| list_recent | List recently added items |
| get_schema | Overview of your types and how many items you have |
| get_sources | List all source documents |
| find_patterns | Surface recurring patterns across your knowledge |
| synthesise | Synthesise across multiple knowledge items on a topic |
Read-only SQL access to Postgres — let your assistant inspect schemas and answer questions from real data.
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Official MongoDB server covering data, schemas and Atlas management — from find queries to spinning up clusters.
Serverless Postgres with database branching — point your assistant at Neon and let it work on disposable copies.