How to Use the 7shifts MCP in CrewAI

Q: Can I restrict which 7shifts tools a CrewAI agent can use?

Yes. Import MCPServerHTTP from crewai.mcp and apply a toolfilter. This keeps your analysis agents from accidentally firing off write commands like shift creation.

Deploy a team of autonomous AI managers to handle your restaurant scheduling with the 7shifts CrewAI integration.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect 7shifts MCP to CrewAI

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

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Multi-Agent Restaurant Management

Stop trying to make one agent do everything. CrewAI lets you build a specialized team. You assign a Researcher agent to pull the roster using `list_employees` and a Coordinator agent to actually build the schedule. They share memory. The Researcher figures out who is available and passes that context to the Coordinator. The Coordinator then executes `create_shift` repeatedly until the floor is fully staffed. Nobody has to babysit them.

Autonomous 7shifts MCP Server Audits

Labor costs bleed out when nobody watches the clock. You can spin up a Monitor agent that constantly checks `list_time_punches` against the planned hours from `list_schedules`. It runs in the background, looking for discrepancies. If someone forgets to clock out, the Monitor spots the anomaly. It flags a Moderator agent, which pulls the specific staff details via `get_employee` and drafts an alert to the general manager.

Cross-Department Coordination

Kitchen staff and front-of-house operate in different worlds. You can restrict your agents so they only see what they need. Use a tool filter in your setup to give the Kitchen Agent access to `list_departments` and `list_shifts` for back-of-house only. A separate FOH Agent manages the servers and hosts. They collaborate hierarchically. A Manager agent sits on top, reviewing the combined schedule before allowing any write operations to hit the API.

Setup guide

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

crew.py

from crewai import Agent, Task, Crew

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

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

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

Pass your Vinkius endpoint directly into the mcps array when defining your agent. Just add the URL and the agent automatically inherits the tools.

Yes. Import MCPServerHTTP from crewai.mcp and apply a tool_filter. This keeps your analysis agents from accidentally firing off write commands like shift creation.

They use shared memory. One agent can pull the business venues via the locations tool, and the next agent in the sequence can use those IDs to pull specific schedules without asking for the data twice.

You can use stdio, SSE, or Streamable HTTP. The framework handles the underlying connection so you can focus on agent prompts.

We run the connection through a stateless V8 Isolate. Your agents pull sensitive wage and timecard data, but the sandbox drops it all the moment the execution step completes. No persistence, no leaks.

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