mcp-server-flyder
About
A Model Context Protocol server for integrating with Flyder workflows. It allows users to list and run workflows via MCP tools, currently in early development.
Details
- Author
- Streamline-TS
- Downloads
- 135
- Categories
- Other
Jump to
- Lists workflows belonging to the user
- Runs a specific workflow by its ID
- Supports optional input text for workflows
- Early development, features subject to change
Setting up with Highlight
This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:
- Download and install Highlight from highlightai.com/download
- Navigate to the plugins tab and select "Add Custom Plugin"
-
Configure the plugin with the settings below
Plugin Name
mcp-server-flyderCommand (node, npx, python, etc.)Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
- Enable "Start Automatically" if you want the plugin to start when Highlight launches
From the repository
Install via uvx and configure in Claude Desktop's claude_desktop_config.json. Set two environment variables: FLYDER_EMAIL and FLYDER_API_KEY. Use the provided tools list_workflows and run_workflow_by_id.
Claude Desktop / Cursor
Paste into your MCP client config file to install this server.
{
"mcpServers": {
"mcp-server-flyder": {
"flyder": {
"command": "uvx",
"args": [
"mcp-server-flyder"
],
"env": {
"FLYDER_EMAIL": "<email used to sign up on Flyder>",
"FLYDER_API_KEY": "<your Flyder API key>"
}
}
}
}
}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>"
}
}
}mcp-server-flyder
MCP Server for FlyderOverview
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:
{
"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 for run instructions.
2. 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.
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
