Agendaforge vs Fillo
A side-by-side look at the Agendaforge and Fillo MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
A
AgendaforgeDeveloper ToolsEvent management for organizers: events, sessions, speakers, agendas, forms, approval-gated writes.38FairAuth: not declaredVerdict: choose Agendaforge for developer tools work; choose Fillo for developer tools as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
AChoose Agendaforge when
- You need dedicated capabilities in the Developer Tools domain.
Choose Fillo when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | A Agendaforge | |
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 38/100 · Fair | 44/100 · Fair |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Agendaforge | View Fillo |
Tools & capabilities
Agendaforge tools
No tool names declared yet. Check the project README from the listing page.
Fillo 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.
Agendaforge
No confirmed install command for Agendaforge yet — follow the setup steps linked from its listing page rather than a guessed package name.
Fillo
{
"mcpServers": {
"fillo": {
"command": "npx",
"args": [
"-y",
"@usefillo/cli@latest"
]
}
}
}
Frequently asked questions
Agendaforge is categorized under Developer Tools and uses an install path we have not confirmed yet. Fillo belongs to Developer Tools and uses a local stdio subprocess. Pick Agendaforge for developer tools work and Fillo 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. Agendaforge has no confirmed install command yet — follow its own setup instructions.
Agendaforge has no declared pricing — check the project's own site. Fillo 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 agendaforge and fillo as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Agendaforge has a quality signal of 38/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Fillo has 44/100 (Fair) with 2 views, 0 installs and 0 GitHub stars.