For your AI

What an assistant needs to know about Plants

What the assistant you connect reads to work well. Public, so you can point yours here first.

You can skip this section. Share it with your AI when you want help getting started.

For your AI

You are connecting to one person's private plant record. You reason and draft; Plants stores what you and they write, dated and signed with who wrote it.

The address, as a remote MCP server

https://www.assistwithplants.com/mcp

That exact hostname, including the www. Copying it connects nothing: pasting it into an assistant starts a sign-in in the person's own browser, and their sign-in is the approval. Connect your AI walks through it.

Tools
43
Read
19
Write
24
Switches
7

Read by your AIcatalogue cat_1r5nhmy

How to work well here

  1. Orient once. Read the workspace overview and the person's preferences at the start, not between every save.
  2. Find before creating. Search for the plant, species and place first. Two lemons are two Plants sharing one Species.
  3. Answer now, save as you go. Give the useful answer first, with its uncertainty. Save a sparse record straight away and add detail as it arrives.
  4. Batch. A garden walk is one observations call; a nursery haul is one plant-records call.
  5. Put facts where they belong. Kind-level knowledge on the Species, one tree's history on the Plant, what was seen today on an Entry, long research in a Document linked to all of them.
  6. Say what you did not check. Record sources, regions, dates and gaps. An unvisited source stays unvisited.
  7. Correct by superseding. Never overwrite a reading or a date: save a new entry that points at the one it replaces.
  8. Suggest; do not decide. Care advice is a proposal. The person's decision and action are theirs to record.
  9. Tell the person what you saved. Name the records and give their links.

The full briefing is at /ai, and as plain text at /ai.txt.

The first calls of a session

5 calls
  1. plants_list_directivesWhat the person marked ready for you. The catalogue says to call it first.
  2. plants_get_workspace_overviewOnce, at the start: their Preferences, standing preferences and display units, what is due, and what to call next.
  3. plants_search_workspaceBefore you create anything. Similar names are a question for the person, not a new record.
  4. plants_save_observationsWhat was seen or done, in one batched call — a garden walk is one save, not twenty.
  5. plants_manage_connectionWhen a call is refused: see what this connection holds, and hand the person the link to change it.

The toolset

43 tools · 19 read · 24 write

Every tool the connection answers, read from the catalogue itself, grouped by the switch each one rides. A tool answers only while that switch is on for the connection — a refusal means the person changed it, not that the tool is broken.

Read your plants and their entries13

  • plants_search_workspaceRead

    Search your active records and return the exact words, dates, authors, and stable references.

  • plants_get_record_contextRead

    Open one active record with its summary, history, relationships, care context, and sources.

  • plants_get_entryRead

    Read back one of your journal entries in full, with its corrections.

  • plants_find_plantsRead

    Look up which of your plants a request is about.

  • plants_area_walkRead

    Read a whole area of your garden back in one go, the way you walk it.

  • plants_recall_seasonRead

    Look back at what you wrote about a plant around this same week in earlier years.

  • plants_list_speciesRead

    List your real Species records and how many visible plants link to each one.

  • plants_list_documentsRead

    Browse the reusable research Documents available to this connection.

  • plants_search_documentsRead

    Find prior research before asking your AI to repeat it.

  • plants_read_documentRead

    Read the exact full text of one permitted research Document.

  • plants_list_libraryRead

    Browse saved Library shelf pointers without opening their content.

  • plants_list_care_dueRead

    See which of your plants are due for water, in the order you would walk round them.

  • plants_read_resourceRead

    Read your Resources, watering lines and their context.

Look at their photos1

  • plants_get_media_batchRead

    Read photos on an authorized Plant, or selected photos and voice notes on a Queue request.

Save its own work, and keep your records16

  • plants_save_observationsWrite

    Write dated observations and measurements into your journal as you dictate them.

  • plants_save_speciesWrite

    Create and correct real Species records, and resolve plant identity claims honestly.

  • plants_save_documentsWrite

    Save substantial attributed research as reusable, linked Documents.

  • plants_save_plant_recordsWrite

    Add a plant, correct its name or placement, or record what you believe it is.

  • plants_set_primary_imagesWrite

    Choose the primary image your record leads with; every change is stale-protected and replay-safe.

  • plants_attach_photoWrite

    Attach a license-clean photograph to an approved Plant, Species, Product, or Tool, marked as attached by it rather than by you. Only you can remove it.

  • plants_save_site_recordWrite

    Write down the things that are true of your whole garden — zone, frost dates, the lot, which way it faces — so every later answer starts from the same facts.

  • plants_save_placesWrite

    Save a public or third-party spot for something you encountered, separate from where you live; or correct an older Place.

  • plants_save_growing_contextsWrite

    Record your real Property, its named Areas, and the Ground Plot/Bed, Planter, or Pot/Container each plant grows in without turning any of them into the wrong kind.

  • plants_save_listsWrite

    Keep your Lists — the records you think about together, or a checklist to tick off — so advice about them arrives once instead of once each.

  • plants_save_studyWrite

    Organise your Lists' flashcards: say what photos show, link look-alike plants, and write question cards with sources. It never schedules anything.

  • plants_save_resourcesWrite

    Keep Resource context and shared watering settings, with history.

  • plants_save_equipmentWrite

    Keep a record of the products and tools you use — what you bought, what its label says — so later answers can name them exactly.

  • plants_record_human_statesWrite

    Write down a decision you made or care you performed, as you report it.

  • plants_save_care_plansWrite

    Write down how often and how much to water a plant, so the answer stops living in a chat.

  • plants_log_careWrite

    Write down a watering or feeding you tell your assistant about, with the date and the amount.

Read and answer the queue2

  • plants_list_directivesRead

    See which of your requests you marked ready for your AI.

  • plants_queue_for_laterWrite

    Write down work you asked it to do later, as ordinary requests waiting in your Queue. Each one says your AI wrote it down at your request, and nothing starts until you ask.

Propose suggestions3

  • plants_suggest_directivesWrite

    File suggestions you might want to pursue, on your AI Suggestions page rather than in your Queue. Each one waits for you to make it your own request or put it down, and the order it recommends is shown as its opinion.

  • plants_suggest_duplicateWrite

    Ask whether two visible Plant records describe one individual. Nothing changes unless you accept the exact reversible action on AI Suggestions; nothing ever merges or deletes.

  • plants_suggest_tendencyWrite

    Ask whether it has read how you like to work — one line at a time, on your AI Suggestions page, in the exact words it would keep. Nothing is stored unless you accept, it can only ever shape how answers are written, and you can retire any of them.

Read and answer the queue + Read your plants and their entries4

  • plants_get_workspace_overviewRead

    See a compact active-workspace summary: your Queue, upcoming care, and suggestions.

  • plants_get_contextRead

    Read the brief you prepared for one request.

  • plants_start_directiveRead

    Open one request with its brief, the plant's record, and the answer format.

  • plants_get_evidenceRead

    Read the dated observations and research behind that brief.

Read and answer the queue + Save its own work, and keep your records2

  • plants_save_complete_resultWrite

    Save one complete answer against a request, and move it to Done. When it suggests several things, they arrive in the order it would do them — an opinion for you to weigh, not work assigned to you.

  • plants_update_resultWrite

    Correct or add to an answer it already saved, including changing its mind about what matters most. Your own call on each suggestion stays yours.

No switch needed2

  • plants_archive_plantsWrite

    Move a plant out of your active list, or bring it back. Nothing is deleted.

  • plants_manage_connectionWrite

    Look up what it is allowed to do or ask you for a change. It cannot change its own authority.

What each permission covers

7 switches

Seven switches, chosen per assistant by the person on Connect your AI. Signing in normally turns on everyday garden work; archiving and every change to a connection's reach stay the person's.

  • Read your plants and their entries

    Names, species, where they live, and what you have written about them

    This is the floor. With it off, the assistant cannot see any of your records — it answers about plants in general, exactly as it would with no connection at all.

  • Look at their photos

    With the date and the entry each one belongs to

    Photos are how an assistant recognises what you are describing — a cupped leaf, a scale insect, the colour of chlorosis. It reads the date too, so it can tell what changed since. A voice note you leave on a job travels on this same switch: your AI hears the recording, and nothing here turns it into text first.

  • Save its own work, and keep your records

    Its research and answers, your journal entries, photographs it attaches — all signed with its name

    This is the one switch behind every kind of writing. Its own research and answers; dated observations and measurements as you dictate them; a plant added, or its name or place corrected; a photograph attached to a record; and the decisions and care you tell it you carried out, recorded as reported by you. Everything carries its model name and the date, on the record it belongs to, and nothing it writes can overwrite or edit a word of yours.

  • Read and answer the queue

    The jobs you leave it from the garden, and the ones you ask it to write down for you

    The queue only moves when you tell an assistant to check it. This ability lets it look when asked, and post the answer back onto the right record. It also lets it write a job down for you mid-conversation — say “add that to the list” and it lands in Waiting on AI as your own request, marked as left by your AI at your request, so it does not have to disappear into a long job to keep hold of it. Nothing it writes down starts on its own, and you can edit, archive or delete any of it.

  • Propose suggestions

    As questions for you to decide on, never as actions

    A proposal is a card you accept or decline; it cannot act on its own conclusion. Proposing a conclusion about a record — an insight — is not in the connector yet: this switch is ready for it and it arrives with a connector update, announced at /updates.

  • See where your garden is

    The location context you recorded, at the precision this connection carries

    On, an assistant may be told where things are as precisely as you recorded them — which is what lets research say “in your climate” instead of hedging across three continents. Off, it is told nothing about where anything is, and a brief says by name what it withheld. There is no middle setting: this switch is on or it is off.

  • Read plants you marked private

    Records you have deliberately held back

    New normal-care connections can read records marked private because this is your private continuity workspace. This switch still lets you narrow one existing connection without changing any other assistant.

What differs between AI apps

6 capabilities

Plants names no “supported” apps: any AI that can use the tools can connect. What differs is a handful of capabilities, observed across the Assist With family as of September 2026.

CapabilityWhat has been observedWhat to do
Hearing a voice noteNo client is proven to transcribe reliably; one invented words over silence.Say if you cannot process audio, and ask the person what they said. Never present a guess as their words. A Pro account may carry a transcript labelled machine-made.
Uploading a photo fileSome apps can see a photo but cannot hand its file to a tool.Use the first-party upload path on the Plants host. If you cannot send the file, reserve a pending photo slot and the person adds it from their phone.
Photos pasted into chatChat apps often re-encode photos and strip the capture time and location.Never treat the message time as the capture time. Ask, or let the person upload the original to the site.
New tools after a releaseA running conversation keeps its old tool list.Start a new conversation after a Plants release.
Adding a connector on a phoneSome mobile apps can use a connector but cannot add one.Set it up once from a desktop or the web.
Approval prompts on every callSaves were lost when nobody could answer the prompts in time.Batch saves, and suggest an “always allow” for Plants tools if the person wants one.

What Plants promises

6
  • Plants has no AI of its own. Every sentence on a record was written by the person or by an assistant they connected, and says which.
  • Nothing runs while the person is away. A Queue request waits until an AI they connected picks it up.
  • Leaving a request grants an assistant nothing it could not already do.
  • Corrections are additive: the original stays readable beside the one that supersedes it.
  • Archiving deletes nothing, and an archived record can be brought back.
  • Each Assist site keeps its own records. Nothing crosses between them unless the person asks their AI to carry it — and then say where it came from.

What no approval allows

8

However much the person switches on, a connected assistant can never:

  • Reach another account, or name yours. Which workspace it is in comes from the credential you approved, not from anything it sends.
  • Ask for context you did not select, or for a finer location than you chose. Neither is a request a tool can make, and writing does not widen reading: an assistant may name a place you or it defined — "the north wall bed" — and put a plant in it, and it still learns nothing about where you live that you did not choose to disclose. A place name is a string, not a coordinate, and what it may be told back is governed by your precision setting exactly as before.
  • Receive a link to your files. A selected photograph arrives as a picture and a voice note you left on a job arrives as the recording itself — the file, never an address for it. Unless your account has Pro, nothing here transcribes a recording, so what your AI hears is the whole of what it is given; on Pro, a transcript labelled machine-made may travel beside it, never in its place. A recording you uploaded from somewhere else is the one that may not travel at all: audio can carry a coordinate in its own bytes and no strip removes it, so unless you have disclosed location to that assistant, the file is handed over only after its bytes have been read and found to carry no place — and it is named and withheld otherwise, never quietly dropped. Every other kind of file stays here and is not even named.
  • Export your records, or delete anything, ever. No approval this product can issue grants either, and none is planned. Archive/Restore is included by default and reversible: nothing is removed. You can limit it at /settings/ai.
  • Erase or rewrite an observation you already made. A correction it writes is a new dated record naming the one it supersedes, and your original words stay readable beside it.
  • Decide anything. It can write down a decision you made or care you performed, and the record names you as the one who decided and names the assistant as the one who merely wrote it down.
  • Change your account, your sign-in, your billing, or anything about this site's settings.
  • Share, publish, message, schedule, purchase, control equipment or irrigation, apply a treatment, diagnose, or take any other action outside this record.

The standing rules

7

The exact sentences a connected assistant is served when it asks plants_manage_connection to describe its own authority, printed from the same source.

  • Normal authority after verified OAuth: plants:read, plants:media:read, plants:result:write, plants:records:write, plants:archive, across every ordinary record category (observations, measurements, research, careContext, identityClaims, relationships, mediaMetadata, humanStates) and the person's permitted location context, with no end date by default. Full access includes future tools. Plants receipts this authority separately from OAuth identity. Approval-first accounts still require a confirmation click.
  • That baseline is the "ordinary-care" policy, version 2 — the product owner's deliberate decision of 2026-10-22, reaffirmed 2026-10-22. Every grant records which policy issued it and when; describe returns that provenance as signInBaselinePolicy.
  • Archive/Restore is included. Fewer scopes or an end date are opt-in choices at /settings/ai.
  • Requesting access never changes or removes live authority. It files one exact request and returns a link for the person; only their click can approve it.
  • No assistant operation changes live permission or authority. To narrow, widen, revoke, or change connection policy, the person acts in Your AI settings.
  • A connected client may still apply its own per-tool prompt or block policy; Plants does not override client-side approval controls.
  • No approval this product can issue ever allows export, permanent deletion, sharing, messaging, purchasing, scheduling, equipment control, or any action outside this record.