How to Use the GameScorekeeper MCP in CrewAI

Deploy autonomous agent teams in CrewAI to analyze esports matches and team performance using GameScorekeeper.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect GameScorekeeper MCP to CrewAI

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

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Multi-Agent Analysis with CrewAI

One agent cannot research and analyze an entire tournament effectively. You assign a researcher agent to pull raw data using `list_competitions` and `list_competition_stages`. That agent builds a map of the event. A second analyst agent takes that map and digs deeper. It calls `get_team_form` and `get_player_stats` for the remaining contenders. The agents share this context through their shared memory, building a complete picture of the playoffs.

Autonomous Match Prediction Teams

You connect the MCP Server to a specialized crew to predict upcoming match outcomes. The scout agent uses `get_fixture_lineup` to verify who is actually playing. It passes the confirmed rosters to the historical analyst agent. The analyst pulls `get_player_details` for every starter to find historical mismatches. A moderator agent oversees the session, ensuring the crew bases its final prediction strictly on the returned stats rather than hallucinated metrics.

Filtered Tool Access for Security

You do not want your writer agent making unnecessary API calls. You restrict its access using the tool_filter parameter in the MCPServerHTTP configuration. The writer only gets access to `get_fixture_details` to check final scores. This compartmentalization saves API credits. The research agents handle the heavy lifting with the complex endpoints, while the writer agent focuses solely on formatting the final report for publication.

Setup guide

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

crew.py

from crewai import Agent, Task, Crew

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

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

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

Pass the Vinkius URL directly into the mcps array when defining your agent. The framework automatically discovers and mounts all ten available endpoints for that specific agent.

Yes. Use the MCPServerHTTP class from crewai.mcp and apply a tool_filter. This ensures your scout agent only accesses `get_player_details` while ignoring tournament-level tools.

The framework maintains shared memory across the crew. When the first agent fetches `list_fixtures`, the subsequent agents can reference those match IDs without making duplicate API requests.

You can configure a manager agent to delegate specific data retrieval tasks. The manager reviews the initial `get_team_details` response and decides which subordinate agent should investigate further.

The server only processes public esports rosters and historical performance metrics. Your proprietary prediction algorithms remain entirely local to your Python environment. Vinkius runs the external fetch logic in an ephemeral, stateless sandbox.

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