How to Use the Gingr MCP in CrewAI

Q: How do I add the Gingr server to a CrewAI agent?

Pass the server URL directly into the mcps parameter of your CrewAI Agent definition. It automatically discovers the tools and makes them available to the crew.

Q: Does CrewAI support selective tool exposure for Gingr?

You can use the toolfilter option in the MCP client configuration. This limits which specific tools, like getdigitalwhiteboard, each agent can access.

Deploy a specialized agent crew for Gingr operations with this MCP server.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Gingr MCP to CrewAI

Create your Vinkius account to connect Gingr 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 Gingr with CrewAI

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Automated kennel monitoring with CrewAI

Assign a monitor agent to watch the facility status using `list_active_checkins`. It keeps a constant eye on occupancy levels and alerts the team to any anomalies. It runs in the background of your operation. You get a steady stream of updates without having to manually check the dashboard yourself.

Role-based pet management in CrewAI

Create a team where one agent handles owner inquiries via `find_owner_by_email` and another manages reservations via `list_owner_reservations`. They share memory to ensure the owner gets the right info. It mirrors how a professional kennel works. You have one agent for logistics and another for client relations, working in tandem.

Escalate issues through your CrewAI agents

Use `list_business_locations` to help agents understand which branch they are querying. If a tool fails, the agent reports it to the moderator for human review. It creates a clear path for error handling. Your agents don't get stuck in loops; they flag the problem and wait for instructions.

Setup guide

Set up Gingr 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 Gingr tools as needed.

crew.py

from crewai import Agent, Task, Crew

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

task = Task(
    description="List recent Gingr 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="Gingr Analyst",
        goal="Access and analyze Gingr data via MCP.",
        backstory="Expert analyst with direct Gingr access.",
        tools=mcp_tools,
    )

    task = Task(
        description="List recent Gingr 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 Gingr. 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 Gingr 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 Gingr MCP in CrewAI

Pass the server URL directly into the `mcps` parameter of your CrewAI Agent definition. It automatically discovers the tools and makes them available to the crew.

Yes. By using shared memory, your agents pass the findings from `get_pet_owner_details` between themselves, keeping the context consistent throughout the task.

You can use the tool_filter option in the MCP client configuration. This limits which specific tools, like `get_digital_whiteboard`, each agent can access.

Use environment variables. The server handles the authentication handshake, so your agent code never sees the raw keys.

The server enforces strict boundaries. It only retrieves specific pet medical and owner contact records required by the current agent task and discards them once the crew finishes.

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