A CRM MCP server with a record you can check
Short answer: Flori's remote MCP server is https://useflori.com/mcp. It connects compatible assistants to authorized CRM, project and task records through browser sign-in. Choose read-only or update access and a workspace or selected project. The connection does not grant access to all your other apps or make every write subject to approval.
What the connection does
| Need | Capability and boundary |
|---|---|
| Read context | Search and retrieve authorized records; check scope and pagination rather than assuming every record is in the first result |
| Save work | Create or update supported records and save concise outcomes when access and workflow settings allow |
| Propose work | Suggested tasks and projects have proposal paths; submitted assistant work can be reviewed |
| Make a direct change | Some explicitly requested creations and authorized field updates save immediately |
| Coordinate a task | Activity and task claims help connected assistants avoid overlapping work; they are not a universal guarantee against duplicates |
| Import a CRM CSV | Use the signed-in Flori import screen; this is not an MCP bulk-import tool |
| Email or publish externally | The MCP connector has no email-send, payment or public-publish tool |
The developer reference is the current tool and schema inventory. A whole-workspace grant is broader than a project grant. A project connection does not make unrelated CRM records visible; use the supported scoped records and inspect denied operations rather than broadening access merely to make a prompt succeed.
Complete a first connection
- Create a Flori account and a test project containing a brief and one task. The Juniper example supplies fictional inputs.
- Open Settings, then Connections and follow the guide for your assistant. For Claude, add a custom connector at the remote address; for other clients use their documented remote-MCP and OAuth setup.
- Finish browser sign-in, select the intended workspace or test project and begin with read-only access.
- Enable the connection in the work conversation. Ask the assistant to retrieve the named project and quote the specific next action from its saved brief.
- Compare the answer with Flori. A successful sign-in alone does not establish that the right record was read.
Use the maintained Claude, ChatGPT or assistant connection guides. Availability depends on the assistant's plan and organizational policy. Flori provides a custom connection; do not infer a public marketplace listing from that availability. You do not need an API key for Flori's OAuth flow.
Demonstrate scope and review with synthetic records
Create a second test project containing no real client information. Through the first project's connection, ask for the second project by its known ID. Its contents should not be returned. Next, request a due-date change with the read-only connection: it should be denied and the task should remain unchanged.
To try a write, reconnect with update access to the first project and explicitly request a proposed task. Inspect it in Flori, accept or reject it, then read back the result. For an immediate authorized update, check the changed field and saved attribution instead of looking for a proposal that was never requested. The full exercise gives prompts and expected observations; it is not a claim of a completed live assistant trial.
If something fails
| Result | Recovery |
|---|---|
| No connection tools | Enable the connection and check account or organization policy |
| 401 or an expired session | Sign in again through the normal flow |
| 403 or a missing/out-of-scope record | Check the chosen grant and permission; do not treat the response as evidence the record was deleted |
| 409 conflict | Re-read current state and the conflicting task claim before retrying |
| A save is uncertain | Inspect its result and read the record; do not blindly create the same item again |
The server uses version and request information for supported mutations. Clients must follow the returned instructions. An assistant saying "done" is not a readback. Keep the user's actual approval and workflow preference distinct from a progress heartbeat.
Cost and alternatives
Flori does not sell AI credits or bill assistants as people. Your external assistant plan and usage limits still apply. The Free plan can be used to try the connection within its project and record limits; see current pricing.
Other CRMs also offer MCP. Compare the documented CRM and project options and test your required scope and operations. The useful distinction is what your chosen connection actually lets you accomplish and verify.
FAQ
What is the Flori MCP server URL? https://useflori.com/mcp. It is a remote connection using browser sign-in. Follow your assistant's connection guide and select the intended project or workspace access.
Can I keep the connection read-only? Yes. Choose read-only access at sign-in for summaries and drafts. Confirm that a test write is refused before using the connection for sensitive work.
Does the review queue block every assistant write? No. Proposed and submitted work have review paths, but authorized direct updates can save immediately. Choose the path and access level that match the task.
Does MCP automatically keep every conversation synchronized? No. The assistant must retrieve the relevant record and make a supported save. Check important outcomes in Flori before relying on them in another session.
Start your workspace