Overview
FlowiseAI is a visual workflow builder for AI agents with native MCP support.Prerequisites
- Flowise installed (installation guide)
- StackOne API key (get one here)
- StackOne account ID (find it here)
Setup Steps
Step 1: Prepare StackOne Configuration
First, prepare your StackOne connection details:- Get your API key from the StackOne Dashboard
- Get your account ID from the Accounts section
- Encode your API key for Basic auth:
Step 2: Add MCP Server to Flowise
1
Open Flowise
Navigate to your Flowise instance (typically
http://localhost:3000)2
Create or Open a Chatflow
Create a new chatflow or open an existing one where you want to add StackOne tools
3
Add MCP Tool
- In the left sidebar, find “MCP Tools” or “Tools” section
- Drag the MCP Tool component onto your canvas
- Connect it to your agent or chat model
4
Configure MCP Server
In the MCP Tool configuration panel:Server Type: Select “HTTP” (StackOne uses HTTP transport)Server URL:Headers: Click “Add Header” and configure:Protocol Version:
2025-06-18 (optional)5
Test Connection
Click “Connect” or “Test” to verify the MCP server connectionYou should see available tools populate from your StackOne account
Step 3: Configure Available Tools
Once connected, Flowise will discover all available StackOne tools for your account: Tool Filtering:- You can filter which tools to expose to your agent
- Search for specific operations by provider or action type
- Enable/disable tools as needed for your workflow
gong_crm_search_calls- Search CRM calls in Gongsalesforce_list_accounts- List accounts from Salesforceslack_send_message- Send messages via Slack- Plus hundreds more based on your connected integrations
To see all available integrations and operations:
- Browse Integrations: stackone.com/integrations
- Explore Operations: app.stackone.com/actions
Step 4: Build Your Workflow
Now you can use StackOne tools in your Flowise chatflow:- Connect to Agent: Link the MCP Tool to your AI agent node
- Configure Agent Prompt: Tell your agent when to use StackOne tools
- Add Logic: Combine with other Flowise components (conditional logic, data transformation, etc.)
- Test: Try asking questions that require StackOne data
Example Workflows
Workflow 1: Cross-Platform Search Assistant
Components:- Chat Input
- MCP Tool (StackOne - multiple providers)
- Chat Model (GPT-4, Claude, etc.)
- Chat Output
Workflow 2: Automated Activity Dashboard
Components:- Schedule Trigger (daily)
- MCP Tool (StackOne - multiple providers)
- Data Aggregation
- Notification (Slack, Email)
Workflow 3: Multi-System Data Agent
Components:- Chat Input
- MCP Tool (StackOne with multiple accounts/providers)
- MCP Tool (Other services)
- Chat Model with function calling
- Chat Output
Troubleshooting
Connection Issues
MCP server connection fails
MCP server connection fails
Check:
- URL is exactly
https://api.stackone.com/mcp - Base64 token includes the colon:
api_key: - Account ID is correct
- Headers are properly formatted JSON
No tools appearing
No tools appearing
Possible causes:
- No active integrations in your StackOne account
- Incorrect account ID
- API key doesn’t have proper permissions
- Accounts section shows linked integrations
- API key is valid and not expired
Tools fail when executed
Tools fail when executed
Common issues:
- Missing required parameters
- Provider connection issue
- Rate limiting
- Flowise logs for error messages
- StackOne Request Logs for API errors
- Tool schema matches expected parameters
HTTP vs SSE transport confusion
HTTP vs SSE transport confusion
StackOne uses HTTP transport only, not SSE (Server-Sent Events).Configuration:
- Select “HTTP” as transport type
- Do NOT use SSE endpoints
- URL should be
https://api.stackone.com/mcpwithout/ssesuffix
Best Practices
Performance
- Tool Selection: Only enable tools you need in your workflow
- Parallel Execution: Flowise can execute multiple tools in parallel
Security
- Environment Variables: Store credentials in environment variables, not hardcoded
- Access Control: Use Flowise’s access control features
- API Key Rotation: Rotate StackOne API keys periodically
Limitations
- Transport: StackOne only supports HTTP transport (no STDIO or SSE)
- Session Management: StackOne MCP is stateless (no session persistence)
- Tool Discovery: Tools are determined by the enabled actions for the integration configuration associated with the linked account
- Rate Limits: Subject to StackOne API rate limits (60 requests/min by default)
Next Steps
Explore All Tools
See all available operations in the StackOne Playground
API Documentation
Learn about StackOne’s Platform API
FlowiseAI Docs
Official Flowise MCP documentation
Get Support
Contact StackOne support for assistance