2,500+ MCP servers ready to use
Vinkius

Polar MCP Server for CrewAI 10 tools — connect in under 2 minutes

Built by Vinkius GDPR 10 Tools Framework

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

Vinkius supports streamable HTTP and SSE.

python
from crewai import Agent, Task, Crew

agent = Agent(
    role="Polar Specialist",
    goal="Help users interact with Polar effectively",
    backstory=(
        "You are an expert at leveraging Polar 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 Polar "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 10 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)
Polar
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 Polar MCP Server

Connect your Polar account to any AI agent and take full control of your digital commerce operations through natural conversation.

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

  • Product Management — List, retrieve and audit all products (one-time, subscription, free) with pricing and metadata
  • Subscription Tracking — Monitor active, canceled and past_due subscriptions with billing periods and customer info
  • Order & Revenue — List completed orders with amounts, currency, payment status and customer details
  • Customer Discovery — Browse customers by email, name and purchase history
  • Discount Management — List, create and audit discount codes with percentage or fixed-amount types
  • Checkout Operations — Create checkout sessions for products and track open, expired and confirmed checkouts
  • Webhook Audit — Review configured webhook endpoints and their subscribed events

The Polar MCP Server exposes 10 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 Polar to CrewAI via MCP

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

01

Install CrewAI

Run pip install crewai

02

Replace the token

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

03

Customize the agent

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

04

Run the crew

Run python crew.py. CrewAI auto-discovers 10 tools from Polar

Why Use CrewAI with the Polar MCP Server

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

01

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

02

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

03

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

04

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

Polar + CrewAI Use Cases

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

01

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

02

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

03

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

04

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

Polar MCP Tools for CrewAI (10)

These 10 tools become available when you connect Polar to CrewAI via MCP:

01

create_checkout

Requires the product ID. Optionally associate with an existing customer and apply a discount. Returns the checkout session with its URL that you can redirect customers to for payment. Create a new checkout session in Polar

02

create_discount

Requires the name, code, type (percentage or fixed_amount), and amount. Optionally set the duration (once, forever, repeating). The discount can be applied during checkout. Create a new discount code in Polar

03

get_product

Provide the product ID (UUID format). Get details for a specific Polar product

04

list_checkouts

Each checkout shows its status (open, expired, confirmed), associated product, customer, and creation date. Useful for tracking abandoned and completed checkouts. List checkout sessions in your Polar store

05

list_customers

Each customer shows their email, name, billing address, and metadata. Optionally filter by email to find a specific customer. List customers in your Polar store

06

list_discounts

Each discount shows its code, type (percentage, fixed_amount), amount, duration (once, forever, repeating), and active status. Use this to audit your promotional offers. List discount codes in your Polar store

07

list_orders

Each order shows the customer, product, amount, currency, payment status, and creation date. Useful for tracking revenue and verifying successful transactions. List orders in your Polar store

08

list_products

Each product includes its name, description, price, type (one-time, subscription, free), and metadata. Use this to audit your product catalog and see what you are selling. List products in your Polar store

09

list_subscriptions

Each subscription shows the customer, product, status (active, past_due, canceled, expired, incomplete, trialing), current period start/end dates, and amount. Optionally filter by status and set a limit. List subscriptions in your Polar store

10

list_webhooks

Each webhook shows its URL, subscribed events (order.created, subscription.active, etc.), and status. Use this to audit your event integrations. List webhook endpoints in your Polar store

Example Prompts for Polar in CrewAI

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

01

"Show me all active subscriptions and their total monthly revenue."

02

"Create a 20% discount code called 'LAUNCH20' for the summer sale."

03

"Show me all orders from the last 30 days."

Troubleshooting Polar MCP Server with CrewAI

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

01

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.
02

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".
03

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.
04

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.

Polar + CrewAI FAQ

Common questions about integrating Polar MCP Server with CrewAI.

01

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.
02

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.
03

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.
04

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.
05

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.

Connect Polar to CrewAI

Get your token, paste the configuration, and start using 10 tools in under 2 minutes. No API key management needed.