A workflow management system for AI-assisted development, similar to Jira or Azure DevOps. Supports both API-driven interactions and Model Context
A workflow management system for AI-assisted development, similar to Jira or Azure DevOps. Supports both API-driven interactions and Model Context Protocol for seamless AI agent integration. The projectflow mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 2 defined tools rather than through you.
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.
Everything the assistant can do here goes through one of these:
Prerequisites — The Prerequisites tool exposed by this serverBuilding — The Building tool exposed by this serverYou will need 7 environment variables: STORAGE_DIR, LLM_PROVIDER, LLM_OLLAMA_MODEL, LLM_API_KEY, LLM_MODEL, LLM_BASE_URL, LLM_OLLAMA_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. Projectflow's toolset — Prerequisites, Building — is a fair guide to whether it matches your workflow. It is maintained by aykay76; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Projectflow's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| Prerequisites | The Prerequisites tool exposed by this server. |
| Building | The Building tool exposed by this server. |
2. **Configure VS Code MCP:**
```json
{
"mcpServers": {
"projectflow": {
"command": "go",
"args": ["run", "/path/to/projectflow/cmd/mcp-server/main.go"],
"env": {
"STORAGE_DIR": "./.projectflow/data"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| STORAGE_DIR | Filesystem location the server is allowed to use. | Optional |
| LLM_PROVIDER | Configuration value read at startup. | Optional |
| LLM_OLLAMA_MODEL | Configuration value read at startup. | Optional |
| LLM_API_KEY | Credential the server authenticates with. | Yes |
| LLM_MODEL | Configuration value read at startup. | Optional |
| LLM_BASE_URL | Endpoint or connection string the server talks to. | Yes |
| LLM_OLLAMA_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.