Siltwell is answering right now. Last checked 1 min ago. It exposes 32 tools.
Your garden notebook: ask about your beds, plantings, harvests and frost dates, and log your work.
Uptime history
13 days of history
13 days agonow
100.0%
Uptime 24h
92 of 92 checks
32
Tools
read from the server
543 ms
Response time
average over 24h
open, no key
Access
streamable-http
Nothing serious here today
Today is the operative word: we check Siltwell every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 1 min ago.
run in your terminal
claude mcp add garden --transport http https://app.siltwell.com/mcpSettings → Connectors → Add custom connector, then paste this address
https://app.siltwell.com/mcp~/.codex/config.toml
[mcp_servers.garden]
url = "https://app.siltwell.com/mcp".cursor/mcp.json
{
"mcpServers": {
"garden": {
"url": "https://app.siltwell.com/mcp"
}
}
}.vscode/mcp.json
{
"servers": {
"garden": {
"type": "http",
"url": "https://app.siltwell.com/mcp"
}
}
}Available tools 32
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
bed
create_bed
Add a garden bed. `type` is one of outdoor_bed (in-ground), raised_bed, greenhouse, grow_light_shelf, pot. Dimensions (lengthCm/widthCm/heightCm) are optional. Use when the user wants a new bed or planting area.
delete_bed
Remove a bed from the garden. Siltwell archives it: it leaves the bed lists in the app and in these tools, its care schedules stop, and planned plantings queued for it are skipped. Past weather history still shows its name. The app has no way to restore it. Blocked while the bed has active plantings; remove or finish those first. Identify by bed name.
get_bed_layout
Read a bed's layout grid: the bed's dimensions (cm) plus each placed planting's footprint (xCm, yCm from the bed's top-left; wCm × hCm), and any active plantings not yet placed. Use to reason about space — e.g. "is there 60 cm free at the front of Bed 2?". Positions are written by place_planting.
update_bed
Change an existing bed's name, type, or dimensions. Identify the bed by its current name. Use when the user wants to rename a bed, change its type, or set/adjust its dimensions.
lookup
lookup_frost_dates
Average last spring frost, average first fall frost and hardiness zone for any place, from 10 years of weather records. Works without a Siltwell account. Dates are MM-DD. For the signed-in user's own garden, get_plan returns the garden's zone and frost dates, with the frost dates adjusted for its microclimate.
lookup_frost_risk
Forecast lows for the next 7 days at any place and the nights at risk of frost. Each frost night is dated by the morning its low falls on, so protect plants the evening before that date. Works without a Siltwell account. For the signed-in user's own garden, get_forecast returns this forecast with the garden's microclimate adjustment applied.
lookup_growing_season
Frost-free season length and seasonal growing degree days at any place, and whether heat-loving crops get enough heat to ripen. Works without a Siltwell account. For the signed-in user's own garden, get_plan returns the microclimate-adjusted frost dates that bound its season, and get_history returns its daily growing degree days.
lookup_planting_windows
When to start seeds indoors, plant out, and sow for a fall harvest at any place, crop by crop, with the days left to sow today. Works without a Siltwell account. Dates are YYYY-MM-DD. Without crops, it returns the 30 crops with the soonest next step; pass crops to see others. For the signed-in user's own garden, get_plan returns sowing and transplant windows for the garden's own plants, counted from its microclimate-adjusted last frost date.
planned
add_planned_planting
Queue a future planting for a bed as part of a succession plan — it is NOT yet sown (use add_planting for something the user already planted). Use when the user wants to plan ahead, e.g. "plan to plant more carrots in Bed 2 on August 15".
delete_planned_planting
Remove an entry from the succession plan outright (a queued future planting that hasn't been sown). This is a hard delete, not recoverable — for a planting already sown/growing, use delete_planting instead. Identify it by id (from list_planned_plantings).
list_planned_plantings
List the garden's succession plan — future plantings queued for a bed that haven't been sown yet (only status='planned'; done/skipped entries are omitted). Use when the user asks what's coming up next, what they've planned to plant, or wants to review their succession plan. For plantings already in the ground, use query_plantings instead.
update_planned_planting
Update a queued succession-plan entry: change its status (planned/done/skipped), reschedule its targetDate, or adjust quantity/notes. Identify it by id (from list_planned_plantings). Use when the user sows a planned planting (mark status done), decides to skip it, or wants to reschedule/adjust it.
planting
add_planting
Record that the user planted/sowed something: creates the plant in their catalog if new and the planting in the named bed. Passing variety replaces the variety stored on an existing plant with the same name.
delete_planting
Remove a planting from the garden. Siltwell archives it: it disappears from the app and from these tools, and its care schedules stop. Its harvests, events and photos stay stored, but the app has no way to restore it. Identify by plant name or plantingId. Use when the user says to delete/remove a planting (e.g. one added by mistake).
update_planting
Change a planting's status (active/finished/failed), notes, quantity, transplant date, variety, or MOVE it to another bed (pass bed with the target bed's name — history stays attached; any layout position is cleared, re-place with place_planting). Identify the planting by plant name or plantingId.
log
log_curing
Record that a harvested crop has finished curing (or dismiss the reminder). Use when the gardener says they've cured, dried, trimmed or stored a crop like garlic, onions or herbs.
log_event
Record something the user did or observed: watered, fertilized, transplanted, pruned, pest sighting, treatment, frost damage, or a note. Attach it to a plant's active planting via `plant`, to a bed via `bed`, or garden-wide with neither. If both plant and bed are given, the event attaches to the plant's planting.
beds
list_beds
List the garden's beds: name, type (outdoor_bed/raised_bed/greenhouse/grow_light_shelf/pot), dimensions in cm, notes, and how many active plantings each holds. Use to see what beds exist and where there may be room.
care
set_care_schedule
Create a recurring care schedule (water/fertilize/custom). Scope it to a plant (its active planting), a bed, or the whole garden. Recurrence is EITHER everyDays (e.g. 3) OR weekdays (e.g. ['monday','thursday']). Use when the user wants a repeating watering/feeding reminder. Optionally end it on a date (endsOn) or after N completions (endsAfter); use at most one.
current
get_current_conditions
Current weather at the garden (station if connected, else forecast) plus per-bed soil moisture/temperature. Use for "how is the garden right now / should I water".
events
search_events
Search the garden log: watering, fertilizing, transplanting, pruning, pest sightings, treatments, frost damage, notes. Use when the user asks when they last did something or what happened in the garden.
forecast
get_forecast
7-day forecast for the garden with overnight-low frost alerts. Use for planting timing, frost protection, watering plans.
harvest
update_harvest
Correct a logged harvest — the most-recent harvest of a plant (by name) or a specific harvestId. Edit quantity, unit, notes, or the date. Use when the user says a harvest they recorded was wrong.
harvests
get_harvests
List harvests with per-plant totals. Use when the user asks what/how much they harvested.
history
get_history
Daily weather history for the garden: min/max temp, rain, growing degree days (base 10 °C) with a cumulative total. Use for "how warm/wet has it been" and growth-progress questions.
place
place_planting
Place or move a planting on its bed's layout grid — set its position (xCm, yCm measured from the bed's top-left corner) and footprint (wCm × hCm) in centimeters. Identify the planting by plant name or plantingId. Use when the user wants to arrange, position, or move a plant within its bed. For a planting that already spans several grid squares, use the app's layout editor instead.
plan
get_plan
Upcoming sowing/transplant windows computed from the user's plant catalog and the garden's frost dates, plus zone, frost dates, and any due care tasks (watering/fertilizing, with a rain-skip hint). Use for "what should I plant/start/transplant and when" and "what care is due".
plantings
query_plantings
List the user's plantings (what is planted, where, when, how, current status). Use when the user asks what they planted, when something was sown/transplanted, or what's growing in a bed.
record
record_harvest
Record a harvest, e.g. "I picked 2 kg of cucumbers" or "2 lb of tomatoes". Resolves the plant's active planting automatically. Pounds and ounces are stored as grams.
schedule
delete_schedule
Turn off a recurring care schedule (stops its reminders). Identify it by scheduleId, or by scope — plant (its active planting), bed, or garden-wide (neither) — optionally narrowed by type (water/fertilize/custom). Use when the user says to stop a watering/feeding reminder.
season
get_season_plan
Compute the garden's rest-of-season planting schedule: every bed's next crops, chained forward to the effective first frost, deconflicted across beds with crop rotation and curated sow windows. Returns a PROPOSAL only — nothing is written; use add_planned_planting to accept a row into the succession plan. Returns every bed's chain, or one bed's full chain plus remainingCount for the rest when the garden's plan covers one bed.
soil
get_soil_readings
Latest soil moisture % and soil temperature per bed, with bed names. Use for watering/sowing decisions.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://app.siltwell.com/mcp | streamable-http | answering | 479 ms | 1 min ago |
Alternatives to Siltwell
same job, measured the same wayMinecraft
by mairwunnx
Ask an AI about your Minecraft server and let it run it: players, worlds, configs, logs.
Memoshelf
by myclaimfile
Shared notebook for AI agents: run log, notes, a pinned How-we-work page, one lane across platforms
S
Slate
by slate-hq
Your own SLATE health data in your AI assistant: read, trend, plan and log. Never suggests a dose.
Eutexa CRM
by eutexa
Search contacts, track deals, create tasks and log notes in your Eutexa CRM workspace.
petromcp
by ameyxd
Local-first MCP server: read LAS well logs and DLIS files from your own disk.
Reps
by repsworkout
Your Reps gym log in Claude or ChatGPT: workouts, PRs, progress, routines and training plans.
Tally Workout
by westvegh
iPhone strength log. Any MCP agent reads your training and plans workouts in the Tally app.
Anatome
by anatome
Log workouts and meals by telling your AI. 873 exercises, muscle diagrams, food lookup.
Siltwell — questions
Answers built from our own checks of this server.
What can Siltwell do?
It exposes 32 tools, read directly from the server on our last check. Among them: add_planned_planting, add_planting, create_bed, delete_bed, delete_planned_planting, delete_planting and 26 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README.
How MCP servers expose tools in the first place →
What is Siltwell mostly used for?
Its tools cluster around lookup, planned and bed. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is Siltwell working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 543 ms. The bar chart above shows every period we have measured.
How do I connect Siltwell?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Siltwell need an API key?
No. Siltwell completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 32 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Siltwell?
It answers our handshake in 543 ms on average, which is faster than 24% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.