MCP Server for Flyder
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":"mcp-server-flyder","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.
# mcp-server-flyder MCP Server for Flyder ## Overview A Model Context Protocol server for Flyder workflow integration. Please note that mcp-server-flyder is currently in early development. The functionality and available tools are subject to change as we continue to develop and improve the server. ### Tools 1. `list_workflows` - Get a list of workflows that belong to the user. This returns a dictionary that has workflow names and their IDs. - Input: - none - Returns: A list containing workflow names and their IDs. The IDs can later be used to run a specific workflow. 2. `run_workflow_by_id` - Run a specific workflow using its ID. - Input: - `workflow_id` (int): The ID of the workflow to run. - `input` (str, optional): The input text to be passed to the workflow. If not provided, the default input from the workflow will be used. - Returns: An object containing the result of the workflow run. ## Configuration ### Usage with Claude Desktop Add this to your `claude_desktop_config.json`: ```json { "mcpServers": { "flyder": { "command": "uvx", "args": [ "mcp-server-flyder" ], "env": { "FLYDER_EMAIL": "<email used to sign up on Flyder>", "FLYDER_API_KEY": "<your Flyder API key>" } } } } ``` ## Debugging You can use the MCP inspector to debug the server. ``` cd path/to/repo npx @modelcontextprotocol/inspector uv run mcp-server-flyder ``` ## Development If you are doing local development, there are two ways to test your changes: 1. Run the MCP inspector to test your changes. See [Debugging](#debugging) for run instructions. 2. Test using the Claude desktop app. Add the following to your `claude_desktop_config.json`: ```json { "mcpServers": { "flyder": { "command": "uv", "args": [ "--directory", "/<path to repo>", "run", "mcp-server-flyder" ], "env": { "FLYDER_EMAIL": "<email used to sign…
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.