Bloomerang MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COTLET_API_KEY | Yes | Your Cotlet.dev API key. Get one at https://cotlet.dev/app. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Bloomerang through Cotlet.dev. Call bloomerang_guide first. Set COTLET_API_KEY (https://cotlet.dev/app).
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| bloomerang_guideA | How to work in Bloomerang (constituents, gifts, interactions and duplicate records): its screens and the sign-in link. Call this first. |
| bloomerang_statusA | Check that your Cotlet.dev account and Bloomerang are ready: account, credits and Bloomerang connection. |
| bloomerang_openA | Open a Bloomerang page in your signed-in Cloud Browser (default https://crm.bloomerang.co) to work with constituents, gifts, interactions and duplicate records. |
| bloomerang_readB | Read the current Bloomerang page: its text and numbered buttons, links and fields. |
| bloomerang_clickB | Click a numbered element on the current Bloomerang page. |
| bloomerang_typeB | Type text into a numbered field on the current Bloomerang page. |
| bloomerang_closeA | Close the Bloomerang browser session when the work is done, so credits stop running. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool maps to a distinct step in the browser workflow: onboarding guidance, account status, opening a page, reading it, clicking, typing, and closing. The boundaries between open/read/click/type/close are clear, and guide vs status is also distinguishable.
All tools share the bloomerang_ prefix and use short lowercase names, giving a predictable pattern. Minor deviation: guide and status are nouns rather than verbs, while the rest are actions.
Seven tools is well-scoped for a browser-automation server focused on Bloomerang. Each tool covers a necessary part of the workflow without redundant actions.
The surface covers the core browser lifecycle: onboarding, status, open, read, click, type, and close. Minor gaps exist around advanced interactions like scrolling, explicit waits, file upload, or dropdown selection, though many can be worked around with click and type.