2,500+ MCP servers ready to use
Vinkius

OpenTHC MCP Server for Claude Desktop 12 tools β€” connect in under 2 minutes

Built by Vinkius GDPR 12 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.

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": {
      // Your Vinkius token. get it at cloud.vinkius.com
      "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.

Claude Desktop is the definitive way to connect OpenTHC to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 12 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

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

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

01

Open Claude Desktop Settings

Go to Settings β†’ Developer β†’ Edit Config to open claude_desktop_config.json

02

Add the MCP Server

Paste the configuration above into the mcpServers section

03

Restart Claude Desktop

Close and reopen Claude Desktop to load the new server

04

Start using OpenTHC

Look for the πŸ”Œ icon in the chat. your 12 tools are now available

Why Use Claude Desktop with the OpenTHC MCP Server

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

01

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

02

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

03

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

04

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

OpenTHC + Claude Desktop Use Cases

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

01

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

02

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

03

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

04

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

OpenTHC MCP Tools for Claude Desktop (12)

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

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

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

01

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).
02

Authentication error

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

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.

OpenTHC + Claude Desktop FAQ

Common questions about integrating OpenTHC MCP Server with Claude Desktop.

01

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.
02

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.
03

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.
04

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.
05

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.

Connect OpenTHC to Claude Desktop

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