Can I test money flows safely without losing real funds?

Absolutely. Increase has a top-tier sandbox environment. In your MCP settings, pass a Sandbox API Key (starting with `sk_test_`) and optionally set the environment to 'sandbox'. We even implemented literal tool overrides like `increase_simulate_inbound_ach` which are intentionally restricted exclusively to simulating inbound events on your test environment.

Does adding a new account via the Agent require paperwork?

No! Assuming your global LLC has already passed initial onboarding and your Entity object handles compliance, any subsequent programmatic calls to `increase_create_account` yield a fully compliant sub-ledger and associated numbers instantaneously contextually within the UI chat responses.

What is the difference between ACH and Wire transfer arrays here?

ACH acts through clearing houses taking normally 1-3 business days suited perfectly for non-urgent vendor mass payouts (`create_ach`). Wire transfers (`create_wire`) tie directly to Fedwire routing logic hitting banks internally within minutes - often bearing a slight static fee. Dictate which the bot should invoke based on liquidity needs.

How can I trace a specific payment?

We've added `increase_list_transactions` to handle historical booked transfers strictly by ID limits, exposing whether money cleared Fed limits safely.

Increase MCP Server for CrewAI 12 tools — connect in under 2 minutes

Name: Increase
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 12 Tools Framework

Connect your CrewAI agents to Increase through Vinkius, pass the Edge URL in the `mcps` parameter and every Increase tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="Increase Specialist",
    goal="Help users interact with Increase effectively",
    backstory=(
        "You are an expert at leveraging Increase tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in Increase "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 12 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* 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

About Increase MCP Server

The Increase MCP Server connects AI to a physical, fully compliant commercial US bank built explicitly top-down for programmatic transactions.

When paired with CrewAI, Increase becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Increase tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

What you can do

Endless Provisioning — Instantly generate new live bank accounts increase_create_account acting as sub-ledgers, enabling separate balances.
Open Payment Rails — Need to inject funds into a supplier directly using native American payment streams? Use increase_create_ach or sweep high-value overnight increase_create_wire securely.
Simulation Environment — Use Sandbox arrays to trigger simulated money hits increase_simulate_inbound_ach checking if an external agent script validates receiving deposits before going to production.

The Increase MCP Server exposes 12 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Increase to CrewAI via MCP

Follow these steps to integrate the Increase MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py. CrewAI auto-discovers 12 tools from Increase

Why Use CrewAI with the Increase MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Increase through the Model Context Protocol.

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 `mcps` parameter 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

Increase + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Increase MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries Increase for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries Increase, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Increase tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries Increase against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Increase MCP Tools for CrewAI (12)

These 12 tools become available when you connect Increase to CrewAI via MCP:

increase_create_account

Spin up a new Bank Account programmatically

increase_create_ach

Push an outbound ACH transfer to any US Bank

increase_create_card

Issue a physical/virtual debit card attached to an account

increase_create_routing_number

Generate new ABA routing & account number data

increase_create_wire

Send a same-day US Wire transfer

increase_get_balance

Fetch realtime ledger balance for a specific account

increase_list_accounts

List all sub-accounts under your charter

increase_list_cards

Sweep the active array of issued Cards

increase_list_transactions

Financial history extraction (Booked)

increase_list_transfers

Audit outbound transfers

increase_simulate_inbound_ach

Simulate receiving an ACH inbound (SANDBOX ONLY)

increase_simulate_inbound_wire

Simulate receiving a Wire inbound (SANDBOX ONLY)

Example Prompts for Increase in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with Increase immediately.

"Use our main test routing sandbox mechanism to simulate inbound an external payload of $1000 into Account ID 'acc_1234'."

"Audit our entire open accounts layout right now."

"Spin up a new fresh physical corporate banking account dedicated uniquely to 'Server Spends'. Send the Routing number to me."

Troubleshooting Increase MCP Server with CrewAI

Common issues when connecting Increase to CrewAI through the Vinkius, and how to resolve them.

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.

Increase + CrewAI FAQ

Common questions about integrating Increase MCP Server with CrewAI.

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.