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 Claude Desktop 10 tools — connect in under 2 minutes

Name: Metrc
Availability: InStock
Author: Vinkius

modelcontextprotocol.io/quickstart/user

Built by Vinkius GDPR 10 Tools IDE

Claude Desktop is Anthropic's native application for interacting with Claude AI models on macOS and Windows. It was the first consumer application to ship with built-in MCP support, making it the reference implementation for the Model Context Protocol standard.

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.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Metrc and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "metrc": {
      // Your Vinkius token. get it at cloud.vinkius.com
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

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.

Claude Desktop is the definitive way to connect Metrc to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 10 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.

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 Claude Desktop 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 Claude Desktop via MCP

Follow these steps to integrate the Metrc MCP Server with Claude Desktop.

Open Claude Desktop Settings

Go to Settings → Developer → Edit Config to open claude_desktop_config.json

Add the MCP Server

Paste the configuration above into the mcpServers section

Restart Claude Desktop

Close and reopen Claude Desktop to load the new server

Start using Metrc

Look for the 🔌 icon in the chat. your 10 tools are now available

Why Use Claude Desktop with the Metrc MCP Server

Claude Desktop by Anthropic provides unique advantages when paired with Metrc through the Model Context Protocol.

Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available

Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface

Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions

Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network

Metrc + Claude Desktop Use Cases

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

Interactive data exploration: ask Claude to query DNS records, look up WHOIS data, and cross-reference results in a single conversation

Ad-hoc security audits: type a domain name and let Claude enumerate subdomains, check DNS history, and flag configuration anomalies. all through natural language

Executive briefings: generate comprehensive domain intelligence reports by asking Claude to compile findings into a formatted summary

Learning and training: new team members can explore API capabilities conversationally without needing to read documentation

Metrc MCP Tools for Claude Desktop (10)

These 10 tools become available when you connect Metrc to Claude Desktop 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 Claude Desktop

Ready-to-use prompts you can give your Claude Desktop 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 Claude Desktop

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

Server not appearing after restart

Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).

Authentication error

Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.

Tools not showing in chat

Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.

Metrc + Claude Desktop FAQ

Common questions about integrating Metrc MCP Server with Claude Desktop.

How does Claude Desktop discover MCP tools?

When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.

What happens if the MCP server is temporarily unavailable?

Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.

Can I connect multiple MCP servers simultaneously?

Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.

Is there a limit on the number of tools per server?

Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.

Does Claude Desktop support Streamable HTTP transport?

Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.