Connect your WeMush account to Claude AI for intelligent mycology research assistance. The WeMush Claude Connector enables Claude to access your research projects, specimens, and cultivation data to provide personalized insights and recommendations.
The WeMush Claude Connector uses the Model Context Protocol (MCP) to securely connect your WeMush account with Claude AI. Once connected, Claude can:
Before connecting WeMush to Claude, you need:
https://wemush.com/mcpDemo: Connecting WeMush to Claude and querying your mycology data
When you connect, you'll be asked to approve specific scopes:
| Scope | What It Allows |
|---|---|
profile:read | View your research profile and activity |
research:read | View research projects and your enrollments |
research:write | Join projects and submit observations |
specimens:read | View your specimen data |
observations:read | View research observations |
observations:write | Create new observations |
analytics:read | Access aggregated analytics |
catalog:read | Browse species and strain catalog |
You can revoke access at any time from WeMush Settings > Connected Apps.
The WeMush connector provides 50 tools organized into six categories:
| Tool | Description |
|---|---|
list_research_projects | List available research projects with filtering |
get_research_project | Get detailed information about a specific project |
enroll_in_project | Join a recruiting research project, optionally into an experiment group (by id or name); specimenIds are recorded as taking part and specimenAssignments puts individual specimens into their own groups; draft projects return INVALID_STATE |
assign_specimens_to_group | Put up to 100 of your specimens into experiment groups of a project you're enrolled in (per-specimen groups override your enrollment group), move or remove them; dryRun |
withdraw_from_project | Leave a research project |
get_my_enrollments | List your research project enrollments |
create_research_project | Create a draft research project with scheduled dates and experiment groups. Optional organizationId must be one of your active organizations (else NOT_FOUND). If omitted: with exactly one active organization the project is created in it; with several, ORGANIZATION visibility requires organizationId (VALIDATION_ERROR lists your organization ids and names) and PRIVATE/PUBLIC projects get no organization |
| Tool | Description |
|---|---|
create_observation | Submit a research observation |
list_my_observations | List your submitted observations |
get_observation | Get details of a specific observation |
update_observation | Update an observation (before verification) |
delete_observation | Delete an observation (before verification) |
move_specimen_observation | Move a specimen observation (or some of its photos) logged against the wrong specimen to the right one |
delete_specimen_observation | Delete a specimen observation, or remove one of its photos (undoable for 30 minutes) |
undo_observation_correction | Undo a specimen observation delete, photo removal or move using its undo token |
| Tool | Description |
|---|---|
list_my_specimens | List your specimens with filtering; compact `view: "summary"` or chosen `fields`, and `groupBy` strain/status/type counts |
get_specimen_details | Get detailed specimen information |
get_specimen_lineage | View specimen ancestry and descendants |
get_specimen_analytics | Get predictions and analytics for a specimen |
record_specimen_observation | Record an observation on a specimen |
get_specimen_history | View observation history for a specimen |
bulk_update_specimens | Change status, location, colonization, container, visibility, linked media recipe (`mediaRecipeId`, `null` clears) or substrate/inoculum quantities (`inoculumVolumeMl`, `substrateWetWeightG`, `substrateDryWeightG`), or link a store order (e.g. #1006), on up to 100 specimens at once, by id/code or by filter (supports dry run). Receive pre-registered PLANNED stock by setting status ACTIVE |
bulk_archive_specimens | Archive up to 100 specimens at once with a reason, by id/code or by filter (supports dry run) |
bulk_record_observations | Record the same observation on up to 100 specimens, optionally updating status or colonization |
batch_get_specimens | Get details for up to 50 specimens in one call, including substrate/inoculum quantities |
compare_specimens | Compare related specimens (siblings, same strain, or a list) and flag outliers |
audit_specimens | Find data gaps and cultivation-health issues across your specimens, with suggested fixes — including stale ACTIVE specimens to archive and future or typo dates |
triage_contamination | From one specimen, rank related specimens at risk of contamination and suggest follow-up actions |
derive_specimens | Create child specimens from a parent (e.g. a plate into grain jars), or a whole plan of several types in one call (up to 100), with lineage, organization and visibility inherited, a starting colonization status, per-group substrate/inoculum quantities, and an optional store-order link; a PLANNED parent plans a round of PLANNED children before the stock arrives; undoable (supports dry run) |
log_harvest | Log a harvest weight and quality on a grow bag or its linked specimen |
bulk_log_harvests | Log up to 100 harvests at once (supports dry run) |
undo_bulk_operation | Undo a recent bulk specimen change or derive using the operation ID it returned (within 24 hours); derived specimens with no activity since are archived |
| Tool | Description |
|---|---|
get_project_analytics | Get aggregated project statistics (k-anonymous; organizers and org members of private/organization projects see their own data without the participant threshold) |
get_outcome_breakdown | View outcome distribution data |
get_equipment_analysis | Analyze equipment correlation |
get_group_comparison | Compare experiment groups, grouping data by per-specimen assignment when present, else enrollment group |
get_research_trends | View research activity trends |
| Tool | Description |
|---|---|
search_species | Search species in the catalog |
get_species_details | Get cultivation information for a species |
search_strains | Search strains by name, vendor alias, or description (case- and punctuation-insensitive: "Lions Paw" finds "Lion's Paw") |
get_strain_details | Get strain-specific information |
Strain search also matches a strain's aliases, so vendor and trade names resolve to the catalog strain they refer to. Catalog upkeep (adding aliases, moving a strain to the correct species, merging duplicate strains) is done by WeMush administrators with the separate WeMush Admin connector's update_strain and merge_strains tools. A merge moves every specimen, grow operation, and other record to the surviving strain, keeps the old names as aliases, and archives the duplicates instead of deleting them.
| Tool | Description |
|---|---|
get_my_research_profile | View your research profile and statistics |
get_research_activity_feed | View your recent activity feed |
The connector includes five pre-built prompts for common workflows:
"Use the analyze_cultivation prompt for my grain spawn jar"
Claude will fetch your specimen details, recent observations, and strain information to provide a comprehensive analysis with recommendations.
"Give me an overview of the Substrate Colonization Study"
Get a summary of any research project including participation statistics, key findings, and how to contribute.
"Compare Blue Oyster and Italian Oyster strains"
Claude will present a structured comparison of cultivation requirements, expected yields, and difficulty levels.
"Help me troubleshoot green contamination on my grain spawn"
Get diagnostic assistance for common cultivation problems with actionable solutions.
"Summarize my research activity this month"
View a summary of your contributions, observations, and project participation.
The connector provides access to three resources:
| Resource | Description |
|---|---|
| Cultivation Guide | Best practices for mushroom cultivation |
| Research Glossary | Definitions of mycology and research terms |
| My Research Profile | Your profile, enrollments, and statistics |
Research analytics use k=5 anonymity, meaning data is only shown when at least 5 participants share similar characteristics. This protects individual privacy while enabling meaningful research insights.
Claude can only access data within the scopes you explicitly approve during authorization. You control what data is shared.
All data access through the connector is logged for security auditing. You can review access logs in your WeMush account settings.
You: "What mycology research projects can I join?"
Claude: Uses list_research_projects to find recruiting projects, then describes options and can enroll you with enroll_in_project.
You: "My grain jar is 75% colonized, can you record that?"
Claude: Uses list_my_specimens to find your grain spawn, then record_specimen_observation to log the colonization progress.
You: "What temperature should I fruit my Blue Oyster block at?"
Claude: Uses search_strains and get_strain_details to find optimal fruiting conditions for Blue Oyster mushrooms.
If you're having trouble connecting:
If Claude reports permission errors:
If your data isn't appearing:
The WeMush Mycology Assistant skill is open source and available for self-hosting, customization, or contribution.
If you want to run your own instance of the WeMush MCP server:
We welcome contributions! Whether you want to add new tools, improve existing functionality, or fix bugs:
See the repository's CONTRIBUTING.md for detailed guidelines.
Need help with the WeMush Claude Connector?
For issues specific to Claude AI, visit support.anthropic.com.
https://wemush.com/mcp (the previous /api/mcp/research/mcp URL still works)Initial Release