Bring Micro Payments
to CrewAI
Learn how to connect FynCom to CrewAI and start using 6 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the FynCom MCP Server?
Connect your FynCom account to any AI agent and take full control of your user incentives and reward operations through natural conversation.
What you can do
- Reward Orchestration — Send instant cryptocurrency or fiat rewards to users or email addresses programmatically to incentivize engagement and feedback
- Campaign Management — Access and monitor your active reward campaigns and retrieve detailed performance and lead metadata in real-time
- Lead Engagement Tracking — Add leads to specific reward workflows programmatically from your AI agent to trigger automated incentives and follow-ups
- Wallet Intelligence — Check your real-time rewards wallet balance directly through your agent to ensure uninterrupted delivery of user incentives
- Transaction Oversight — Get a comprehensive overview of your reward history and campaign health using natural language commands
How it works
1. Subscribe to this server
2. Retrieve your API Key from your FynCom dashboard (Settings > API)
3. Start managing your user rewards from Claude, Cursor, or any MCP client
No more manual payment processing for small incentives. Your AI acts as your dedicated rewards and engagement coordinator.
Who is this for?
- Growth Marketers — automate the delivery of incentives for survey completions and product feedback using natural language queries
- Customer Success Managers — reward key customer actions and track engagement patterns more efficiently without leaving your workspace
- Product Developers — integrate real-time reward systems and incentive intelligence into custom applications through automated AI actions
Built-in capabilities (6)
Pass data in JSON. Add a lead to a reward campaign
Get specific campaign details
Check current rewards wallet balance
List active reward campaigns
List history of sent rewards
Pass data as a JSON string. Send a reward or incentive
Why CrewAI?
When paired with CrewAI, FynCom becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call FynCom tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.
- —
Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools
- —
CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the
mcpsparameter and agents auto-discover every available tool at runtime - —
Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls
- —
Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports
FynCom in CrewAI
FynCom and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect FynCom to CrewAI through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for FynCom in CrewAI
The FynCom MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 6 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in CrewAI only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
FynCom for CrewAI
Every tool call from CrewAI to the FynCom MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How do I find my FynCom API Key?
Log in to your FynCom dashboard and navigate to the Settings > API section to generate or copy your unique key.
Can I check my wallet balance via AI?
Yes! Use the get_wallet_balance tool to retrieve your current rewards budget and ensured you have sufficient funds for your campaigns.
How do I add a lead to a reward campaign?
Use the add_reward_lead tool by providing the campaign_id and a JSON string with the lead's email and other required details.
How does CrewAI discover and connect to MCP tools?
CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.
Can different agents in the same crew use different MCP servers?
Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.
What happens when an MCP tool call fails during a crew run?
CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.
Can CrewAI agents call multiple MCP tools in parallel?
CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.
Can I run CrewAI crews on a schedule (cron)?
Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.
MCP tools not discovered
Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.
Agent not using tools
Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".
Timeout errors
CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.
Rate limiting or 429 errors
Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.