Plancraft API and MCP server Let your AI agent write the offer and chase the invoice.

ToolWhat it doesAccess

• list_contacts Customers and other contacts, with salutation, name, company and addresses. read

  Lists the contacts in plancraft as the contact picker shows them, with the details plancraft keeps per contact: salutation, full name, the company it belongs to and addresses. query searches by name. Pass contact_id to create_project to attach a customer.

  MCP callplancraft_read → list_contacts

  REST endpointGET https://cotlet.dev/api/v1/plancraft/contacts

  Parameters

  Parameters: list_contacts

  Name	Type	Description
  query string	string	Part of the contact or company name.

  Example response

  {
    "contacts": [
      {
        "contact_id": "con_77b2e4",
        "name": "Muster Hausverwaltung GmbH",
        "address": "Beispielstrasse 12, 20095 Hamburg"
      },
      {
        "contact_id": "con_5a90c1",
        "salutation": "Frau",
        "name": "Anna Beispiel",
        "company": null,
        "address": "Probeweg 3, 22765 Hamburg"
      }
    ]
  }

• create_contact Add a customer contact: a person or a company. write

  Creates one contact in plancraft, as the Kontakt erstellen button does. It reaches no one and you edit or correct it in plancraft, so it needs no confirmation. Put salutation, full name, the company it belongs to and the address in the contact, because documents take their recipient from it.

  MCP callplancraft_write → create_contact

  REST endpointPOST https://cotlet.dev/api/v1/plancraft/contacts

  Parameters

  Parameters: create_contact

  Name	Type	Description
  name string required	string	Full name of the person, or the company name.
  salutation string	string	Salutation as plancraft offers it, e.g. Frau or Herr.
  company string	string	Company the person belongs to.
  address string	string	Street, postcode and city on one line.

  Example input

  {
    "name": "Jane Doe"
  }

  Example response

  {
    "contact_id": "con_5a90c1",
    "salutation": "Frau",
    "name": "Anna Beispiel",
    "address": "Probeweg 3, 22765 Hamburg"
  }

• list_projects Projects with number, name, customer and status. Filter by status or search by name. read

  Lists the projects from the Projekte menu, with the project number, name, customer and status. status takes a name from your own list under Projekte > Status verwalten, because plancraft lets every business define its statuses. A project without one shows "Kein Status". Pass project_id to get_project, list_documents or create_offer.

  MCP callplancraft_read → list_projects

  REST endpointGET https://cotlet.dev/api/v1/plancraft/projects

  Parameters

  Parameters: list_projects

  Name	Type	Description
  status string	string	A status name as it appears in your Projekte filter, e.g. "In Arbeit".
  query string	string	Part of the project name, number or customer.

  Example response

  {
    "projects": [
      {
        "project_id": "prj_8f3a21",
        "number": "P-00045",
        "name": "Fassade Muster Hausverwaltung",
        "customer": "Muster Hausverwaltung GmbH",
        "status": "In Arbeit"
      },
      {
        "project_id": "prj_41c9d0",
        "number": "P-00046",
        "name": "Bad Beispiel",
        "customer": "Anna Beispiel",
        "status": "Kein Status"
      }
    ]
  }

• get_project One project's overview: description, assigned employees, customer, site address and hours. read

  Returns what the project overview shows: project number, description, the customer from Kontakte, the site address (Baustellenadresse), the hours booked and the employees assigned to the project. Use it before create_offer to check the recipient the documents will take by default, which is the project's customer.

  MCP callplancraft_read → get_project

  REST endpointGET https://cotlet.dev/api/v1/plancraft/projects/{project_id}

  Parameters

  Parameters: get_project

  Name	Type	Description
  project_id string required	string	Project ID from list_projects.

  Example input

  {
    "project_id": "project_8c41d2"
  }

  Example response

  {
    "project_id": "prj_8f3a21",
    "number": "P-00045",
    "name": "Fassade Muster Hausverwaltung",
    "status": "In Arbeit",
    "description": "Fassade Nordseite streichen, Gerüst steht bis 20.11.",
    "customer": {
      "contact_id": "con_77b2e4",
      "name": "Muster Hausverwaltung GmbH"
    },
    "site_address": "Beispielstrasse 12, 20095 Hamburg",
    "employees": [
      "Lena Muster",
      "Jonas Beispiel"
    ],
    "hours_booked": 16
  }

• create_project Open a new project for a customer, with number, description and site address. write

  Creates a project, as Neues Projekt does. The name is required. If you give no project_number, plancraft assigns the next one from its number sequence. You are assigned to the project; add employees to assign more. It reaches no one until someone is assigned, so it needs no confirmation.

  MCP callplancraft_write → create_project

  REST endpointPOST https://cotlet.dev/api/v1/plancraft/projects

  Parameters

  Parameters: create_project

  Name	Type	Description
  name string required	string	Project name. Plancraft recommends the wording you use as the subject of your offers.
  contact_id string	string	Customer, from list_contacts or create_contact.
  project_number string	string	Your own number. Default: next number from plancraft.
  description string	string	Notes on the job.
  site_address string	string	Site address (Baustellenadresse), one line.
  employees array	array	Employee names to assign besides you.

  Example input

  {
    "name": "Jane Doe"
  }

  Example response

  {
    "project_id": "prj_41c9d0",
    "number": "P-00046",
    "name": "Bad Beispiel",
    "customer": "Anna Beispiel",
    "employees": [
      "Lena Muster"
    ]
  }

ToolWhat it doesAccess

• list_documents The documents in one project: offers, order confirmations, delivery notes, invoices and reminders. read

  Lists the documents in a project folder with type, document number, date and total. type is one of offer, order_confirmation, delivery_note, invoice, reminder. Pass document_id to create_invoice_from_document or send_document. Documents still in draft have no document number yet.

  MCP callplancraft_read → list_documents

  REST endpointGET https://cotlet.dev/api/v1/plancraft/projects/{project_id}/documents

  Parameters

  Parameters: list_documents

  Name	Type	Description
  project_id string required	string	Project ID from list_projects.
  type string	string	offer, order_confirmation, delivery_note, invoice or reminder. Default: all types.

  Example input

  {
    "project_id": "project_8c41d2"
  }

  Example response

  {
    "documents": [
      {
        "document_id": "doc_2e71a8",
        "type": "offer",
        "number": "A-2026-0112",
        "date": "2026-10-02",
        "net_total": 4250,
        "currency": "EUR"
      },
      {
        "document_id": "doc_93b0d4",
        "type": "order_confirmation",
        "number": "AB-2026-0090",
        "date": "2026-10-09",
        "net_total": 4250,
        "currency": "EUR"
      }
    ]
  }

• create_offer Draft a blank offer in a project with positions: text, quantity, unit and unit price. write

  Creates an offer in the project as a blank document (Blanko) with the positions you give, each with a title, optional long text, quantity, unit and unit price. It returns the totals plancraft shows. The offer is only created, never sent; open it in plancraft to adjust or finish it, and use send_document to send it. It reaches no one, so it needs no confirmation.

  MCP callplancraft_write → create_offer

  REST endpointPOST https://cotlet.dev/api/v1/plancraft/projects/{project_id}/offers

  Parameters

  Parameters: create_offer

  Name	Type	Description
  project_id string required	string	Project ID from list_projects.
  subject string	string	Subject line of the offer.
  positions array required	array	Objects with title, quantity, unit, unit_price and optional long_text.

  Example input

  {
    "project_id": "prj_41c9d0",
    "subject": "Malerarbeiten Bad",
    "positions": [
      {
        "title": "Untergrund spachteln",
        "quantity": 85,
        "unit": "m2",
        "unit_price": 6.4
      },
      {
        "title": "Waende streichen",
        "quantity": 85,
        "unit": "m2",
        "unit_price": 7.2
      },
      {
        "title": "Decke streichen",
        "quantity": 24,
        "unit": "m2",
        "unit_price": 8.5
      }
    ]
  }

  Example response

  {
    "document_id": "doc_2e71a8",
    "type": "offer",
    "project": "P-00046",
    "subject": "Malerarbeiten Bad",
    "positions": [
      {
        "title": "Untergrund spachteln",
        "quantity": 85,
        "unit": "m2",
        "unit_price": 6.4,
        "total": 544
      },
      {
        "title": "Waende streichen",
        "quantity": 85,
        "unit": "m2",
        "unit_price": 7.2,
        "total": 612
      },
      {
        "title": "Decke streichen",
        "quantity": 24,
        "unit": "m2",
        "unit_price": 8.5,
        "total": 204
      }
    ],
    "net_total": 1360,
    "vat_total": 258.4,
    "gross_total": 1618.4,
    "currency": "EUR"
  }

• create_invoice_from_document Create an invoice from an offer, order confirmation or delivery note in the same project. write

  Does what the Plus button next to a document does when you pick "Rechnung": it creates an invoice in the project from that document, with its positions. The invoice stays a draft (Entwurf) with no document number until you finish it in plancraft, where you check the payment due date and tax. It reaches no one, so it needs no confirmation.

  MCP callplancraft_write → create_invoice_from_document

  REST endpointPOST https://cotlet.dev/api/v1/plancraft/projects/{project_id}/invoice-from-documents

  Parameters

  Parameters: create_invoice_from_document

  Name	Type	Description
  project_id string required	string	Project ID from list_projects.
  document_id string required	string	The offer, order confirmation or delivery note, from list_documents.

  Example input

  {
    "project_id": "project_8c41d2",
    "document_id": "document_8c41d2"
  }

  Example response

  {
    "document_id": "doc_b81c05",
    "type": "invoice",
    "status": "draft",
    "project": "P-00046",
    "from_document": "doc_2e71a8",
    "net_total": 1360,
    "vat_total": 258.4,
    "gross_total": 1618.4,
    "currency": "EUR"
  }

• send_document Send an offer, invoice or reminder from plancraft to its recipient. writeAsks first

  Sends one document from plancraft to the recipient on it, which by default is the project's customer. It works for offers, order confirmations, invoices and reminders. A draft invoice has no document number or status yet, so finish it in plancraft first. By default you confirm each call; you can switch that off for this tool.

  MCP callplancraft_write → send_document

  REST endpointPOST https://cotlet.dev/api/v1/plancraft/projects/{project_id}/documents/{document_id}

  Parameters

  Parameters: send_document

  Name	Type	Description
  project_id string required	string	Project ID from list_projects.
  document_id string required	string	Document ID from list_documents.

  Example input

  {
    "project_id": "project_8c41d2",
    "document_id": "document_8c41d2"
  }

  Example response

  {
    "document_id": "doc_d6a2f0",
    "status": "sent",
    "recipient": "verwaltung@muster-hausverwaltung.example"
  }

ToolWhat it doesAccess

• list_invoices Outgoing invoices for a period, with status, due date, total and open amount. read

  Lists the invoices of the Ausgangsrechnungen menu. Only invoices whose invoice date falls in the period are listed; the default is the last 90 days, as in plancraft. status is open, overdue, paid, draft, reminded (Angemahnt), cancelled or none. plancraft sets open, overdue and paid by itself once an invoice is finished, and overdue only works when the invoice shows its payment due date. Invoice corrections appear only when you ask for all statuses.

  MCP callplancraft_read → list_invoices

  REST endpointGET https://cotlet.dev/api/v1/plancraft/invoices

  Parameters

  Parameters: list_invoices

  Name	Type	Description
  status string	string	open, overdue, paid, draft, reminded, cancelled or none. Default: all.
  from string	string	Start of the period, YYYY-MM-DD, on the invoice date. Default: 90 days ago.
  to string	string	End of the period, YYYY-MM-DD. Default: today.

  Example response

  {
    "invoices": [
      {
        "invoice_id": "inv_c40e19",
        "number": "R-2026-0187",
        "project": "P-00045",
        "customer": "Muster Hausverwaltung GmbH",
        "status": "overdue",
        "invoice_date": "2026-10-14",
        "due_date": "2026-10-28",
        "gross_total": 5057.5,
        "open_amount": 3057.5,
        "currency": "EUR"
      },
      {
        "invoice_id": "inv_7d12f3",
        "number": "R-2026-0191",
        "project": "P-00046",
        "customer": "Anna Beispiel",
        "status": "open",
        "invoice_date": "2026-11-05",
        "due_date": "2026-11-19",
        "gross_total": 1190,
        "open_amount": 1190,
        "currency": "EUR"
      }
    ]
  }

• record_payment Record a customer payment on an invoice and lower its open amount. writeAsks first

  Adds a payment with its date to an invoice, as the payment entry on the invoice does. plancraft lowers the open amount, and an invoice with 0.00 open becomes paid. You can record several payments on one invoice. Set cash_discount or retention first when the customer took a Skonto or a Sicherheitseinbehalt, so plancraft takes the figures from the invoice. It changes your books. By default you confirm each call; you can switch that off for this tool.

  MCP callplancraft_write → record_payment

  REST endpointPOST https://cotlet.dev/api/v1/plancraft/invoices/{invoice_id}/payments

  Parameters

  Parameters: record_payment

  Name	Type	Description
  invoice_id string required	string	Invoice ID from list_invoices.
  amount number	number	Amount paid. Default: the whole open amount.
  date string	string	Payment date, YYYY-MM-DD. Default: today.
  cash_discount boolean	boolean	The customer deducted a Skonto.
  retention boolean	boolean	The customer withheld a Sicherheitseinbehalt.

  Example input

  {
    "invoice_id": "invoice_8c41d2"
  }

  Example response

  {
    "invoice_id": "inv_c40e19",
    "number": "R-2026-0187",
    "payment": {
      "amount": 2000,
      "date": "2026-11-12"
    },
    "open_amount": 1057.5,
    "status": "overdue",
    "currency": "EUR"
  }

• create_payment_reminder Create the next reminder for an overdue invoice: payment reminder, 1st or 2nd dunning letter. write

  Creates the reminder document in the invoice's project, from the overdue invoice. level is reminder (Zahlungserinnerung), first_dunning (1. Mahnung) or second_dunning (2. Mahnung); plancraft offers the dunning letters only after a reminder exists. The document is created, not sent: it appears in the project and you can edit its text in plancraft. Send it with send_document.

  MCP callplancraft_write → create_payment_reminder

  REST endpointPOST https://cotlet.dev/api/v1/plancraft/invoices/{invoice_id}/payment-reminders

  Parameters

  Parameters: create_payment_reminder

  Name	Type	Description
  invoice_id string required	string	Invoice ID from list_invoices.
  level string required	string	reminder, first_dunning or second_dunning.

  Example input

  {
    "invoice_id": "invoice_8c41d2",
    "level": "level"
  }

  Example response

  {
    "document_id": "doc_d6a2f0",
    "type": "reminder",
    "level": "reminder",
    "invoice": "R-2026-0187",
    "project": "P-00045",
    "open_amount": 3057.5,
    "currency": "EUR"
  }

ToolWhat it doesAccess

• list_time_entries Booked working hours, travel time and absences, by period, employee or project. read

  Lists the entries of the Zeiten menu: employee, date, start, end, break, project and type. type is work (Arbeitszeit), travel (Fahrtzeit) or an absence such as vacation or sick. Work and travel entries belong to a project; workshop, warehouse or office work has project "none".

  MCP callplancraft_read → list_time_entries

  REST endpointGET https://cotlet.dev/api/v1/plancraft/time-entries

  Parameters

  Parameters: list_time_entries

  Name	Type	Description
  from string	string	Start date, YYYY-MM-DD.
  to string	string	End date, YYYY-MM-DD.
  employee string	string	Employee name as plancraft shows it.
  project_id string	string	Only entries booked to this project.

  Example response

  {
    "entries": [
      {
        "entry_id": "tim_19a0c7",
        "employee": "Lena Muster",
        "date": "2026-11-13",
        "start": "07:30",
        "end": "16:00",
        "break_minutes": 30,
        "hours": 8,
        "type": "work",
        "project": "P-00045"
      },
      {
        "entry_id": "tim_19a0c8",
        "employee": "Jonas Beispiel",
        "date": "2026-11-13",
        "start": "07:30",
        "end": "16:00",
        "break_minutes": 30,
        "hours": 8,
        "type": "work",
        "project": "P-00045"
      }
    ]
  }

• create_time_entry Book working time or travel time for one or more employees on a project. writeAsks first

  Creates a time entry as Neue Zeit does, for one or more employees, with date, start, end, break and project. Work and travel entries need a project; for workshop, warehouse or office work pass project_id "none". Entries land in your team's time lists and exports. By default you confirm each call; you can switch that off for this tool.

  MCP callplancraft_write → create_time_entry

  REST endpointPOST https://cotlet.dev/api/v1/plancraft/projects/{project_id}/time-entries

  Parameters

  Parameters: create_time_entry

  Name	Type	Description
  employees array required	array	Employee names as plancraft shows them.
  date string	string	YYYY-MM-DD. Default: today.
  start string required	string	Start time, HH:MM.
  end string required	string	End time, HH:MM.
  break_minutes integer	integer	Break in minutes. Default: 0.
  project_id string required	string	Project ID from list_projects, or "none".
  type string	string	work or travel. Default: work.
  description string	string	Short note on what was done.

  Example input

  {
    "employees": "employees",
    "start": "start",
    "end": "end",
    "project_id": "project_8c41d2"
  }

  Example response

  {
    "entries": [
      {
        "entry_id": "tim_19a0c7",
        "employee": "Lena Muster",
        "date": "2026-11-13",
        "start": "07:30",
        "end": "16:00",
        "break_minutes": 30,
        "hours": 8,
        "type": "work",
        "project": "P-00045"
      },
      {
        "entry_id": "tim_19a0c8",
        "employee": "Jonas Beispiel",
        "date": "2026-11-13",
        "start": "07:30",
        "end": "16:00",
        "break_minutes": 30,
        "hours": 8,
        "type": "work",
        "project": "P-00045"
      }
    ]
  }