2,500+ MCP servers ready to use
Vinkius

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

Built by Vinkius GDPR 12 Tools Framework

LangChain is the leading Python framework for composable LLM applications. Connect OpenTHC through Vinkius and LangChain agents can call every tool natively. combine them with retrievers, memory, and output parsers for sophisticated AI pipelines.

Vinkius supports streamable HTTP and SSE.

python
import asyncio
from langchain_mcp_adapters.client import MultiServerMCPClient
from langchain_openai import ChatOpenAI
from langgraph.prebuilt import create_react_agent

async def main():
    # Your Vinkius token. get it at cloud.vinkius.com
    async with MultiServerMCPClient({
        "openthc": {
            "transport": "streamable_http",
            "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp",
        }
    }) as client:
        tools = client.get_tools()
        agent = create_react_agent(
            ChatOpenAI(model="gpt-4o"),
            tools,
        )
        response = await agent.ainvoke({
            "messages": [{
                "role": "user",
                "content": "Using OpenTHC, show me what tools are available.",
            }]
        })
        print(response["messages"][-1].content)

asyncio.run(main())
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.

LangChain's ecosystem of 500+ components combines seamlessly with OpenTHC through native MCP adapters. Connect 12 tools via Vinkius and use ReAct agents, Plan-and-Execute strategies, or custom agent architectures. with LangSmith tracing giving full visibility into every tool call, latency, and token cost.

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 LangChain 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 LangChain via MCP

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

01

Install dependencies

Run pip install langchain langchain-mcp-adapters langgraph langchain-openai

02

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token

03

Run the agent

Save the code and run python agent.py

04

Explore tools

The agent discovers 12 tools from OpenTHC via MCP

Why Use LangChain with the OpenTHC MCP Server

LangChain provides unique advantages when paired with OpenTHC through the Model Context Protocol.

01

The largest ecosystem of integrations, chains, and agents. combine OpenTHC MCP tools with 500+ LangChain components

02

Agent architecture supports ReAct, Plan-and-Execute, and custom strategies with full MCP tool access at every step

03

LangSmith tracing gives you complete visibility into tool calls, latencies, and token usage for production debugging

04

Memory and conversation persistence let agents maintain context across OpenTHC queries for multi-turn workflows

OpenTHC + LangChain Use Cases

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

01

RAG with live data: combine OpenTHC tool results with vector store retrievals for answers grounded in both real-time and historical data

02

Autonomous research agents: LangChain agents query OpenTHC, synthesize findings, and generate comprehensive research reports

03

Multi-tool orchestration: chain OpenTHC tools with web scrapers, databases, and calculators in a single agent run

04

Production monitoring: use LangSmith to trace every OpenTHC tool call, measure latency, and optimize your agent's performance

OpenTHC MCP Tools for LangChain (12)

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

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

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

01

MultiServerMCPClient not found

Install: pip install langchain-mcp-adapters

OpenTHC + LangChain FAQ

Common questions about integrating OpenTHC MCP Server with LangChain.

01

How does LangChain connect to MCP servers?

Use langchain-mcp-adapters to create an MCP client. LangChain discovers all tools and wraps them as native LangChain tools compatible with any agent type.
02

Which LangChain agent types work with MCP?

All agent types including ReAct, OpenAI Functions, and custom agents work with MCP tools. The tools appear as standard LangChain tools after the adapter wraps them.
03

Can I trace MCP tool calls in LangSmith?

Yes. All MCP tool invocations appear as traced steps in LangSmith, showing input parameters, response payloads, latency, and token usage.

Connect OpenTHC to LangChain

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