Koskamo

PlantLab MCP

The PlantLab MCP server enables AI assistants to perform plant health diagnoses by sending photos to PlantLab's custom-trained models. It provides tools to list supported diagnoses, check usage limits, and analyze plant images for conditions and confidence scores, ensuring no image retention by the service.

Endpoint and access

OAuth sign-in: the first time you connect, your client opens the vendor's own authorization prompt in a browser.

PlantLab MCP logo, by PlantLabVendor evidenceStreamable HTTPOAuth sign-inEndpoint checked 2026-10-26Operated by PlantLab
You need:Sign in at plantlab.ai and create an API key in your dashboard.Leave Authentication on OAuth .
MCP endpoint (Streamable HTTP)
https://mcp.plantlab.ai
Vendor documentation

What you can do with it

  • Diagnose plant health from photos
  • List supported plant diagnoses
  • Check daily and monthly usage allowance

Source and maintenance

Vendor evidenceRegistry 0.1.1

Tools

Reported by the attributed source; not independently observed by Koskamo.

No tool definitions available.

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · registry · passed · metadata changed · Source metadata updated
  • · backfill · recorded · Pre-expansion baseline; unobserved rich metadata remains unknown

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http plantlab-mcp https://mcp.plantlab.ai

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add plantlab-mcp --url https://mcp.plantlab.ai

Cursor

Merge this server into .cursor/mcp.json in your project, then enable plantlab-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "plantlab-mcp": {
      "url": "https://mcp.plantlab.ai"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "plantlab-mcp": {
      "type": "streamableHttp",
      "url": "https://mcp.plantlab.ai",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start plantlab-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "plantlab-mcp": {
      "type": "http",
      "url": "https://mcp.plantlab.ai"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http plantlab-mcp https://mcp.plantlab.ai

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.
Claude Desktop configuration
{
  "mcpServers": {
    "plantlab-mcp": {
      "url": "https://mcp.plantlab.ai"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "plantlab-mcp": {
      "serverUrl": "https://mcp.plantlab.ai"
    }
  }
}

Let your agent find its tools

Find servers like PlantLab MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Do you run PlantLab MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing