A powerful knowledge management system that forges wisdom from experiences, insights, and best practices. Built with Qdrant vector database for
A powerful knowledge management system that forges wisdom from experiences, insights, and best practices. Built with Qdrant vector database for efficient knowledge storage and retrieval. That is what the wisdomforge mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
The server publishes 11 tools. What each one is for:
DATABASE_TYPE — Choose your vector database (qdrant or chroma)COLLECTION_NAME — Name of your vector collectionQDRANT_URL — URL of your Qdrant instance (required if using Qdrant)QDRANT_API_KEY — API key for Qdrant (required if using Qdrant)CHROMA_URL — URL of your Chroma instance (required if using Chroma)HTTP_SERVER — Set to true to enable HTTP server modePORT — Port number for local development only (default: 3000). Not used in Smithery cloud deploymentYOUR_API_KEY — Your Smithery API keyYOUR_COLLECTION_NAME — Your Qdrant collection nameYOUR_QDRANT_URL — Your Qdrant instance URLYOUR_QDRANT_API_KEY — Your Qdrant API keyConfiguration is passed through the environment: QDRANT_URL, QDRANT_API_KEY, CHROMA_URL, YOUR_API_KEY, YOUR_QDRANT_URL, YOUR_QDRANT_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
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. WisdomForge's toolset — DATABASE_TYPE, COLLECTION_NAME, QDRANT_URL and 8 more — is a fair guide to whether it matches your workflow. It is maintained by hadv; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against WisdomForge's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| DATABASE_TYPE | Choose your vector database (qdrant or chroma) |
| COLLECTION_NAME | Name of your vector collection |
| QDRANT_URL | URL of your Qdrant instance (required if using Qdrant) |
| QDRANT_API_KEY | API key for Qdrant (required if using Qdrant) |
| CHROMA_URL | URL of your Chroma instance (required if using Chroma) |
| HTTP_SERVER | Set to true to enable HTTP server mode |
| PORT | Port number for local development only (default: 3000). Not used in Smithery cloud deployment. |
| YOUR_API_KEY | Your Smithery API key |
| YOUR_COLLECTION_NAME | Your Qdrant collection name |
| YOUR_QDRANT_URL | Your Qdrant instance URL |
| YOUR_QDRANT_API_KEY | Your Qdrant API key |
{
"mcpServers": {
"wisdomforge": {
"command": "/bin/zsh",
"args": [
"/path/to/wisdomforge/run-wisdomforge-mcp.sh"
]
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| QDRANT_URL | Endpoint or connection string the server talks to. | Yes |
| QDRANT_API_KEY | Credential the server authenticates with. | Yes |
| CHROMA_URL | Endpoint or connection string the server talks to. | Yes |
| YOUR_API_KEY | Credential the server authenticates with. | Yes |
| YOUR_QDRANT_URL | Endpoint or connection string the server talks to. | Yes |
| YOUR_QDRANT_API_KEY | Credential the server authenticates with. | Yes |
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.