2,500+ MCP servers ready to use
Vinkius

OpenTHC MCP Server for Cursor 12 tools — connect in under 2 minutes

Built by Vinkius GDPR 12 Tools IDE

Cursor is an AI-first code editor built on VS Code that integrates LLM-powered coding assistance directly into the development workflow. Its Agent mode enables autonomous multi-step coding tasks, and MCP support lets agents access external data sources and APIs during code generation.

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 OpenTHC and 2,500+ MCP Servers from a single visual interface.

Vinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop Interface
Download Free Open SourceNo signup required
Classic Setup·json
{
  "mcpServers": {
    "openthc": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}
OpenTHC
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 OpenTHC MCP Server

Connect your OpenTHC Cannabis Regulatory Compliance Engine to any AI agent and take full control of your seed-to-sale workflows through natural conversation.

Cursor's Agent mode turns OpenTHC into an in-editor superpower. Ask Cursor to generate code using live data from OpenTHC and it fetches, processes, and writes. all in a single agentic loop. 12 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.

What you can do

  • Company & License Management — List all registered companies and verify active cannabis licenses for compliance assurance
  • Cultivation Tracking — Query all active plants in cultivation with growth stages, strain varieties, and facility room locations
  • Inventory Control — Fetch complete inventory ledger including harvested material, work-in-progress, finished goods, and destruction candidates
  • Laboratory Testing — Access lab samples and Certificates of Analysis (CoA) with full potency, terpene, and contaminant test results
  • B2B Transfers — Monitor incoming and outgoing wholesale transfer orders with manifests, bills of lading, and fulfillment status
  • Retail Sales — Retrieve point-of-sale B2C transaction history for daily reporting, tax verification, and purchase limit enforcement
  • Product Catalog — Browse your complete cannabis product catalog with THC/CBD percentages, SKU data, and regulatory classifications
  • Facility Organization — List cultivation rooms, processing areas, and operational zones for spatial inventory and workflow planning

The OpenTHC MCP Server exposes 12 tools through the Vinkius. Connect it to Cursor 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 OpenTHC to Cursor via MCP

Follow these steps to integrate the OpenTHC MCP Server with Cursor.

01

Open MCP Settings

Press Cmd+Shift+P (macOS) or Ctrl+Shift+P (Windows/Linux) → search "MCP Settings"

02

Add the server config

Paste the JSON configuration above into the mcp.json file that opens

03

Save the file

Cursor will automatically detect the new MCP server

04

Start using OpenTHC

Open Agent mode in chat and ask: "Using OpenTHC, help me...". 12 tools available

Why Use Cursor with the OpenTHC MCP Server

Cursor AI Code Editor provides unique advantages when paired with OpenTHC through the Model Context Protocol.

01

Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context

02

Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards

03

MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment

04

VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools

OpenTHC + Cursor Use Cases

Practical scenarios where Cursor combined with the OpenTHC MCP Server delivers measurable value.

01

Code generation with live data: ask Cursor to generate a security report module using live DNS and subdomain data fetched through MCP

02

Automated documentation: have Cursor query your API's tool schemas and generate TypeScript interfaces or OpenAPI specs automatically

03

Infrastructure-as-code: Cursor can fetch domain configurations and generate corresponding Terraform or CloudFormation templates

04

Test scaffolding: ask Cursor to pull real API responses via MCP and generate unit test fixtures from actual data

OpenTHC MCP Tools for Cursor (12)

These 12 tools become available when you connect OpenTHC to Cursor via MCP:

01

list_b2b_transactions

Each B2B transaction record contains the transfer ID, direction (incoming/outgoing), counterparty company, transfer status (draft, committed, received, rejected), creation date, expected fulfillment date, line items with quantities, and attached manifests or bills of lading. Essential for supply chain orchestration, logistics planning, and regulatory transfer documentation. AI agents use this to track shipment status, verify received quantities, and prepare compliance reports. List all B2B transfer transactions (incoming and outgoing)

02

list_b2c_transactions

Each transaction includes the sale ID, customer information (if recorded), sale date, line items with products and quantities, total amount, tax breakdown, dispensary location, and inventory deduction confirmations. Critical for daily sales reporting, tax calculation verification, inventory reconciliation, and regulatory sales limit enforcement. AI agents should query this to analyze sales patterns, verify compliance with purchase limits, and prepare end-of-day reports. List all retail B2C sales transactions

03

list_companies

Use this to understand which organizations are part of your regulatory network, including license holders, cultivators, processors, distributors, and retailers. Each company record contains legal identification data, registration status, and associated license information. Essential for multi-company operations and B2B transaction verification. List all companies registered in the OpenTHC compliance engine

04

list_contacts

Each contact includes company affiliation, contact type (B2B partner, regulatory agency, logistics provider), communication details, and relationship status. Use this to identify verified trading partners before creating B2B transfer orders or compliance documentation. List all business contacts in the OpenTHC network

05

list_inventory

Each inventory item displays the lot number, item type, quantity with unit of measurement, storage location, creation date, chain of custody history, and compliance status. Fundamental for stock reconciliation, audit preparation, transfer order creation, and regulatory reporting. AI agents should query this before fulfilling orders or conducting inventory audits. List all inventory items with quantities and locations

06

list_lab_results

Each result includes the lab result ID, linked sample, testing laboratory accreditation, full analytical results (THC/CBD potency, terpene profile, contaminant levels), pass/fail determination, and the official CoA document reference. Critical for regulatory compliance, product labeling accuracy, retail menu display, and consumer transparency. AI agents should reference this to verify product safety before sale or transfer. List all laboratory test results and certificates of analysis

07

list_lab_samples

Each sample contains the sample ID, linked inventory lot, sample type (flower, edible, concentrate), test panel requested (potency, pesticides, heavy metals, mycotoxins, microbials, residual solvents), submission date, testing laboratory, and current analysis status. Essential for quality assurance workflows, batch release decisions, and compliance with mandatory testing regulations. AI agents should check this to determine if a batch has pending or cleared lab results. List all laboratory samples submitted for testing

08

list_licenses

Each license contains the license type, expiration dates, regulatory conditions, and approval status. Critical for compliance verification — AI agents should check this before initiating any regulated activity to ensure the proper license is active and valid for the intended operation. List all cannabis licenses associated with your account

09

list_plants

Each plant record contains the unique plant ID (POP/PIP tags), growth stage (vegetative, flowering, harvesting), strain/variety, location within the facility (room, rack, shelf), planting date, and estimated harvest window. Critical for cultivation management, compliance reporting, and seed-to-sale traceability. AI agents use this to monitor crop health, predict harvest timelines, and ensure regulatory plant count limits are respected. List all cannabis plants in active cultivation

10

list_products

Each product entry contains the product name, type classification, SKU, potency information (THC/CBD percentages), package sizes, and regulatory tags. Essential for retail operations, menu generation, and B2B sales order creation. AI agents should reference this when checking product availability or creating sales transactions. List all cannabis products in your inventory catalog

11

list_sections

Each section entry includes the section ID, name, purpose classification (vegetation room, flowering room, drying room, processing area, retail floor, warehouse), environmental parameters, and capacity limits. Essential for spatial inventory tracking, cultivation workflow organization, facility compliance inspections, and operational planning. AI agents use this to assign plants to specific rooms during cultivation activities, locate inventory within the facility, and generate room-level production reports. List all facility sections and cultivation areas

12

list_varieties

Each variety record contains the variety ID, strain name (e.g., Blue Dream, OG Kush, Sour Diesel), genetics type (Type I - THC dominant, Type II - Mixed THC/CBD, Type III - CBD dominant), breeder information, and associated cultivation characteristics. Fundamental for cultivation planning, product labeling, genetic tracking, and regulatory strain registration. AI agents reference this when creating new plant records, generating product labels, or analyzing strain performance metrics. List all cannabis varieties (strains) in the system

Example Prompts for OpenTHC in Cursor

Ready-to-use prompts you can give your Cursor agent to start working with OpenTHC immediately.

01

"List all our active cannabis licenses and verify which ones are expiring soon."

02

"Show me all plants currently in flowering stage in Room 3 and estimate harvest readiness."

03

"Check inventory levels for all THC-dominant flower products and show me pending lab results."

Troubleshooting OpenTHC MCP Server with Cursor

Common issues when connecting OpenTHC to Cursor through the Vinkius, and how to resolve them.

01

Tools not appearing in Cursor

Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
02

Server shows as disconnected

Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.

OpenTHC + Cursor FAQ

Common questions about integrating OpenTHC MCP Server with Cursor.

01

What is Agent mode and why does it matter for MCP?

Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
02

Where does Cursor store MCP configuration?

Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
03

Can Cursor use MCP tools in inline edits?

No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
04

How do I verify MCP tools are loaded?

Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.

Connect OpenTHC to Cursor

Get your token, paste the configuration, and start using 12 tools in under 2 minutes. No API key management needed.