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
-
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.
-
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:
{
"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:
-
Run the MCP inspector to test your changes. See Debugging for run instructions.
-
Test using the Claude desktop app. Add the following to your
claude_desktop_config.json:
{
"mcpServers": {
"flyder": {
"command": "uv",
"args": [
"--directory",
"/<path to repo>",
"run",
"mcp-server-flyder"
],
"env": {
"FLYDER_EMAIL": "<email used to sign up on Flyder>",
"FLYDER_API_KEY": "<your Flyder API key>"
}
}
}
}
License
This MCP server is licensed under the GNU General Public License. This means you are free to use, modify, and distribute the software, subject to the terms and conditions of the GNU License. For more details, please see the LICENSE file in the project repository.
Metadata
Release files for mcp-server-flyder 0.4.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| mcp_server_flyder-0.4.5.tar.gz | 31.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mcp_server_flyder-0.4.5-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 48.4 kB
Release files / mcp_server_flyder-0.4.5.tar.gz
| Download URL | mcp_server_flyder-0.4.5.tar.gz |
|---|---|
| Size | 31.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7ace30b0cca20bd01e4e1d2f4c3423878315942db43541c19754894f1317b3ac
|
|
BLAKE2b-256 checksum How to use checksums |
7745ce8fc0c443fc708f3fb0bb334308f29d623f3ece97f5109e2b314c7ac858
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.6.11
|
Release files / mcp_server_flyder-0.4.5-py3-none-any.whl
| Download URL | mcp_server_flyder-0.4.5-py3-none-any.whl |
|---|---|
| Size | 16.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4134b74a9b888a4c1723353cd7340dc539fbd4e6bd18823e1bcd63e0c06fa846
|
|
BLAKE2b-256 checksum How to use checksums |
e399593e72933c673d418175d7cca75db44b7c688b19e8afd3166bbf635eea41
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.6.11
|
Security for mcp-server-flyder 0.4.5
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.