[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup) # Bloom MCP server: Let your AI agent do the Bloom admin. > Bloom has no MCP server, no ChatGPT or Claude app and no public API: we found no developer docs, only a Zapier app with triggers such as new lead and new payment (checked 8 Nov 2026). Cotlet runs 9 Bloom tools hosted, over MCP for agents and REST for scripts, in your own Bloom login. Your AI agent logs enquiries as leads, follows up quiet ones, books projects with a contract and sends invoices. Sign in to Bloom once in your own Cloud Browser. No API, no zaps to build. - Free 7-day trial, no card - Unofficial, not affiliated with Bloom - Page: https://cotlet.dev/integrations/bloom-api-mcp-server ## What can your AI agent do in Bloom? - Log enquiries as leads - Follow up quiet leads - Send contracts for signing - Send invoices - Record payments - Plan the week's shoots ## Does Bloom have an MCP server or an API? - Bloom's help center has no API articles. - Bloom's Zapier app sends events out; it creates almost nothing in Bloom. - Bloom has no connector in the ChatGPT apps directory or in Claude. | What you need | Bloom API | Zapier app | Cotlet | |---|---|---|---| | New leads and payments | No API | Triggers | Yes | | Create leads and projects | No API | No | Yes | | Send invoices and contracts | No API | No | Yes, after your OK | | Ask in ChatGPT or Claude | No | No | Yes | | Setup | None possible | Zaps to build | Sign in once | Checked 8 Nov 2026. Sources: [Bloom on Zapier](https://zapier.com/apps/bloom/integrations), [Bloom help center](https://help.bloom.io/en/), [Bloom help: Creating and sending an invoice](https://help.bloom.io/en/articles/5147285-creating-and-sending-an-invoice) ## How does the Bloom MCP server work? 1. **Sign in to Bloom.** Once, in a browser we host for you. 2. **Connect your AI agent.** One address in its settings. 3. **Hand it the busywork.** It drafts the work, you OK what customers get. We never keep your Bloom password, and no invoice, contract or payment reaches a client until you approve it. ## How to connect Bloom to your AI agent 1. **Sign in to Bloom in a Cloud Browser.** Create a Cotlet account, open Bloom in its Cloud Browser, sign in with your Bloom login on app.bloom.io and press Enable for agents. 2. **Add the Cotlet address.** Enter https://cotlet.dev/mcp/v1 as the MCP server or connector URL in your agent. 3. **Let the agent in.** Chat apps open a Cotlet sign-in page. Editors, n8n and scripts send an API key made in the console. Bloom shares the address `https://cotlet.dev/mcp/v1` with every other app you enable, so one connector covers them all. Turned Bloom on after connecting? Refresh the connector and the 9 tools appear. Claude: ``` Settings > Connectors > Add custom connector URL: https://cotlet.dev/mcp/v1/connect Claude Code: claude mcp add --transport http cotlet \ https://cotlet.dev/mcp/v1 \ --header "Authorization: Bearer $COTLET_API_KEY" ``` ChatGPT: ``` Settings > Apps & Connectors > Create MCP server URL: https://cotlet.dev/mcp/v1/connect Authentication: OAuth ``` Cursor: ``` // ~/.cursor/mcp.json { "mcpServers": { "cotlet": { "url": "https://cotlet.dev/mcp/v1", "headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" } } } } ``` Codex: ``` # ~/.codex/config.toml [mcp_servers.cotlet] url = "https://cotlet.dev/mcp/v1" bearer_token_env_var = "COTLET_API_KEY" ``` n8n: ``` MCP Client Tool (inside an AI Agent) Transport: HTTP Streamable URL: https://cotlet.dev/mcp/v1 Auth: Bearer, Tool: bloom_read ``` Make, Zapier: ``` Make: MCP Client > Call a tool Zapier: MCP Client by Zapier > Run Tool Server URL: https://cotlet.dev/mcp/v1 Token: Tool: bloom_write ``` ## All 9 Bloom MCP tools ### Leads and contacts New leads reach no one, so they run at once. Search matches name and email. - **List leads** (`list_leads`, read): Leads by stage, with event date and source. - **Create lead** (`create_lead`, write): Adds a lead from an enquiry. - **List contacts** (`list_contacts`, read): Contacts, searchable by name or email. ### Projects Projects and workflow tasks as you set them up in Bloom. A task that emails the client waits for your OK. - **List projects** (`list_projects`, read): Projects with status, date, amount paid and next workflow task. - **Create project** (`create_project`, write): Creates a project for a contact. - **Complete workflow task** (`complete_task`, write): Marks a workflow task done on a project. ### Invoices and contracts Anything that reaches the client, or changes what they owe, waits for your OK. - **Send invoice** (`send_invoice`, write, asks first): Creates and sends an invoice from a project. - **Send contract** (`send_contract`, write, asks first): Sends a contract from your templates for signing. - **Record payment** (`record_payment`, write, asks first): Records a payment made outside Bloom against an invoice. Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/bloom-api-mcp-server#tools ## Who can see my Bloom session, and how do I revoke it? - **What we store.** Your signed-in Bloom profile, AES-256-GCM encrypted, in Finland. No password. - **What your agent gets.** The 9 Bloom tools, never the session cookie. - **What the session sees.** What your login sees: leads, contacts, projects, invoices, contracts. - **What no tool touches.** Galleries, your website, refunds, payment settings, deletes. - **If Bloom signs you out.** You sign in again yourself, in the same Cloud Browser. - **How to cut access.** Disable for agents, reset the browser, or change your Bloom password. Cotlet never types your password: you sign in yourself, and the agent only uses the session. Our site scores A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory ([live results](https://cotlet.dev/security.md)). ## What happens when Bloom changes? - **12 h** between tests of the Bloom reads - **24 h** between tests of sends a customer would notice - **$0** for a call to a Bloom tool paused for repair When Bloom moves a button on a project or renames a tab, we fix the tool and your agent calls it the same way. [status.cotlet.dev](https://status.cotlet.dev) checks the site, console and API every 3 minutes. ## Approvals, undo and mistakes 1. **Finds the contact.** Or adds them from the lead. 2. **Creates the project.** With the date and your workflow. 3. **Fills the contract.** From your template. 4. **Waits, then sends.** The contract shows up in your Cotlet console first. | Action | Undo | |---|---| | Add a lead or project | Yes, edit or archive it in Bloom | | Send an invoice or contract | No, it is in the client's inbox; void it in Bloom | | Record a payment | Yes, delete the payment in Bloom | 3 of 9 tools ask first: send_invoice, send_contract, record_payment. New leads, projects and workflow ticks reach no customer, so they run at once. You can turn the wait off per tool once you trust a routine. MCP call: ``` { "name": "create_lead", "arguments": { "name": "Priya Natarajan", "email": "priya@example.com", "service": "Family session", "event_date": "2026-11-29" } } ``` REST: ``` curl -X POST https://cotlet.dev/api/v1/bloom/leads \ -H "Authorization: Bearer $COTLET_API_KEY" \ -H "Content-Type: application/json" \ -d '{"name":"Priya Natarajan","email":"priya@example.com","service":"Family session","event_date":"2026-11-29"}' ``` Response: ``` { "lead_id": "LD-4433", "contact": "Priya Natarajan", "service": "Family session", "stage": "Inquiry" } ``` A cron job or n8n flow can call the same tools over REST at `/api/v1/bloom` with the same key and price, in JSON. Failed calls are free. Each tool row above shows its REST path. ## How much does the Bloom MCP server cost? **About $14 a month** for a solo wedding and portrait photographer, 2,360 credits. Your Bloom plan stays as it is. | Job | Calls | Credits | |---|---|---| | Enquiry logged as a lead | 1 × 30 | 300 | | Quiet leads, weekly | 1 × 4 | 40 | | Project booked with a contract | 3 × 8 | 240 | | Invoice sent | 2 × 12 | 240 | | Week planned | 1 × 4 | 40 | | Cloud Browser, 30 days | | 1,500 | | Total | | 2,360 | - Free 7-day trial, no card - 10 credits per successful call, MCP or REST - 50 credits a day for the Cloud Browser - Works on any Bloom plan Bloom publishes no project counts, so the month is our example. Dollars at the $29 pack rate. ## Bloom MCP server on GitHub, Zapier or hosted: which to use | Option | What it does | Where it stops | |---|---|---| | Zapier app | New leads, forms, projects and payments to other apps. | Triggers only; nothing you can ask in plain words. | | Bloom automations | Workflow emails and reminders inside Bloom. | Fixed steps you set up; no questions or new records. | | By hand | Every screen of Bloom, one client at a time. | Your editing time. | If you only need new leads copied to a sheet, the Zapier app does that. To log leads, book projects and send invoices from ChatGPT or Claude this week, Cotlet works in the Bloom account you already have. ## Who runs Cotlet Take Group sp. z o.o. runs Cotlet. It is a software company registered in Poland, EU (VAT PL6342984273), in business since 2019, led by its founders Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Questions about the Bloom tools go to contact@cotlet.dev. ## Bloom MCP server: questions ### How do I get access? Sign up free at https://cotlet.dev, open Bloom under Integrations in the console and sign in to Bloom in its Cloud Browser. The trial starts with your first app and asks for no card. ### How do I connect Bloom to ChatGPT or Claude? Sign up at cotlet.dev, log in to Bloom once in its Cloud Browser and add Cotlet to ChatGPT or Claude, following the steps in your console. No API key is needed. ChatGPT and Claude then work in your Bloom account through Cotlet, in their phone apps too. ### What can ChatGPT do in Bloom? With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in Bloom: log enquiries as leads; follow up quiet leads; book a lead. You ask in plain words, and anything that reaches other people waits for your OK first. ### Is there an official ChatGPT or Claude app for Bloom? No. Bloom has no ChatGPT or Claude connector of its own and Bloom has no official MCP server (checked 8 Nov 2026). Cotlet is an independent one that works in ChatGPT, Claude, Cursor and any MCP client, on your signed-in account. ### Can ChatGPT add leads in Bloom? Yes, with Cotlet. ChatGPT adds enquiries from email or DMs as Bloom leads with the service and date, and lists leads that have gone quiet. ### Can ChatGPT send invoices in Bloom? Yes, with Cotlet. ChatGPT creates the invoice from your packages on the project and sends it with the payment link after your OK. ### Can ChatGPT send contracts in Bloom? Yes, with Cotlet. ChatGPT fills one of your contract templates for the project and sends it for signing after your OK. ### Does it deliver galleries? Not yet. Cotlet works with leads, projects, workflow tasks, invoices and contracts. Uploading and delivering galleries stays in Bloom. ### Does it work for designers and coaches too? Yes. Bloom is the same for photographers, videographers, designers and coaches, and so are the tools: leads, projects, invoices and contracts. ### Is the MCP server different from the REST API? Only in how it is called. Both carry the same 9 tools, inputs, answers, API key and price. Agents use MCP; scripts and HTTP steps use REST. ### Is Cotlet affiliated with Bloom? No. Cotlet is independent and not affiliated with Bloom. --- Give your AI agents your signed-in browser. **Product:** [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md) **Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet) **Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) **Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md) **Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors) **Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet) Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. [About us](https://cotlet.dev/about.md) Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.