pluggedin-app
pluggedin-app is an MCP server, listed under databases. It reaches next, nextauth, pluggedin, postgres and redis. It needs NEXTAUTH_SECRET, NEXT_SERVER_ACTIONS_ENCRYPTION_KEY, PLUGGEDIN_API_KEY, POSTGRES_PASSWORD and REDIS_PASSWORD to authenticate. Its repository has 103 GitHub stars and is licensed under MIT; we last read it on 2026-10-23.
Connects to Model Context Protocol (MCP) servers to discover, configure, and manage AI tools, workspaces, prompts, and logs from multiple sources (Claude, Cursor, etc.). Requires no specific credentials.
Install
MCP servers are packaged differently from each other -- some run via npx, some as a Docker image, some as a plain script you clone and run. pluggedin-app’s own README did not state one plainly enough for this page to quote it rather than guess, so it will not guess. The repository below states it.
What it reaches, and what it needs
What it connects to
Unverified means a mention in the server’s own description, not a citation. A wrong claim here costs nothing to correct and nothing to trust yet.
Maintenance
The Crossroads for AI Data Exchanges. A unified, self-hostable web interface for discovering, configuring, and managing Model Context Protocol (MCP) servers—bringing together AI tools, workspaces, prompts, and logs from multiple MCP sources (Claude, Cursor, etc.) under one roof.
pluggedin-app compared with similar servers
| Server | Reaches | Needs | Stars | Last update | Licence |
|---|---|---|---|---|---|
| pluggedin-app (this page) | next, nextauth, pluggedin, postgres, redis | NEXTAUTH_SECRET, NEXT_SERVER_ACTIONS_ENCRYPTION_KEY, PLUGGEDIN_API_KEY, POSTGRES_PASSWORD, REDIS_PASSWORD | 103 | 2026-10-21 | MIT |
| dbhub | mysql, postgres, sqlite(1 shared) | None listed | 3,702 | 2026-10-21 | MIT |
| tiger-cli | postgres(1 shared) | None listed | 126 | 2026-10-24 | Apache-2.0 |
| yandex-tracker-mcp | oauth, redis, tracker(1 shared) | OAUTH_CLIENT_SECRET, REDIS_PASSWORD, TRACKER_IAM_TOKEN, TRACKER_SA_PRIVATE_KEY, TRACKER_TOKEN | 123 | 2026-09-06 | Apache-2.0 |
| notifyd | jwt, notifyd, postgres, resend(1 shared) | ADMIN_API_KEY, JWT_SECRET, NOTIFYD_ADMIN_API_KEY, NOTIFYD_API_KEY, RESEND_API_KEY | 17 | 2026-10-21 | MIT |
| Easy-Postgres-MCP | postgres, postgresql(1 shared) | None listed | 13 | 2025-06-15 | — |
Ranked by services in common with pluggedin-app, then by stars. Figures are from each repository when we last read it.
Common questions about pluggedin-app
- What does pluggedin-app do?
- Connects to Model Context Protocol (MCP) servers to discover, configure, and manage AI tools, workspaces, prompts, and logs from multiple sources (Claude, Cursor, etc.). Requires no specific credentials.
- How do I install pluggedin-app?
- Its README did not state an install command plainly enough for us to quote one, so we do not guess. The repository has the instructions: https://github.com/VeriTeknik/pluggedin-app
- What does pluggedin-app connect to, and what does it need?
- It reaches next, nextauth, pluggedin, postgres and redis. The credentials we found in its source are NEXTAUTH_SECRET, NEXT_SERVER_ACTIONS_ENCRYPTION_KEY, PLUGGEDIN_API_KEY, POSTGRES_PASSWORD and REDIS_PASSWORD.
- Which AI clients can use pluggedin-app?
- Its own description mentions Cursor. That is a mention in its description, not a test we ran.
- Is pluggedin-app official and is it maintained?
- We found nothing naming it as a vendor’s official server. Its repository has 103 GitHub stars and its state in our directory is listed. Its last commit we recorded was on 2026-10-21.
- What licence does pluggedin-app use?
- The repository declares the MIT licence.
More MCP servers for databases
- CodeGraphContext4,360 stars
- dbhub3,702 stars
- mcp-server-mysql2,173 stars
- mysql_mcp_server1,402 stars
- server874 stars
- supabase-mcp-server833 stars