How to Use the CloudCard ID Photos MCP in CrewAI

Q: Can a CrewAI agent autonomously reject photos using CloudCard ID Photos?

Yes, you can delegate the denyidphoto tool to a specialized moderator agent in your crew. The agent will evaluate photo status and submit the rejection code autonomously.

Run autonomous multi-agent CrewAI teams to manage CloudCard ID Photos approvals and cardholder data.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect CloudCard ID Photos MCP to CrewAI

Create your Vinkius account to connect CloudCard ID Photos to CrewAI and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup CloudCard ID Photos with CrewAI

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Multi-Agent CrewAI Photo Moderation

Set up a dual-agent crew to handle your queue. The first CrewAI agent uses `list_submitted_photos` to gather pending submissions and checks them against rules retrieved by `list_photo_requirements`. The second CrewAI agent receives the analysis and either triggers `approve_id_photo` or executes `deny_id_photo` with a highly specific rejection reason.

Automated Cardholder Auditing

Keep your directory clean without lifting a finger. A CrewAI audit agent can query `list_cardholders` and use `get_cardholder_details` to flag incomplete profiles or missing photos. It then hands those flags to a CrewAI outreach agent that registers missing info or pings the user to upload a compliant photo.

Distributed Office Coordination

This MCP Server allows your crew to coordinate across physical locations. One CrewAI agent monitors active webhooks via `list_configured_webhooks` to catch new uploads. Another CrewAI agent calls `list_card_offices` to map where the physical cards need to go, ensuring logistics run completely autonomously.

Setup guide

Set up CloudCard ID Photos MCP in CrewAI

Prerequisites

Python 3.10+ installed
crewai package (pip install crewai)
Active Vinkius subscription with a valid endpoint token

1

Install CrewAI
Run pip install crewai to install the framework. MCP support is built-in via the mcps parameter.
2

Add the MCP URL to your agent
Pass your Vinkius endpoint directly to the mcps list. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. CrewAI handles tool discovery and caching automatically.
3

Kick off your crew
Create a Crew with your agent and tasks. Call crew.kickoff() — the agent will automatically invoke CloudCard ID Photos tools as needed.

crew.py

from crewai import Agent, Task, Crew

agent = Agent(
    role="CloudCard ID Photos Analyst",
    goal="Access and analyze CloudCard ID Photos data via MCP.",
    backstory="Expert analyst with direct CloudCard ID Photos access.",
    mcps=[
        "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    ],
)

task = Task(
    description="List recent CloudCard ID Photos transactions",
    agent=agent,
    expected_output="A summary of recent activity",
)

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

Get your connection token →

Prerequisites

Python 3.10+ installed
crewai + crewai-tools packages
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install crewai crewai-tools. The MCPServerAdapter handles lifecycle management and tool conversion.
2

Connect with MCPServerAdapter
Use MCPServerAdapter as a context manager with SseServerParameters pointing to your Vinkius endpoint. The adapter automatically manages connection lifecycle.
3

Assign tools and run
Pass the returned mcp_tools to your agent's tools parameter. The adapter converts MCP tools to native BaseTool objects compatible with all CrewAI agents.

crew.py

from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
from mcp import SseServerParameters

server_params = SseServerParameters(
    url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)

with MCPServerAdapter(server_params) as mcp_tools:
    agent = Agent(
        role="CloudCard ID Photos Analyst",
        goal="Access and analyze CloudCard ID Photos data via MCP.",
        backstory="Expert analyst with direct CloudCard ID Photos access.",
        tools=mcp_tools,
    )

    task = Task(
        description="List recent CloudCard ID Photos transactions",
        agent=agent,
        expected_output="A summary of recent activity",
    )

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

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by CloudCard. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect CloudCard ID Photos now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about CloudCard ID Photos MCP in CrewAI

You pass the Vinkius server URL directly into the mcps parameter of your CrewAI Agent. The framework automatically discovers tools like `list_submitted_photos` and makes them available to the agent.

Yes, you can delegate the `deny_id_photo` tool to a specialized moderator agent in your crew. The agent will evaluate photo status and submit the rejection code autonomously.

CrewAI agents pass context sequentially. For example, your research agent gets cardholder details via `get_cardholder_details` and passes that structured data to your logistics agent to verify card offices.

Yes, you can use CrewAI's advanced setup with MCPServerHTTP to filter tools. This prevents a research agent from accessing writing tools like `register_new_cardholder`.

Your cardholder records, including first/last names, emails, and ID photos, are processed entirely in memory inside Vinkius's secure sandboxed environment. No data is stored or logged on the Vinkius platform, keeping your institutional records strictly private.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript