Every day, you have brilliant conversations with AI - strategy sessions with GPT-4, code reviews with Claude, analysis with Gemini. But when you
Every day, you have brilliant conversations with AI - strategy sessions with GPT-4, code reviews with Claude, analysis with Gemini. But when you close that chat window, all that knowledge vanishes. **This is the "AI knowledge evaporation". The pluggedin app mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 14 defined tools rather than through you.
Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
Everything the assistant can do here goes through one of these:
pluggedin-migrate — One-shot DB migration; reuses the app image, then exitspluggedin-app — Main web application (host port 12005 → container 3000),pluggedin-postgres — PostgreSQL 18 + pgvector database (port 5432)pluggedin-redis — Redis 7 (port 6379)zvec-data — Vector collections (persistent)app-uploads — User uploaded files (persistent)app-logs — Application logs (persistent)mcp-cache — MCP package cache (persistent)Auto-Discovery — Find and configure servers from GitHub, npm, SmitheryEnd-to — End Encryption**: AES-256-GCM for all sensitive dataPer — Profile Encryption**: Isolated encryption keys per workspaceMulti — Hub Architecture**: Organize projects into separate hubsYou will need 8 environment variables: PLUGGEDIN_API_KEY, NEXTAUTH_SECRET, DATABASE_URL, REDIS_URL, NEXTAUTH_URL, NEXT_SERVER_ACTIONS_ENCRYPTION_KEY, ZVEC_DATA_PATH, EMAIL_SERVER_HOST. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
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. Pluggedin App's toolset — pluggedin-migrate, pluggedin-app, pluggedin-postgres and 11 more — is a fair guide to whether it matches your workflow. It is maintained by VeriTeknik; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Pluggedin App's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| pluggedin-migrate | One-shot DB migration; reuses the app image, then exits |
| pluggedin-app | Main web application (host port 12005 → container 3000), |
| pluggedin-postgres | PostgreSQL 18 + pgvector database (port 5432) |
| pluggedin-redis | Redis 7 (port 6379) |
| zvec-data | Vector collections (persistent) |
| app-uploads | User uploaded files (persistent) |
| app-logs | Application logs (persistent) |
| mcp-cache | MCP package cache (persistent) |
| Auto-Discovery | Find and configure servers from GitHub, npm, Smithery |
| End-to | End Encryption**: AES-256-GCM for all sensitive data |
| Per | Profile Encryption**: Isolated encryption keys per workspace |
| Multi | Hub Architecture**: Organize projects into separate hubs |
| Cline | VS Code extension for AI-assisted development |
| Project | scoped isolation with per-field filter validation |
{
"mcpServers": {
"pluggedin": {
"command": "npx",
"args": ["-y", "@pluggedin/pluggedin-mcp-proxy@latest"],
"env": {
"PLUGGEDIN_API_KEY": "YOUR_API_KEY"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| PLUGGEDIN_API_KEY | Credential the server authenticates with. | Yes |
| NEXTAUTH_SECRET | Credential the server authenticates with. | Yes |
| DATABASE_URL | Endpoint or connection string the server talks to. | Yes |
| REDIS_URL | Endpoint or connection string the server talks to. | Yes |
| NEXTAUTH_URL | Endpoint or connection string the server talks to. | Yes |
| NEXT_SERVER_ACTIONS_ENCRYPTION_KEY | Credential the server authenticates with. | Yes |
| ZVEC_DATA_PATH | Filesystem location the server is allowed to use. | Optional |
| EMAIL_SERVER_HOST | Endpoint or connection string the server talks to. | Optional |
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.