See your codebase clearly. Universal AI context generator that maps routes, schema, components, dependencies, and more for Claude Code, Cursor
Most database access work still happens through a UI a human drives. Codesight MCP server moves it into the conversation instead. See your codebase clearly. Universal AI context generator that maps routes, schema, components, dependencies, and more for Claude Code, Cursor, Copilot, Codex, and any AI coding tool.
That's it. Run it in any project root. No config, no setup, no API keys.
The server publishes 11 tools. What each one is for:
Question — Without wikicodesight_get_wiki_index — Get the wiki catalog (~200 tokens) at session startcodesight_get_wiki_article — Read one article by name: auth, database, payments, etccodesight_lint_wiki — Health check: orphan articles, missing cross-links, stale contentRetrospectives — "What went well", "Stop doing", filename: retro, retrospectiveResearch — filename: research, analysis, benchmark, comparisonProject — Manual explorationLanguage — StackDetector — SaaS A (138 files)Routes — 38Components — 0codesight on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
Plenty of database access servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Codesight's toolset — Question, codesight_get_wiki_index, codesight_get_wiki_article and 8 more — is a fair guide to whether it matches your workflow. It is maintained by houseofmvps; 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 |
|---|---|
| Question | Without wiki |
| codesight_get_wiki_index | Get the wiki catalog (~200 tokens) at session start |
| codesight_get_wiki_article | Read one article by name: auth, database, payments, etc. |
| codesight_lint_wiki | Health check: orphan articles, missing cross-links, stale content |
| Retrospectives | "What went well", "Stop doing", filename: retro, retrospective |
| Research | filename: research, analysis, benchmark, comparison |
| Project | Manual exploration |
| Language | Stack |
| Detector | SaaS A (138 files) |
| Routes | 38 |
| Components | 0 |
{
"mcpServers": {
"codesight": {
"command": "npx",
"args": ["-y", "codesight"]
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
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.