What is the difference between Authorize and Confirm in Zip?

Authorize initiates the transaction and checks for customer funds. Confirm (used in some regions) finalizes the checkout intent before capture.

Can I process partial captures via the agent?

Yes, the `capture_zip_payment` tool accepts an optional JSON body where you can specify a partial amount to capture if only part of the order is shipping.

How do I handle different regions like US and AU?

Specify your account region ('US' or 'AU') in the configuration settings. The MCP server automatically routes requests to the correct Zip gateway URL.

Zip MCP Server for CrewAI 8 tools — connect in under 2 minutes

Name: Zip
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 8 Tools Framework

Connect your CrewAI agents to Zip through Vinkius, pass the Edge URL in the `mcps` parameter and every Zip 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="Zip Specialist",
    goal="Help users interact with Zip effectively",
    backstory=(
        "You are an expert at leveraging Zip 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 Zip "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 8 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 Zip MCP Server

Connect your Zip (formerly Quadpay) merchant account to any AI agent to automate your Buy Now, Pay Later (BNPL) workflows. This MCP server enables your agent to initiate checkouts, manage order authorizations, and process captures or refunds directly from natural language interfaces.

When paired with CrewAI, Zip becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Zip 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

Checkout Initiation — Create new checkout sessions and retrieve redirect URLs for customers
Order Management — Authorize and confirm orders across US and Global gateway environments
Payment Ingestion — Capture authorized funds once goods are shipped to finalize transactions
Financial Resolution — Process full or partial refunds and void authorized but uncaptured payments
Status Monitoring — Retrieve real-time status and lifecycle updates for any Zip order
Account Insight — Access merchant configuration, currency limits, and account-level settings

The Zip MCP Server exposes 8 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 Zip to CrewAI via MCP

Follow these steps to integrate the Zip 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 8 tools from Zip

Why Use CrewAI with the Zip MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Zip 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

Zip + CrewAI Use Cases

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

Automated multi-step research: a reconnaissance agent queries Zip 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 Zip, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Zip 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 Zip against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Zip MCP Tools for CrewAI (8)

These 8 tools become available when you connect Zip to CrewAI via MCP:

authorize_zip_order

Typically used in US gateway integrations. Authorize a payment order

capture_zip_payment

Capture funds for an authorized order

confirm_zip_order

Finalize an authorized order

create_zip_checkout

Requires amount, currency, and redirect URLs. Initialize a new Zip checkout session

get_zip_merchant_config

Retrieve merchant account configuration

get_zip_order_status

g., Authorized, Captured, Cancelled) for a target order. Check the status of a Zip order

refund_zip_payment

Process a refund for an order

void_zip_payment

Void an authorized but uncaptured payment

Example Prompts for Zip in CrewAI

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

"Create a Zip checkout for $100.00 USD."

"Check the status of Zip order ID '98765'."

"Capture payment for authorized order '98765'."

Troubleshooting Zip MCP Server with CrewAI

Common issues when connecting Zip 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.

Zip + CrewAI FAQ

Common questions about integrating Zip 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.