plant-intel-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_plantsA | Search the Perenual species catalogue by name and return candidate species with ids. Use the returned id with plant_details, companion_check, or planting_window rather than passing a name again -- resolving a name costs an extra upstream request. |
| plant_detailsA | Full care profile for one species: sun, water, hardiness zones, mature height, edibility, toxicity to people and pets, and known pests. Fields the configured Perenual plan withholds are reported as null and named in |
| planting_windowA | Frost envelope and hardiness fit for a plant at a location. Given coordinates it derives last spring frost, first autumn frost, season length, and the USDA zone from ten years of observed daily minima. Supply days_to_maturity and frost_tolerance from your own crop data to also get transplant and sow-by dates -- no source this server reads publishes those, so they are never guessed. |
| companion_checkA | Whether two plants should share a bed, with the mechanism behind the answer. A "bad" verdict is derived from shared botanical family (rotation and soilborne disease) or overlapping pest susceptibility, never from folklore. A "good" verdict comes from a documented Permapeople listing when that source is configured. Every matched reason is returned, including any the verdict overrode. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/wyattlindsey/plant-intel-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server