PharmWare MCP Server for CrewAI 12 tools — connect in under 2 minutes
Connect your CrewAI agents to PharmWare through Vinkius, pass the Edge URL in the `mcps` parameter and every PharmWare tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.
ASK AI ABOUT THIS MCP SERVER
Vinkius supports streamable HTTP and SSE.
from crewai import Agent, Task, Crew
agent = Agent(
role="PharmWare Specialist",
goal="Help users interact with PharmWare effectively",
backstory=(
"You are an expert at leveraging PharmWare tools "
"for automation and data analysis."
),
# Your Vinkius token. get it at cloud.vinkius.com
mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)
task = Task(
description=(
"Explore all available tools in PharmWare "
"and summarize their capabilities."
),
agent=agent,
expected_output=(
"A detailed summary of 12 available tools "
"and what they can do."
),
)
crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)
* 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.
When paired with CrewAI, PharmWare becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call PharmWare tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.
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 CrewAI 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 CrewAI via MCP
Follow these steps to integrate the PharmWare MCP Server with CrewAI.
Install CrewAI
Run pip install crewai
Replace the token
Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com
Customize the agent
Adjust the role, goal, and backstory to fit your use case
Run the crew
Run python crew.py. CrewAI auto-discovers 12 tools from PharmWare
Why Use CrewAI with the PharmWare MCP Server
CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with PharmWare through the Model Context Protocol.
Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools
CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime
Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls
Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports
PharmWare + CrewAI Use Cases
Practical scenarios where CrewAI combined with the PharmWare MCP Server delivers measurable value.
Automated multi-step research: a reconnaissance agent queries PharmWare for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff
Scheduled intelligence reports: set up a crew that periodically queries PharmWare, analyzes trends over time, and generates executive briefings in markdown or PDF format
Multi-source enrichment pipelines: chain PharmWare tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow
Compliance and audit automation: a compliance agent queries PharmWare against predefined policy rules, generates deviation reports, and routes findings to the appropriate team
PharmWare MCP Tools for CrewAI (12)
These 12 tools become available when you connect PharmWare to CrewAI via MCP:
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
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
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
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
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
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)
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
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
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
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
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
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 CrewAI
Ready-to-use prompts you can give your CrewAI agent to start working with PharmWare immediately.
"Show me all cannabis samples currently in testing and their expected completion dates."
"List all pending Certificates of Analysis awaiting review and signature."
"Check the integration status with state regulatory APIs and WeedMaps CoA publishing."
Troubleshooting PharmWare MCP Server with CrewAI
Common issues when connecting PharmWare to CrewAI through the Vinkius, and how to resolve them.
MCP tools not discovered
Agent not using tools
Timeout errors
Rate limiting or 429 errors
PharmWare + CrewAI FAQ
Common questions about integrating PharmWare MCP Server with CrewAI.
How does CrewAI discover and connect to MCP tools?
tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.Can different agents in the same crew use different MCP servers?
mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.What happens when an MCP tool call fails during a crew run?
Can CrewAI agents call multiple MCP tools in parallel?
process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.Can I run CrewAI crews on a schedule (cron)?
crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.Connect PharmWare with your favorite client
Step-by-step setup guides for every MCP-compatible client and framework:
Anthropic's native desktop app for Claude with built-in MCP support.
AI-first code editor with integrated LLM-powered coding assistance.
GitHub Copilot in VS Code with Agent mode and MCP support.
Purpose-built IDE for agentic AI coding workflows.
Autonomous AI coding agent that runs inside VS Code.
Anthropic's agentic CLI for terminal-first development.
Python SDK for building production-grade OpenAI agent workflows.
Google's framework for building production AI agents.
Type-safe agent development for Python with first-class MCP support.
TypeScript toolkit for building AI-powered web applications.
TypeScript-native agent framework for modern web stacks.
Python framework for orchestrating collaborative AI agent crews.
Leading Python framework for composable LLM applications.
Data-aware AI agent framework for structured and unstructured sources.
Microsoft's framework for multi-agent collaborative conversations.
Connect PharmWare to CrewAI
Get your token, paste the configuration, and start using 12 tools in under 2 minutes. No API key management needed.