Farmbrite MCP by usefulapi

Was du damit machen kannst

Für diesen Server haben wir noch keine Zusammenfassung in einfacher Sprache geschrieben. Unten stehen die Fakten, die wir aus der Registry gelesen haben.

• Verbindung: Läuft in der Cloud
• Transport: Streamable HTTP
• Kategorie: Onlineshops & Zahlungen

Installation

Wähle die KI-App, die du nutzt, und kopiere die Einstellungen.

Du brauchst

• Läuft in der CloudNichts zu installieren; die Verbindung läuft übers Internet

Welche App nutzt du?

https://farmbrite.usefulapi.io/mcp

claude mcp add --transport http farmbrite https://farmbrite.usefulapi.io/mcp

{
  "mcpServers": {
    "farmbrite": {
      "url": "https://farmbrite.usefulapi.io/mcp"
    }
  }
}

{
  "servers": {
    "farmbrite": {
      "type": "http",
      "url": "https://farmbrite.usefulapi.io/mcp"
    }
  }
}

https://farmbrite.usefulapi.io/mcp

Deine Auswahl bleibt in einem Cookie auf diesem Gerät; kein Konto nötig.

Diese Einstellungen werden aus dem Registry-Eintrag des Entwicklers erzeugt. Wenn in der README etwas anderes steht, folge der README.

Was er kann

Tool-Namen und -Beschreibungen genau so, wie der Server sie am 6. Nov. 2026 gemeldet hat. Geschrieben hat sie der Entwickler, nicht wir; wir zeigen sie als reinen Text.

• farmbrite_list_animals

  List livestock records (name, type, tag number, gender, breed, status, weight, group, purchase/sale data). Farmbrite returns only active-status animals unless you filter by status (Sold, Deceased, Culled, Butchered, Archived...). GET /animals.

• farmbrite_get_animal

  One animal by id, with its current location and custom fields. GET /animals/{animal_id}.

• farmbrite_list_livestock_groups

  List livestock groups (id, name, type). GET /livestock_groups.

• farmbrite_get_livestock_group

  One livestock group by id with its member count, filters and member animals. GET /livestock_groups/{group_id}.

• farmbrite_list_animal_measurements

  Weight, height, temperature, condition score and fecal-count records of one animal, newest data included. GET /animals/{animal_id}/measurements.

• farmbrite_list_feedings

  Feeding records (amount, cost, date, feed type, inventory used) of one animal or livestock group. GET /{animals|livestock_groups}/{id}/feedings.

• farmbrite_list_grazing_summary

  Grazing status per field/pasture: animals present, days rested, rest days required, last grazed. GET /grazings.

• farmbrite_list_plants

  List plant types/varieties (days to maturity, spacing, market price, harvest unit). GET /plants.

• farmbrite_list_crops

  List crop plantings (plant, field/plot, bed, quantity, planting and expected harvest dates, growth stage). GET /crops.

• farmbrite_get_crop

  One crop planting by id. GET /crops/{crop_id}.

• farmbrite_list_plots

  List fields/grow locations (title, type, size, status, grazing rest days). GET /plots.

• farmbrite_get_plot

  One field/grow location by id. GET /plots/{plot_id}.

• farmbrite_list_harvests

  Harvest records (quantity, unit, grade, price, date, inventory added) of one animal or crop planting. GET /{animals|crops}/{id}/harvests.

• farmbrite_list_treatments

  Treatment records (type, product, amount, cost, date, withdrawal date, technician) of one animal, field or crop planting. GET /{animals|plots|crops}/{id}/treatments.

• farmbrite_list_notes

  Notes (description, category, date, keywords) attached to an animal, field, plant type, crop planting or inventory type. GET /{animals|plots|plants|crops|inventory_types}/{id}/notes.

• farmbrite_list_contacts

  List contacts (customers, suppliers, vendors): name, company, email, phone, type, label. GET /contacts.

• farmbrite_get_contact

  One contact by id, with address. GET /contacts/{contact_id}.

• farmbrite_list_tasks

  List tasks (title, description, status, priority, assignee, due/end time, checklist, linked animal/field/crop). GET /tasks.

• farmbrite_get_task

  One task by id with its checklist. GET /tasks/{task_id}.

• farmbrite_list_activities

  List calendar/schedule activities (title, start and end time, all-day flag, linked animal or field). GET /activities.

• farmbrite_list_inventory_types

  List inventory item types (feed, supplies, harvested products) with the quantity remaining, unit, value and low-stock alert level. GET /inventory_types.

• farmbrite_get_inventory_type

  One inventory item type by id with quantity remaining and projected empty date. GET /inventory_types/{inventory_type_id}.

• farmbrite_get_inventory_locations

  Where one inventory item is stored: warehouse and bin ids and names, capacity and quantity remaining in each. Use the ids with farmbrite_add_inventory / farmbrite_remove_inventory. GET /inventory_types/{inventory_type_id}/inventory.

• farmbrite_list_warehouses

  List storage locations (warehouses) for inventory: name, description, internal id. Use the ids when adding or removing inventory. GET /warehouses.

• farmbrite_list_orders

  List sales orders (status, payment status, total, dates, contact, delivery type, invoice number). GET /orders.

• farmbrite_get_order

  One order by id with its line items, customer contact, delivery address and totals. GET /orders/{order_id}.

• farmbrite_list_transactions

  List income and expense transactions (type, amount, date, vendor, category, linked animal/field/plant, description). GET /transactions.

• farmbrite_get_transaction

  One transaction by id. GET /transactions/{transaction_id}.

• farmbrite_create_contact

  WRITE: create a contact (customer, supplier, vendor). Nothing is emailed or sent to the contact. Creating twice makes two contacts. POST /contacts.

• farmbrite_update_contact

  WRITE: change fields of an existing contact (only the fields you pass are sent). Overwrites the previous values. PUT /contacts/{contact_id}.

• farmbrite_create_task

  WRITE: create a task, optionally linked to an animal, equipment, plant, location or planting. May notify the assigned Farmbrite user according to your account settings. Creating twice makes two tasks. POST /tasks.

• farmbrite_update_task

  WRITE: change a task (only the fields you pass are sent); set complete=true to mark it done. Overwrites previous values. PUT /tasks/{task_id}.

• farmbrite_create_transaction

  WRITE: record an income or expense transaction in the farm's books. Creating twice records it twice. POST /transactions.

• farmbrite_create_note

  WRITE: add a note to an animal, livestock group, field, plant type, crop planting or inventory item. Notes cannot be removed with this server. POST /{parent}/{id}/notes.

• farmbrite_add_inventory

  WRITE: add stock to an inventory item in a storage location (warehouse, optionally a bin). Raises the quantity remaining; not idempotent: repeating adds again. Find ids with farmbrite_list_inventory_types, farmbrite_get_inventory_locations and farmbrite_list_warehouses. PUT /inve

• farmbrite_remove_inventory

  WRITE: take stock out of an inventory item in a storage location (use, loss, sale). Lowers the quantity remaining; not idempotent: repeating removes again. It cannot be undone with this server except by adding stock back. PUT /inventory_types/{id}/inventory/remove.

• farmbrite_create_order

  WRITE: create a sales order with line items (status defaults to Draft and payment_status to Due unless you set them; memo is internal, note is customer-facing). Farmbrite may email the customer or generate an invoice depending on the account's settings and the status chosen; the

• farmbrite_update_order

  WRITE: change an order's status and/or payment status (for example mark it Paid or Delivered). Farmbrite may send customer notifications on some status changes, depending on the account settings. PUT /orders/{order_id}.

• farmbrite_create_animal

  WRITE: add an animal (or a group when is_group=true with group_qty) to the herd. type (e.g. Cattle, Sheep) and status are required. Creating twice makes two animals. POST /animals.

• farmbrite_update_animal

  WRITE: change an animal's fields (only the fields you pass are sent), including its status (Sold, Deceased, Culled...). Statuses Butchered, Culled and Deceased need death_date. Overwrites previous values. PUT /animals/{animal_id}.

• farmbrite_add_animal_measurement

  WRITE: record a measurement for one animal (weight, height, temperature, condition score, fecal egg count). Adds a record each time. POST /animals/{animal_id}/measurements.

• farmbrite_create_feeding

  WRITE: record a feeding for an animal or livestock group. Either name the feed type, or give inventory_id + inventory_location_id to draw it from inventory (which lowers that inventory's quantity). Adds a record each time. POST /{animals|livestock_groups}/{id}/feedings.

• farmbrite_create_harvest

  WRITE: record a harvest (quantity and unit) for an animal or crop planting. Adds a record each time. POST /{animals|crops}/{id}/harvests.

• farmbrite_create_treatment

  WRITE: record a treatment (vaccine, dewormer, spray, fertilizer...) for an animal, livestock group, field or crop planting. Adds a record each time. POST /{animals|livestock_groups|plots|crops}/{id}/treatments.

Basischecksi

Wir prüfen Informationen, die jeder sehen kann; den Code haben wir nicht gelesen. Checks, die nicht zutreffen, werden nicht mitgezählt. · Geprüft am 6. Nov. 2026

• ✓ Bestanden

  Entwickler passt zum Repo

  Der Registry-Name wurde über die Domain usefulapi.io bestätigt (die Registry prüft, wem die Domain gehört)

• … Noch nicht geprüft

  Wird noch gepflegt

  Dieses Repo haben wir noch nicht von GitHub gelesen

• … Noch nicht geprüft

  Hat eine Lizenz

  Dieses Repo haben wir noch nicht von GitHub gelesen

• ✓ Bestanden

  Endpunkt antwortet

  Antwort in 114 ms (HTTP 200)

• – Nicht zutreffend

  Anmeldung mit OAuth

  Keine Anmeldung nötig

• ✓ Bestanden

  Keine versteckten Anweisungen in Tool-Beschreibungen

  Wir haben 44 Tool-Beschreibungen gelesen und keine versteckten Anweisungen an die KI gefunden

Im Vergleich mit anderen in Onlineshops & Zahlungeni

• Mehr Sterne als 0 % der anderen 1743 Server in dieser Kategorie
• Neuer in der Registry veröffentlicht als 94 % der anderen 1743 Server in dieser Kategorie
• Basischecks gleich gut wie oder besser als bei 100 % der anderen 1743 Server in dieser Kategorie

Verglichen mit allen aktiven Servern dieser Kategorie in der Registry. Sterne zählen nur, wenn dem Herausgeber das Repo gehört.

Alternativen

Server derselben Kategorie von anderen Entwicklern, sortiert nach Sternen.

So liest du eine Karte:★ GitHub-SterneiDrei Säulen: Bewertungen · Checks · NutzungiAktualisiert = neueste Version in der Registry veröffentlichti

README vom Entwickler

{