fieldflow vs everything
Side-by-side comparison to help you pick between these two MCP servers.
fieldflow by guillaumegay13 | everything by modelcontextprotocol | |
|---|---|---|
| Stars | ★ 111 | ★ 85,748 |
| 30d uses | — | — |
| Score | 47 | 77 |
| Official | — | ✓ |
| Categories | Developer ToolsAI / LLM ToolsProductivity | Developer ToolsAI / LLM ToolsOther |
| Language | Python | TypeScript |
| Last commit | this month | this month |
fieldflow · Summary
FieldFlow converts OpenAPI endpoints into selectively filtered tools with MCP support for AI clients like Claude Desktop.
everything · Summary
Official MCP test server exercising all protocol features for client builders.
fieldflow · Use cases
- Reducing API response payload size for AI models to minimize context window usage
- Creating filtered API access for AI applications through MCP protocol
- Simplifying complex API responses by selecting only relevant fields
everything · Use cases
- Testing MCP client implementations against all protocol features
- Learning MCP protocol capabilities through a reference server
- Validating client compatibility with different transport methods
fieldflow · Install
# Install with MCP support
pip install -e '.[mcp]'
# Run HTTP server
fieldflow serve-http
# Run MCP server (for Claude Desktop)
fieldflow-mcpFor Claude Desktop integration, add to config:
{
"mcpServers": {
"fieldflow": {
"command": "python",
"args": ["-m", "fieldflow_mcp.cli"]
}
}
}everything · Install
NPX (recommended)
{
"mcpServers": {
"everything": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-everything"]
}
}
}On Windows, use cmd /c:
{
"mcpServers": {
"everything": {
"command": "cmd",
"args": ["/c", "npx", "-y", "@modelcontextprotocol/server-everything"]
}
}
}Docker
{
"mcpServers": {
"everything": {
"command": "docker",
"args": ["run", "-i", "--rm", "mcp/everything"]
}
}
}Global install
npm install -g @modelcontextprotocol/server-everything@latest
npx @modelcontextprotocol/server-everything