How to Use the Metrc MCP in Cursor

Q: How do I configure the Metrc MCP Server for a single Cursor project?

Create a .cursor/mcp.json file in your project root directory. Add the server command and environment variables under the mcpServers key, and your agent will pick up the tools instantly.

Q: Can Cursor write code to sync my database using live Metrc data?

Yes, your agent can call listactivepackages to see the actual payload shape and then write the exact SQL or Prisma schema to store it. This cuts out manual data mapping entirely.

Generate code that pulls live Metrc track-and-trace data directly into your Cursor editor using real-time compliance payloads.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Metrc MCP to Cursor

Create your Vinkius account to connect Metrc to Cursor 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 Metrc with Cursor

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Build inventory features with live Metrc payloads in Cursor

`list_facilities` lets you pull your active state licenses directly into your editor context. Your agent uses the actual JSON payloads to write TypeScript interfaces, meaning you never have to guess whether a facility ID is a string or a number. When writing custom sync scripts, your agent runs `get_unit_of_measures` to write precise validation logic. This ensures your local database schema matches the state's official units without having to look up documentation.

Test package queries inside your editor

`list_active_packages` fetches real inventory records while you write your backend logic. The MCP Server lets your agent run live queries so you can see exactly how the state structures package categories, items, and quantities. You can also use `get_package_details` to verify that your error-handling code actually catches missing tags. It beats writing mock tests because you are using real-world API responses directly inside your active workspace.

Auto-complete strain and transfer schemas

`list_active_strains` pulls your facility's registered strains directly into Cursor. This lets your agent generate autocomplete menus or lookup tables with your exact, real-world strain names instead of placeholder text. If you are building intake dashboards, `list_incoming_transfers` provides the exact payload structure of pending shipments. You can write your intake parsing logic against real manifest data in one shot.

Setup guide

Set up Metrc MCP in Cursor

Prerequisites

Cursor installed (macOS, Windows, or Linux)
Active Vinkius subscription with a valid endpoint token

1

Open MCP Settings

Go to Cursor Settings → MCP or open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and search for "MCP: Add Server".
2

Add the Metrc MCP

Cursor will create or open .cursor/mcp.json in your project root. Paste the JSON snippet on the right. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Enable Agent mode

Open Composer (Cmd+I / Ctrl+I) and switch to Agent mode using the dropdown at the top. MCP tools are only available in Agent mode.
4

Verify the connection

Ask Cursor something like "List my recent Metrc transactions." If the MCP tools are loaded correctly, Cursor will call the Metrc tools automatically. You can also check Settings → MCP for a green status indicator.

.cursor/mcp.json

{
  "mcpServers": {
    "metrc-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

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 Metrc. 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 Metrc 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 Metrc MCP in Cursor

Create a `.cursor/mcp.json` file in your project root directory. Add the server command and environment variables under the mcpServers key, and your agent will pick up the tools instantly.

Yes, your agent can call `list_active_packages` to see the actual payload shape and then write the exact SQL or Prisma schema to store it. This cuts out manual data mapping entirely.

No, you can point this MCP integration to either the Metrc sandbox or your live production API. Just make sure you supply the correct vendor and user keys in your local configuration.

If a tool call fails, the error message from the state API prints directly in the Cursor chat window. You can tell your agent to read the error and rewrite your code to handle it.

Your API keys, facility licenses, and package details are stored locally on your machine. This server uses a secure sandbox that prevents your sensitive compliance keys from leaking to external logging servers.

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