Openflowkit MCP vs Memi
A side-by-side look at the Openflowkit MCP and Memi MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Openflowkit MCP for architecture & design work; choose Memi for architecture & design as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Openflowkit MCP when
- You need dedicated capabilities in the Architecture & Design domain.
Choose Memi when
- You need dedicated capabilities in the Architecture & Design domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Architecture & Design | Architecture & Design |
| Quality signal | 37/100 · Fair | 59/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 868 | 47 |
| Directory activity | 0 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Openflowkit MCP | View Memi |
Tools & capabilities
Openflowkit MCP tools
No tool names declared yet. Check the project README from the listing page.
Memi tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Openflowkit MCP
No confirmed install command for Openflowkit MCP yet — follow the setup steps linked from its listing page rather than a guessed package name.
Memi
{
"mcpServers": {
"sarveshsea-memi": {
"command": "npx",
"args": [
"-y",
"@memi-design/cli@latest"
]
}
}
}
Frequently asked questions
Openflowkit MCP is categorized under Architecture & Design and uses an install path we have not confirmed yet. Memi belongs to Architecture & Design and uses a local stdio subprocess. Pick Openflowkit MCP for architecture & design work and Memi for architecture & design.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Openflowkit MCP has no confirmed install command yet — follow its own setup instructions.
Openflowkit MCP has no declared pricing — check the project's own site. Memi is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add openflowkit-mcp-2 and sarveshsea-memi as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Openflowkit MCP has a quality signal of 37/100 (Fair) with 0 views, 0 installs and 868 GitHub stars. Memi has 59/100 (Good) with 2 views, 0 installs and 47 GitHub stars.