Vertical Flows vs io.github.oktopeak/clio-mcp
Vertical Flows is an MCP server published by verticalflows.com. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.oktopeak/clio-mcp is an MCP server published by oktopeak. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-08. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Vertical Flows |  io.github.oktopeak/clio-mcp |
|---|---|---|
| Official MCP Registry | Listed Version: 2.0.0 No figure published Not marked · First seen |
Listed Version: 2.5.0 Downloads/month (npm): 606 Downloads/week (npm): 145 Forks (GitHub): 15 Stars (GitHub): 27 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 2.5.0 Downloads/month (npm): 606 Downloads/week (npm): 145 Forks (GitHub): 15 Stars (GitHub): 27 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | Vertical Flows | io.github.oktopeak/clio-mcp |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | No figure on GitHub | 27 |
| Forks (GitHub) (differs) | No figure on GitHub | 15 |
| Last release (differs) | Not published | 2026-11-03 |
| Where it runs (differs) | Remote server (verticalflows.com/api/mcp) | On your machine (@oktopeak/clio-mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 10, secrets among them: 2 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/vertical-flows/verticalflows | github.com/oktopeak/clio-mcp |
| Changes in the last 7 days (differs) | 0 | 4 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 12 h ago, requires authentication | no remote endpoint we check |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
Vertical Flows
View client requests, prepare actions and approve work within your firm's permissions.
io.github.oktopeak/clio-mcp
Connect Claude to Clio (37 tools), and export a whole Clio account, documents included.
How to run each
Vertical Flows As a remote MCP server
claude mcp add --transport http agent-gateway https://verticalflows.com/api/mcpio.github.oktopeak/clio-mcp As a local MCP server: npm package
claude mcp add --env "CLIO_CLIENT_ID=<YOUR_CLIO_CLIENT_ID>" --env "CLIO_CLIENT_SECRET=<YOUR_CLIO_CLIENT_SECRET>" --env "ENCRYPTION_KEY=<YOUR_ENCRYPTION_KEY>" --env "TOKEN_BROKER_URL=<YOUR_TOKEN_BROKER_URL>" --transport stdio clio-mcp -- npx -y @oktopeak/clio-mcpRequires: CLIO_CLIENT_ID, CLIO_CLIENT_SECRET (secret), ENCRYPTION_KEY (secret), TOKEN_BROKER_URL
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Vertical Flows has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of Vertical Flows publish no settings it asks for, so we do not compare settings.
What it can do: Vertical Flows · What it can do: io.github.oktopeak/clio-mcp · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.