AgenticFlow

Product details

Q: Availability of Actions for MCPs like Blue, AITable, and Bika.ai

Hi,

I’ve noticed that many MCPs, such as Blue, AITable, VBOUT, NEURONWriter, and Bika.ai, currently do not include any available actions or some few actions within the platform.

Could you please let me know when the complete set of actions for these tools is expected to be released?
This functionality is important for many sumo-lings as we depend on these tools, and I’d appreciate any updates you can share.

Thanks in advance for your time and support!

Best regards,

Yusri_PLUSMay 2, 2025
Founder Team
SeanP_AgenticFlowAI

SeanP_AgenticFlowAI

May 2, 2025

A: Hey Yusri,

Thanks for reaching out and highlighting this – you are correct that while we have connection placeholders listed for many tools in our MCP catalog (like Blue, AITable, Bika.ai, VBOUT, NEURONWriter), the specific, easy-to-use Actions within AgenticFlow for many of them are indeed limited or not yet built out.

Building deep, reliable actions for each of the thousands of potential integrations is a significant ongoing effort. We prioritize which MCPs get actions developed based on several factors, including the vendor's API stability, technical complexity, and most importantly, direct community demand expressed on our public roadmap.

What You Can Do Now:

1. Vote/Request on Roadmap: The best way to get actions for specific tools like AITable, Bika.ai, etc., prioritized is to add or vote for feature requests for them on our public roadmap: https://agenticflow.featurebase.app/. Clearly state which tool and which specific actions (e.g., "AITable - Create Record," "NEURONWriter - Analyze Content") you need. The more votes a request gets, the higher it moves on our development list.

2. Use the API Call Node: In the meantime, if these tools (Blue, AITable, etc.) have a public API, you can often interact with them today using our generic API Call node within a workflow. This requires looking up their API documentation and manually configuring the request (URL, method, headers, body) in the node. It's more technical but provides immediate connectivity.

3. (Advanced) Build a Custom MCP: If you (or someone on your team) have technical skills, you can follow the official Model Context Protocol guidelines (https://modelcontextprotocol.io/quickstart/server) to build your own custom MCP server for the specific tool and actions you need. You can then host this server and connect its endpoint URL to AgenticFlow. This gives you full control and allows you to contribute back if you wish.

We are committed to expanding our library of built-in MCP actions based on what the community needs most. Please use the roadmap to voice your priorities, and explore the API Call node for immediate needs if the tool has an accessible API.

Thanks for your understanding and support!

Share
Helpful?
Log in to join the conversation