Fillo vs Formasty
A side-by-side look at the Fillo and Formasty MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Fillo for developer tools work as a local process; choose Formasty for developer tools over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Fillo when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
Choose Formasty when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a remote HTTP/SSE transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 40/100 · Fair | 37/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
Tools & capabilities
Fillo tools
No tool names declared yet. Check the project README from the listing page.
Formasty 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.
Fillo
{
"mcpServers": {
"fillo": {
"command": "npx",
"args": [
"-y",
"@usefillo/cli@latest"
]
}
}
}
Formasty
{
"mcpServers": {
"formasty-2": {
"url": "https://app.formasty.com/api/mcp"
}
}
}
Frequently asked questions
Fillo is categorized under Developer Tools and uses a local stdio subprocess. Formasty belongs to Developer Tools and uses a remote HTTP/SSE transport. Pick Fillo for developer tools work and Formasty for developer tools.
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.
Fillo has no declared pricing — check the project's own site. Formasty has no declared pricing — check the project's own site. 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 fillo and formasty-2 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Fillo has a quality signal of 40/100 (Fair) with 2 views, 0 installs and 0 GitHub stars. Formasty has 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.