2,500+ MCP servers ready to use
Vinkius

PharmWare MCP Server for Mastra AI 12 tools — connect in under 2 minutes

Built by Vinkius GDPR 12 Tools SDK

Mastra AI is a TypeScript-native agent framework built for modern web stacks. Connect PharmWare through Vinkius and Mastra agents discover all tools automatically. type-safe, streaming-ready, and deployable anywhere Node.js runs.

Vinkius supports streamable HTTP and SSE.

typescript
import { Agent } from "@mastra/core/agent";
import { createMCPClient } from "@mastra/mcp";
import { openai } from "@ai-sdk/openai";

async function main() {
  // Your Vinkius token. get it at cloud.vinkius.com
  const mcpClient = await createMCPClient({
    servers: {
      "pharmware": {
        url: "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp",
      },
    },
  });

  const tools = await mcpClient.getTools();
  const agent = new Agent({
    name: "PharmWare Agent",
    instructions:
      "You help users interact with PharmWare " +
      "using 12 tools.",
    model: openai("gpt-4o"),
    tools,
  });

  const result = await agent.generate(
    "What can I do with PharmWare?"
  );
  console.log(result.text);
}

main();
PharmWare
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 PharmWare MCP Server

Connect your PharmWare Cannabis Testing Laboratory Platform to any AI agent and take full control of your laboratory operations, quality assurance, and compliance workflows through natural conversation.

Mastra's agent abstraction provides a clean separation between LLM logic and PharmWare tool infrastructure. Connect 12 tools through Vinkius and use Mastra's built-in workflow engine to chain tool calls with conditional logic, retries, and parallel execution. deployable to any Node.js host in one command.

What you can do

  • Client Management — List all cultivators, processors, and retailers who submit samples to your laboratory for testing
  • Sample Tracking — Monitor all cannabis samples received with chain of custody, testing status, and priority levels
  • Test Panels — Browse available analytical methods (potency, terpenes, pesticides, heavy metals, microbials, mycotoxins)
  • Test Results — Access complete analytical findings with pass/fail determinations against regulatory limits
  • Certificates of Analysis — Retrieve all issued CoAs with QR codes for consumer verification and regulatory compliance
  • Batch Traceability — Track production batches through laboratory testing with seed-to-sale linkage
  • Laboratory Workflows — Monitor active processes from sample intake through CoA issuance with QC checkpoints
  • Instrument Management — Verify calibration status and maintenance schedules for HPLC, GC-MS, ICP-MS systems
  • Compliance Reports — Generate regulatory submissions, monthly summaries, and trend analyses
  • Platform Integrations — Check health of connections to WeedMaps, Metrc, BioTrack, and state regulatory APIs
  • User Administration — Review laboratory staff roles, permissions, and training certifications
  • Audit Trails — Access complete operation logs for FDA 21 CFR Part 11 compliance and inspection readiness

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

Follow these steps to integrate the PharmWare MCP Server with Mastra AI.

01

Install dependencies

Run npm install @mastra/core @mastra/mcp @ai-sdk/openai

02

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token

03

Run the agent

Save to agent.ts and run with npx tsx agent.ts

04

Explore tools

Mastra discovers 12 tools from PharmWare via MCP

Why Use Mastra AI with the PharmWare MCP Server

Mastra AI provides unique advantages when paired with PharmWare through the Model Context Protocol.

01

Mastra's agent abstraction provides a clean separation between LLM logic and tool infrastructure. add PharmWare without touching business code

02

Built-in workflow engine chains MCP tool calls with conditional logic, retries, and parallel execution for complex automation

03

TypeScript-native: full type inference for every PharmWare tool response with IDE autocomplete and compile-time checks

04

One-command deployment to any Node.js host. Vercel, Railway, Fly.io, or your own infrastructure

PharmWare + Mastra AI Use Cases

Practical scenarios where Mastra AI combined with the PharmWare MCP Server delivers measurable value.

01

Automated workflows: build multi-step agents that query PharmWare, process results, and trigger downstream actions in a typed pipeline

02

SaaS integrations: embed PharmWare as a first-class tool in your product's AI features with Mastra's clean agent API

03

Background jobs: schedule Mastra agents to query PharmWare on a cron and store results in your database automatically

04

Multi-agent systems: create specialist agents that collaborate using PharmWare tools alongside other MCP servers

PharmWare MCP Tools for Mastra AI (12)

These 12 tools become available when you connect PharmWare to Mastra AI via MCP:

01

list_audit_logs

Each audit log entry contains the timestamp, performing user, action type (sample created, result modified, CoA issued, workflow completed, user permission changed), affected record ID, previous and new values (for modifications), IP address, and justification comment (if required). Fundamental for regulatory inspections, data integrity investigations, deviation root cause analysis, and FDA 21 CFR Part 11 compliance. AI agents use this to reconstruct event sequences during quality investigations, identify unauthorized changes, and generate audit-ready documentation packages. List all audit trail entries for laboratory operations and data changes

02

list_batches

Each batch entry contains the batch ID, producing facility license number, batch size, cannabis product type, harvest or manufacture date, linked samples submitted for testing, batch testing status (pending, partial, complete), disposition (released, quarantined, rejected, destroyed), and seed-to-sale tracking identifiers. Essential for batch-level compliance monitoring, recall management, and regulatory reporting. AI agents reference this when tracing contamination issues, verifying batch clearance for distribution, or generating lot-based compliance reports. List all cannabis batches tracked through laboratory testing

03

list_certificates

Each CoA record includes the certificate number, linked sample and batch, issuing laboratory accreditation details, comprehensive analytical results (potency profile, terpene fingerprint, contaminant screening), regulatory compliance statement, authorized signatory, issuance date, and QR code for consumer verification. Critical for product release decisions, regulatory audits, and consumer transparency programs. AI agents use this to verify CoA authenticity, batch compliance status, and generate client-facing documentation packages. List all Certificates of Analysis (CoA) issued by the laboratory

04

list_clients

Each client record contains company name, license number, contact information, client type (cultivation facility, processing plant, dispensary, or third-party tester), account status, and billing information. Essential for laboratory client management, sample intake workflows, and regulatory compliance reporting. AI agents should reference this when identifying sample ownership, generating client-specific reports, or verifying active testing contracts. List all clients (cultivators, processors, retailers) registered in PharmWare

05

list_instruments

Each instrument record contains the instrument name (HPLC system, GC-MS, ICP-MS, spectrophotometer), manufacturer, model, serial number, installation location, calibration status, last calibration date, next scheduled maintenance, qualification status (IQ/OQ/PQ), and associated test methods. Critical for instrument qualification, preventive maintenance scheduling, and analytical data integrity. AI agents should reference this to verify instrument readiness before assigning tests, schedule calibration activities, or troubleshoot analytical failures. List all laboratory instruments and equipment with calibration status

06

list_integrations

Each integration record contains the platform name (WeedMaps, Metrc, BioTrack, Leaf Data Systems, state regulatory API), integration type (bidirectional data sync, CoA publishing, sample status updates, regulatory reporting), connection status, last synchronization timestamp, data mapping configuration, and error logs. Critical for multi-platform compliance, automated CoA distribution, and real-time regulatory reporting. AI agents reference this to verify integration health, troubleshoot sync failures, and ensure seamless data flow between laboratory systems and external platforms. List all external system integrations (WeedMaps, state APIs, seed-to-sale platforms)

07

list_reports

Each report entry includes the report type (monthly summary, regulatory submission, client statement, trend analysis, deviation investigation, corrective action report), generation date, reporting period, associated clients or samples, regulatory agency destination (if applicable), and distribution status. Essential for regulatory compliance documentation, client billing reconciliation, and laboratory performance analytics. AI agents use this to prepare state-mandated reports, analyze testing trends, and identify quality improvement opportunities. List all laboratory reports and compliance documents generated

08

list_results

Each result contains the result ID, linked sample, test panel performed, analytical findings (THC/CBD potency percentages, terpene concentrations, pesticide residue levels, heavy metal concentrations, mycotoxin detection), pass/fail determination against regulatory limits, analyst who performed the test, review status, and date of completion. Fundamental for quality assurance, client notification workflows, and regulatory data submissions. AI agents should query this to verify sample compliance before releasing Certificates of Analysis or advising clients on product disposition. List all laboratory test results with analytical data

09

list_samples

Each sample contains the unique sample ID, submitting client, sample type (flower, edible, concentrate, topical, cartridge), received date, testing priority (standard, rush, priority), sample condition upon receipt, chain of custody documentation, and current testing status (received, in-progress, completed, failed). Critical for laboratory workflow management, turnaround time tracking, and seed-to-sale traceability compliance. AI agents use this to monitor sample queues, predict completion dates, and alert clients about status changes. List all cannabis samples submitted for laboratory testing

10

list_tests

Each test entry includes the test name (potency, terpenes, pesticides, heavy metals, mycotoxins, microbials, residual solvents, water activity, moisture content), test method (HPLC, GC-MS, ICP-MS, ELISA, qPCR), accreditation status, turnaround time, pricing, and regulatory limits per jurisdiction. Essential for test panel configuration, method validation, and compliance with state-specific cannabis testing requirements. AI agents reference this when configuring sample test orders, explaining testing scopes to clients, or verifying analytical method accreditation. List all test panels and analytical methods available in the laboratory

11

list_users

Each user record contains the username, full name, assigned role (laboratory director, quality manager, analytical chemist, sample technician, administrative staff), department, permission level (read-only, data entry, review/approval, system administrator), account status (active, inactive, locked), last login date, and training certification expiry. Essential for access control management, audit trail integrity, and ISO/IEC 17025 personnel competency requirements. AI agents should query this to verify user authorization before approving test results, assigning quality-critical tasks, or conducting access reviews. List all laboratory users with roles and permissions

12

list_workflows

Each workflow entry includes the workflow name (sample intake, potency testing, contaminant screening, CoA review, sample disposal), step definitions, assigned roles and responsibilities, quality control checkpoints, average completion time, and current instances in progress. Essential for laboratory operations management, staff task assignment, and process optimization. AI agents use this to guide technicians through testing procedures, identify workflow bottlenecks, and ensure ISO/IEC 17025 quality management system compliance. List all laboratory workflow templates and active processes

Example Prompts for PharmWare in Mastra AI

Ready-to-use prompts you can give your Mastra AI agent to start working with PharmWare immediately.

01

"Show me all cannabis samples currently in testing and their expected completion dates."

02

"List all pending Certificates of Analysis awaiting review and signature."

03

"Check the integration status with state regulatory APIs and WeedMaps CoA publishing."

Troubleshooting PharmWare MCP Server with Mastra AI

Common issues when connecting PharmWare to Mastra AI through the Vinkius, and how to resolve them.

01

createMCPClient not exported

Install: npm install @mastra/mcp

PharmWare + Mastra AI FAQ

Common questions about integrating PharmWare MCP Server with Mastra AI.

01

How does Mastra AI connect to MCP servers?

Create an MCPClient with the server URL and pass it to your agent. Mastra discovers all tools and makes them available with full TypeScript types.
02

Can Mastra agents use tools from multiple servers?

Yes. Pass multiple MCP clients to the agent constructor. Mastra merges all tool schemas and the agent can call any tool from any server.
03

Does Mastra support workflow orchestration?

Yes. Mastra has a built-in workflow engine that lets you chain MCP tool calls with branching logic, error handling, and parallel execution.

Connect PharmWare to Mastra AI

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