Bloom MCP server Let your AI agent do the Bloom admin.

ToolWhat it doesAccess

• list_leads Leads by stage, with event date and source. read

  Returns leads with contact, service, event date, stage and last contact, newest first.

  MCP callbloom_read → list_leads

  REST endpointGET https://cotlet.dev/api/v1/bloom/leads

  Parameters

  Parameters: list_leads

  Name	Type	Description
  stage string	string	Lead stage.
  no_reply_days integer	integer	Only leads with no contact in this many days.
  page integer	integer	Page number. Default: 1.

  Example response

  {
    "leads": [
      {
        "lead_id": "LD-4410",
        "contact": "Emily & Jordan Hayes",
        "service": "Wedding, full day",
        "event_date": "2027-06-12",
        "stage": "Inquiry",
        "source": "Website form"
      }
    ],
    "page": 1
  }

• create_lead Adds a lead from an enquiry. write

  Creates the contact and lead with service and event date. Reaches no one, so it runs at once.

  MCP callbloom_write → create_lead

  REST endpointPOST https://cotlet.dev/api/v1/bloom/leads

  Parameters

  Parameters: create_lead

  Name	Type	Description
  name string required	string	Contact name.
  email string	string	Email.
  service string	string	Service asked for.
  event_date string	string	ISO date.
  note string	string	What they wrote.

  Example input

  {
    "name": "Priya Natarajan",
    "email": "priya@example.com",
    "service": "Family session",
    "event_date": "2026-11-29"
  }

  Example response

  {
    "lead_id": "LD-4433",
    "contact": "Priya Natarajan",
    "service": "Family session",
    "stage": "Inquiry"
  }

• list_contacts Contacts, searchable by name or email. read

  Returns contacts with ID, email, phone and their projects.

  MCP callbloom_read → list_contacts

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

  Parameters

  Parameters: list_contacts

  Name	Type	Description
  query string	string	Name or email.
  page integer	integer	Page number. Default: 1.

  Example response

  {
    "contacts": [
      {
        "contact_id": "CT-9120",
        "name": "Marcus Bellamy",
        "email": "marcus@example.com",
        "projects": 1
      }
    ],
    "page": 1
  }

ToolWhat it doesAccess

• list_projects Projects with status, date, amount paid and next workflow task. read

  Returns projects with client, shoot date, status, invoice balance and the next open workflow task.

  MCP callbloom_read → list_projects

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

  Parameters

  Parameters: list_projects

  Name	Type	Description
  status string	string	Project status.
  date_from string	string	ISO date.
  date_to string	string	ISO date.
  page integer	integer	Page number. Default: 1.

  Example response

  {
    "projects": [
      {
        "project_id": "PJ-2207",
        "client": "Marcus Bellamy",
        "name": "Headshots",
        "date": "2026-11-15",
        "status": "Booked",
        "balance": "250.00",
        "next_task": "Send prep guide"
      }
    ],
    "page": 1
  }

• create_project Creates a project for a contact. write

  Creates the project with service and date, the way New Project on a contact does. Reaches no one, so it runs at once.

  MCP callbloom_write → create_project

  REST endpointPOST https://cotlet.dev/api/v1/bloom/contacts/{contact_id}/projects

  Parameters

  Parameters: create_project

  Name	Type	Description
  contact_id string required	string	Contact ID from list_contacts.
  name string required	string	Project name.
  date string	string	ISO date of the shoot or session.
  workflow string	string	Workflow name to apply.

  Example input

  {
    "contact_id": "contact_8c41d2",
    "name": "Jane Doe"
  }

  Example response

  {
    "project_id": "PJ-2231",
    "client": "Priya Natarajan",
    "name": "Family session",
    "date": "2026-11-29",
    "status": "Booked"
  }

• complete_task Marks a workflow task done on a project. write

  Ticks the task in the project workflow. If the task is an automation that emails the client, it waits for your OK.

  MCP callbloom_write → complete_task

  REST endpointPOST https://cotlet.dev/api/v1/bloom/projects/{project_id}/task/complete

  Parameters

  Parameters: complete_task

  Name	Type	Description
  project_id string required	string	Project ID from list_projects.
  task string required	string	Task name.

  Example input

  {
    "project_id": "project_8c41d2",
    "task": "task"
  }

  Example response

  {
    "project_id": "PJ-2207",
    "task": "Send prep guide",
    "status": "Done"
  }

ToolWhat it doesAccess

• send_invoice Creates and sends an invoice from a project. writeasks first

  Creates the invoice with your packages or line items and emails it with the payment link. By default you confirm each call; you can switch that off for this tool.

  MCP callbloom_write → send_invoice

  REST endpointPOST https://cotlet.dev/api/v1/bloom/projects/{project_id}/invoices

  Parameters

  Parameters: send_invoice

  Name	Type	Description
  project_id string required	string	Project ID from list_projects.
  items array required	array	Package or line items with price.
  due string	string	ISO due date.

  Example input

  {
    "project_id": "project_8c41d2",
    "items": "items"
  }

  Example response

  {
    "invoice_id": "IV-7781",
    "client": "Priya Natarajan",
    "total": "450.00",
    "status": "Sent"
  }

• send_contract Sends a contract from your templates for signing. writeasks first

  Fills the template with the project details and sends it for the client's signature. By default you confirm each call; you can switch that off for this tool.

  MCP callbloom_write → send_contract

  REST endpointPOST https://cotlet.dev/api/v1/bloom/projects/{project_id}/contracts

  Parameters

  Parameters: send_contract

  Name	Type	Description
  project_id string required	string	Project ID from list_projects.
  template string required	string	Contract template name.

  Example input

  {
    "project_id": "project_8c41d2",
    "template": "template"
  }

  Example response

  {
    "contract_id": "CN-3302",
    "client": "Emily & Jordan Hayes",
    "template": "Wedding agreement",
    "status": "Sent"
  }

• record_payment Records a payment made outside Bloom against an invoice. writeasks first

  Marks the amount paid, for example a bank transfer, so the balance is right. By default you confirm each call; you can switch that off for this tool.

  MCP callbloom_write → record_payment

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

  Parameters

  Parameters: record_payment

  Name	Type	Description
  invoice_id string required	string	Invoice ID.
  amount number required	number	Amount paid.
  method string	string	Bank transfer, cash, check.

  Example input

  {
    "invoice_id": "invoice_8c41d2",
    "amount": 1
  }

  Example response

  {
    "invoice_id": "IV-7702",
    "paid": "250.00",
    "balance": "0.00"
  }