Skip to main content
Glama
plant-intel-mcp

plant-intel-mcp

by wyattlindsey

Related Servers

Alternatives to plant-intel-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      A local-first MCP server for tracking indoor horticulture metrics, enabling cold-stratification timelines, ericaceous soil pH validation, and transplant-shock recovery through a LangGraph agent with a local LLM.
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      MCP server for HortusFox self-hosted plant management system, exposing 38 tools to manage plants, locations, tasks, inventory, calendar, chat, and backups via natural language.
      38
      8 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that gives AI agents grounded access to US natural-hazard data — weather alerts, forecasts, earthquakes, and FEMA flood zones — from free, keyless US government APIs.
      MIT
    • A
      license
      A
      quality
      F
      maintenance
      MCP server for agriculture and farming data. 8 tools: soil conditions (temperature, moisture), crop weather forecasts, historical climate data (NASA POWER, since 1981), global agriculture statistics (World Bank, 20+ indicators), and food product database (Open Food Facts, 3M+ products). All APIs free, no keys required.
      8
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Exposes eighteen garden-planning tools to AI agents over stdio, enabling crop calendar and planting-window lookups, companion planting graphs, crop rotation and succession planning, pest and disease intelligence with beneficial-insect cross-references, and USDA zone plus climate classification. All data is curated and served offline, so agents can answer climate-aware scheduling questions without live API calls.
      1
      MIT

    TDQS

    A4.4/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool targets a distinct operation: searching plants, retrieving details, computing planting windows, and checking companions. There is no overlap in purpose; the tools chain together via the search_then_detail flow, making selection unambiguous.

    Naming Consistency5/5

    All tool names follow a consistent pattern: a noun ('plant') modified by a descriptor ('details', 'intel', 'window', 'check'). The names are clear, descriptive, and follow a predictable schema, with no mixed conventions or vague verbs.

    Tool Count4/5

    Four tools is a lean but coherent set for a plant-intel domain. Each tool covers a distinct need (search, details, planting time, companionship), so none feel redundant. A fifth tool for bulk or batch queries might be additive, but the current count is appropriate for the niche scope.

    Completeness4/5

    The server covers the primary lifecycle: identify a plant, retrieve its profile, plan its planting window, and assess its compatibility with neighbors. Notable gaps include a missing tool for updating or managing the data (e.g., adding a custom plant or saving a garden plan), but the core research-oriented use case is fully covered.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues