Pondlog Garden
Legacy garden-data MCP from Pondlog—only install if you maintain an old project; new work should use @cropgraph/mcp via npx @cropgraph/mcp per upstream deprecation notice.
Overview
pondlog-garden is a deprecated MCP server for the Build phase that was replaced by @cropgraph/mcp for garden data integrations.
What is this MCP server?
- Officially DEPRECATED: upstream directs new users to @cropgraph/mcp (npx @cropgraph/mcp).
- Former npm identifier @pondlog/mcp-garden at version 0.3.4 with stdio transport.
- Part of andrewschristison/pondlog monorepo alongside aggregate Pondlog and eBird servers.
- Do not start new garden MCP integrations on this package—migrate to Cropgraph MCP for maintained tools.
- Retained in catalog so builders recognize legacy configs in old Claude/Cursor MCP JSON.
- Package @pondlog/mcp-garden version 0.3.4 marked DEPRECATED in server description
- Replacement command: npx @cropgraph/mcp
- stdio transport in published schema
What problem does it solve?
Old MCP configs still point at @pondlog/mcp-garden, leaving builders on an unmaintained path while Cropgraph is the supported garden MCP.
Who is it for?
Maintainers decoding legacy Pondlog MCP setups who need a clear migration target to Cropgraph.
Skip if: New garden or agronomy apps—install @cropgraph/mcp directly and do not add pondlog-garden.
What do I get? / Deliverables
After you swap the server entry to npx @cropgraph/mcp, your agent uses the maintained garden tools instead of the deprecated Pondlog package.
- Clarity that @cropgraph/mcp is the supported replacement
- Migration off @pondlog/mcp-garden v0.3.4 configs
- Avoided new debt on deprecated garden MCP
Recommended MCP Servers
Journey fit
Still cataloged under Build integrations because it was a garden-focused MCP bridge, but canonical placement is historical rather than recommended greenfield. Integrations documents its role as a replaced npm package (@pondlog/mcp-garden) rather than active launch or grow tooling.
How it compares
Deprecated npm MCP stub; use @cropgraph/mcp as the active garden integration, not aggregate Pondlog.
Common Questions / FAQ
Who is pondlog-garden for?
It is mainly for developers troubleshooting existing MCP configs that still reference @pondlog/mcp-garden, not for new installations.
When should I use pondlog-garden?
You should not use it for new work; migrate to Cropgraph MCP when you need garden data tools in your agent.
How do I add pondlog-garden to my agent?
Do not add it—replace any pondlog-garden entry with npx @cropgraph/mcp per the deprecation notice, then refresh your Claude Code or Cursor MCP server list.