A: Hey Jhnony!

Let's get those MCP questions answered for you:

1. Can Tier 1 Users Use the MCP Function?

Yes, absolutely! All AppSumo tiers, including Tier 1, have full access to connect to and use actions from MCP (Model Context Protocol) servers. This allows you to equip your agents and workflows with a vast array of tools.

The main distinction with higher tiers (like T3/4) is access to our premium, managed MCP connections for certain high-demand services (e.g., WhatsApp, LinkedIn), which offer enhanced reliability and direct support from us. But the core ability to connect to any MCP server is available to everyone.

2. How MCP Function Works & Credit Consumption:

How it Works: You find an MCP server for an app (e.g., Google Sheets MCP from a provider like Composio, or one you self-host). You authenticate that app with the MCP provider. They give you an "MCP Server URL." You add this URL to your AgenticFlow workspace (MCP Servers). Now, your AgenticFlow agents can be given the "tools" (actions) from that Google Sheets MCP. When your agent needs to, say, "add a new row to my 'Sales Leads' sheet," it uses the connected Google Sheets MCP to perform that action.

3. Credit Consumption:

Each time your agent or workflow uses an MCP action, it costs the fixed AgenticFlow credit cost for that step execution (4 credits for Tier 1/2). This is for our platform's orchestration.

If the MCP action itself internally uses one of AgenticFlow's built-in economical LLMs for processing (this is less common for simple data actions but possible for more complex MCP tools), there would be an additional variable credit cost based on token usage.

Any costs associated with the MCP server provider itself or the end application's API usage (e.g., if the Google Sheets API had its own usage limits you hit through the MCP) are separate and managed by you with those providers.

4. Connecting to an API if No MCP Exists:

If an application has a standard REST API but no available MCP server for it:

You cannot directly connect that API to become an "AgenticFlow MCP server" (AgenticFlow acts as an MCP client, using tools from MCP servers).

Solution: You use AgenticFlow's API Call node (available in the Workflow builder). You directly configure this node with the application's API endpoint, authentication details, and the request data. This is how you integrate any API that doesn't have an MCP.

Alternatively, for deeper integration, a developer could build a new MCP server for that application (using open-source tools or platforms like Vercel/Cloudflare that support MCP), and then you could connect that new MCP server to AgenticFlow.

5. AgenticFlow API for MCP (for Mobile Devices, etc.):

AgenticFlow provides its own robust REST API (get your API key in Settings). Through this API, you can:
- Trigger your AgenticFlow workflows.
- Send messages to your AgenticFlow Agents and get their responses.
- Manage your datasets, etc.

So, yes, your mobile application would interact with your AgenticFlow Agents via our API. The AgenticFlow Agent, in turn, would use its equipped MCP tools to perform tasks. The mobile app talks to AgenticFlow; AgenticFlow talks to the MCPs.

In Summary:
- All tiers can use MCPs.
- MCP actions cost fixed AgenticFlow credits per step (plus variable if it uses our internal AI).
- For tools with APIs but no MCP, use our API Call node.

Yes, your mobile app interacts with AgenticFlow agents (which then use MCPs) via our main platform API.

Hope this helps clarify how MCPs and APIs work with AgenticFlow!
— Sean