How do I find my Metrc API Keys?

Your Integrator Key is provided by your software vendor. Your User Key is found in your Metrc User Profile under the 'API Keys' section.

Which Base URL should I use?

You must use the API URL corresponding to your state (e.g., https://api-ca.metrc.com for California).

Is my regulatory data secure?

Absolutely. Your token is encrypted at rest and injected securely at runtime.

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

Name: Metrc
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 10 Tools Framework

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

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="Metrc Specialist",
    goal="Help users interact with Metrc effectively",
    backstory=(
        "You are an expert at leveraging Metrc 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 Metrc "
        "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)

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 Metrc MCP Server

Connect your Metrc account to any AI agent and take full control of your cannabis track-and-trace compliance through natural conversation.

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

Facility Oversight — List all licensed facilities and fetch detailed metadata for your operations
Inventory Tracking — Retrieve active items, strains, and inventory packages with real-time status visibility
Supply Chain Management — Monitor plant life cycles, harvest batches, and incoming inventory transfers securely
Compliance Auditing — List active sales receipts and verify unit of measure configurations
Detailed Inspection — Fetch comprehensive metadata for individual packages and state-specific license configurations

The Metrc 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 Metrc to CrewAI via MCP

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

Install CrewAI

Run pip install crewai

Replace the token

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

Customize the agent

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

Run the crew

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

Why Use CrewAI with the Metrc MCP Server

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

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

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

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

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

Metrc + CrewAI Use Cases

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

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

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

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

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

Metrc MCP Tools for CrewAI (10)

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

get_package_details

Get details for a specific package

get_unit_of_measures

g. Grams, Ounces). List all units of measure

list_active_harvests

List active harvests for a facility

list_active_items

List active items for a facility

list_active_packages

List active packages for a facility

list_active_sales

List active sales receipts

list_active_strains

List active strains for a facility

list_facilities

List all licensed facilities

list_incoming_transfers

List incoming inventory transfers

list_tracked_plants

List tracked plants for a facility

Example Prompts for Metrc in CrewAI

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

"List all active facilities associated with my Metrc account."

"Show active inventory packages for license 'LIC-12345'."

"Get details for package label 'ABCDEFG1234567'."

Troubleshooting Metrc MCP Server with CrewAI

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

MCP tools not discovered

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

Agent not using tools

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

Timeout errors

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

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.

Metrc + CrewAI FAQ

Common questions about integrating Metrc MCP Server with CrewAI.

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.

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.

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.

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.

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.