LAX MCP Flow Generation Cursor Client Server
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"lax-mcp-flow-generation-cursor-client","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# LambdaX MCP Flow Generation Cursor Client This is a client-side MCP server that acts as a proxy to the backend LAX MCP Flow Generation server. It solves the performance issue of sending large JSON files through the MCP protocol by handling file reading locally and forwarding requests to the backend server. ## Architecture ``` Cursor → Cursor Client MCP Server → Backend MCP Server ``` - **Cursor**: The IDE client that connects to our local MCP server - **Cursor Client MCP Server**: This server (stdio transport) that handles file I/O and forwards requests - **Backend MCP Server**: The original LAX MCP Flow Generation server (HTTP transport) ## Features - **File Path Support**: Tools can accept file paths instead of requiring full JSON objects - **Automatic File Reading**: Reads JSON files locally to avoid large data transfers - **Transparent Forwarding**: All requests are forwarded to the backend server - **Same Interface**: Exposes identical tools as the original server - **Error Handling**: Proper error handling for file operations and network requests ## Available Tools - `validate_flow`: Validates flow JSON (supports file paths) - `search_flows`: Search for similar flows - `search_flows_by_node`: Search flows by specific node - `search_nodes`: Search for available nodes - `check_flow_exists_lax`: Check if flow exists in LAX - `search_advanced_features`: Search for advanced features - `search_functions`: Search for transform functions - `fetch_execution_of_node`: Get node execution examples - `get_node_by_name`: Get node details by name - `think`: Log reasoning and analysis - `get_flow_by_name`: Retrieve flow by name - `save_flow_to_lax`: Save flow to LambdaX (supports file paths) ## Usage Add this to your Cursor MCP configuration: ```json { "mcpServers": { "lax-mcp-flow-generation": { "command": "lax-mcp-flow-gen", "args": [], "env": { "BACKEND_SERVER_URL": "http://localhost:8000/mcp?username=YOUR_USERNAME…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.