Gardener's Almanac

app.gardeners-almanacPublished by gardeners-almanac.appOfficial publisherv2026.929.12Updated Oct 30, 2026

Your vegetable garden: what's growing, what you've done, what needs doing next and when to water.

VerifiedStreamable HTTPWeb executableLocation & Lifestyle

Overview

AI-generated overview

A remote MCP server for a vegetable garden: it lets an assistant see what is growing, what has been done, what needs doing next, and when to water.

What you can do
  • Track what is growing in the vegetable garden and what has already been done there.
  • See what needs doing next and when watering is due.
  • No tool list is published, so the exact actions an assistant can take are not documented; the description points to garden status, activity and care scheduling.
When to use it
Useful if you keep a vegetable garden in this service and want an assistant to answer questions about current plantings, past garden work, upcoming tasks and watering timing.
Requirements
A remote endpoint at gardeners-almanac.app over streamable HTTP; OAuth authentication is required, so an account with the provider is needed. No environment variables or headers are declared.
Before you install
The server requires OAuth sign-in, so the assistant gets access to your garden account data. No tool list is published, so it is unclear whether tools only read garden records or also change them; check before connecting.

Installation

In SourceWeft

  1. Open Gardener's Almanac in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/app.gardeners-almanac%2Fgardeners-almanac/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "gardener-s-almanac": {
      "type": "http",
      "url": "https://gardeners-almanac.app/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v2026.929.12LatestSep 30, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.