Loonflow MCP
The MCP server of the Loonflow platform: an agent reads the ticket and approval queue and acts on tickets
- 2,094 ★ on the repository
- Last commit
Broad access
Why this level
- The agent can act on tickets: approve, reject and change process data
- A personal access token gives the agent the same ticket and user-list rights as your account
- The tenant's user list contains employee names, emails and departments
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/loonflowDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The agent can act on tickets: approve, reject and change process data
- A personal access token gives the agent the same ticket and user-list rights as your account
- The tenant's user list contains employee names, emails and departments
This is third-party code. Review the repository files before installing.
What it does
Loonflow is a platform for processes and tickets: a visual workflow designer, a form builder, routing by form data and an action log. The MCP server is built into the platform and is called loonflow-ticket. All its tools go through the same permission-checked services as the web interface. The agent gets ticket lists by category: my tasks, created by me, related to me, processed and others, and an administrator sees every ticket. Filters cover text search, period, process, node and status. For each ticket the agent sees the form, field permissions and the actions available at the current step. An action on a ticket runs after permission and required-field checks. The agent can also look up tenant users by name, alias or email. Authorization uses a personal access token or a Loonflow JWT.
Who it is for. For administrators and teams that run tickets and approvals in Loonflow and want to hand queue triage and action prep to an agent in Cursor or Claude Code.
Good fit when
- You want to ask an agent which tickets are waiting for your decision and get a list filtered by workflow or node
- Before approving you need to know which fields are required and which actions are available at the current step
- You need a list of tickets you have already processed over a chosen period
- You need to find an assignee or approver by name or email
- You deploy Loonflow yourself with docker-compose and want to connect an agent to it on your own server
Not a fit when
- You have no Loonflow install or cloud account: the server works only with that system
- You need to create or edit workflow schemas and forms: the tools cover ticket handling and user search only
- You use another tracker such as Jira, which has its own MCP servers
Example request
Show the Loonflow tickets waiting for my decision and tell me which fields are required in the first oneMCP
- Transport
- http
- Authentication
- key is optional
Environment variables
LOONFLOW_MCP_ACCESS_TOKENsecret- Server-side default access token for non-interactive setups such as stdio.
LOONFLOW_MCP_HOST- Address on which your own MCP server listens.
LOONFLOW_MCP_PORT- Port of your own MCP server.
Limitations
- A running Loonflow system is required: the cloud edition at https://www.loonflow.com/ with two free weeks or your own install.
- The server uses the Streamable HTTP transport on the /mcp path. For your own install the address is set by LOONFLOW_MCP_HOST and LOONFLOW_MCP_PORT.
- The AGPL-3.0 license sets conditions on modifying and network distribution of the code.
- Documentation and part of the interface target Chinese and English audiences, and the cloud service runs outside Russia.
How to disable. Remove the loonflow-ticket entry from mcpServers in the client settings and revoke the personal token in your Loonflow profile, after which the agent loses access to tickets. If you run the MCP server yourself, stop the process.
FAQ
How do I connect Loonflow to Cursor through MCP?
Create a personal token in your Loonflow profile and add an mcpServers entry loonflow-ticket with the cloud or your own server address and an Authorization: Bearer header with the token. Then enable the server in Cursor's MCP list.
Which tools does the Loonflow MCP server provide?
Five: ticket_list for ticket lists, ticket_detail for the form and available actions, ticket_prepare_handle to prepare handling, ticket_handle to run an action and user_list to search users in the tenant.
Can the agent change a Loonflow ticket by accident?
Only ticket_handle can change tickets. It has a dry_run mode: the server checks the request and returns a summary while the ticket stays as it was.
How do I run Loonflow myself?
Download docker-compose.yml and .env from the repository's docker_compose_deploy folder, change at least the passwords in .env and run docker-compose up -d. You sign in with the email and password set in .env.
Where do I get a token for the Loonflow MCP server?
In the Loonflow interface open Personal Information, then Personal Access Token, and create a new token. Values start with lfpat.; save the token right away, because the Authorization header needs it. An alternative is the X-Loonflow-Access-Token header with the raw value.
Discussion
No questions or reviews yet.
Related
MCP serversAwesome Claude Skills by Composio
Awesome Claude Skills
A curated list of Claude skills and plugins, plus Composio's own automation skills for 78 SaaS apps
n8n Workflows: the Zie619 collection
n8n-workflows
An open collection of 4,343 n8n workflows: 365 integrations, 15 categories, search and a web interface, JSON download
A plugin and CLI catalog for agents: generates command-line interfaces for GUI apps like GIMP and Blender and installs ready ones via CLI-Hub
SDKs, a CLI and MCP access to over a thousand prebuilt SaaS integrations for agents, with auth and per-user sessions
Awesome n8n Templates
awesome-n8n-templates
More than 280 free n8n templates by topic: Gmail, Telegram, Slack, WhatsApp, Google Drive, Notion, OpenAI, AI agents and RAG bots
An MCP server with n8n node and template knowledge: the agent picks nodes, validates configs and, with API access, creates workflows in your n8n
Comparison with similar tools
Entries that share the main search query, and how they differ.
| Entry | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| Loonflow (this entry) | yes | key is optional | 2,094 | |
| Jira MCP | no | key is optional | 97 | MCP for Jira: JQL issues, sprints and time logging |
| Dagu | yes | API key | 4,428 | a local workflow orchestrator in one binary with no tickets or approvals |
| MCP Atlassian | no | key is optional | 6,035 | an MCP for Jira and Confluence working with Atlassian tasks and pages |
README in short
Loonflow 3.0 is an open process platform on Django and React with rebuilt workflow and form designers. Next to the code are demo videos, a roadmap and links to the API reference.