How do I get a Client ID and Secret for Getpaid?

Log in to your Getpaid dashboard, navigate to Settings > Integrations, and you can create a new API integration to retrieve your Client ID and Client Secret.

In what units should I provide the payment amount?

The API uses minor units for currency. For example, to charge $1.00 USD, you must provide the value 100 (cents).

Can I process refunds through the agent?

Yes! Use the 'refund_billing_payment' tool and provide the specific Payment ID. You can also specify a custom amount for a partial refund.

How do I check if a checkout session was completed?

Use the 'get_checkout_status' tool with the Checkout ID. The agent will return the current state, such as 'completed', 'pending', or 'expired'.

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

Name: Getpaid
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 12 Tools Framework

Connect your CrewAI agents to Getpaid through Vinkius, pass the Edge URL in the `mcps` parameter and every Getpaid 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="Getpaid Specialist",
    goal="Help users interact with Getpaid effectively",
    backstory=(
        "You are an expert at leveraging Getpaid 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 Getpaid "
        "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 Getpaid MCP Server

Connect your Getpaid account to any AI agent to automate your billing, payment processing, and checkout workflows through the Model Context Protocol (MCP). Getpaid is a modern payment platform designed for SaaS, marketplaces, and service businesses to handle global transactions with ease. This MCP server enables you to track payments, manage customer records, and initiate new checkout sessions directly through natural conversation.

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

Key Features

Payment Oversight — List all processed payments, fetch detailed metadata including status and timestamps, and monitor revenue flow instantly.
Checkout Automation — Create new checkout sessions for products or services and retrieve secure payment links programmatically.
Refund Management — Process full or partial refunds for captured payments directly from your chat interface.
Customer & Invoice Tracking — Access your billing database, retrieve detailed customer profiles, and monitor generated invoices.
Subscription Insights — List active and inactive recurring billing plans to understand your long-term revenue health.
Webhook Visibility — Monitor configured webhooks to ensure your internal systems are receiving real-time payment notifications.
Real-time Synchronization — Keep your financial operations accessible to your AI assistant without leaving your primary workspace.

The Getpaid 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 Getpaid to CrewAI via MCP

Follow these steps to integrate the Getpaid 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 Getpaid

Why Use CrewAI with the Getpaid MCP Server

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

Getpaid + CrewAI Use Cases

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

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

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

Getpaid MCP Tools for CrewAI (12)

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

create_checkout_session

Initiate checkout

get_account_details

Get account identity

get_checkout_status

Check checkout status

get_customer_details

Get customer metadata

get_payment_details

Get payment metadata

list_billing_customers

List customers

list_billing_invoices

List invoices

list_billing_payments

List all payments

list_billing_subscriptions

List recurring plans

list_payment_webhooks

List webhook configs

refund_billing_payment

Process a refund

verify_api_connection

Check connection

Example Prompts for Getpaid in CrewAI

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

"List all payments processed today."

"Create a checkout session for $25.00 USD."

"Refund payment 'pay_98765' for the full amount."

Troubleshooting Getpaid MCP Server with CrewAI

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

Getpaid + CrewAI FAQ

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