LiveZendesk
Support
Works with Claude
Claude MCP
Connect Claude to the software your business already runs on. FloConnector is a hosted MCP server: add one endpoint as a custom connector, sign in once, and Claude can work in your tools. No server to run.
58 connectors · 6,533 tools · one endpoint
The Claude walkthrough, 2:31.
Setup
Connecting Claude
Claude talks to FloConnector over MCP. You add a profile endpoint as a custom connector, sign in once with your FloConnector account, and the tools that profile exposes show up in Claude ready to call. There is nothing to host, no config file to edit, and no npm package to install, because the server runs on our side and Claude reaches it over HTTP.
The steps mirror the walkthrough in the docs, which is the source of truth if Anthropic moves a menu.
Full guide in the docs- In Claude, open Settings, then Connectors.
- Choose Add custom connector.
- Give it a name you will recognise, such as your workspace name, and paste your profile endpoint as the URL.
- Save, then choose Connect. Claude opens the FloConnector sign-in page.
- Sign in with the email on your FloConnector account and approve access. Claude loads the profile's tools.
What you can connect
58 connectors Claude can use
Every one of these is a connection you authorise once in your dashboard, not a server you install and keep running. Claude sees the tools you choose to expose and nothing else.
Live
LiveStripe
Payments
LiveTrello
Project management
LiveDataForSEO
Analytics
LiveOutlook
LiveMailchimp
Marketing
LiveZoho Books
Accounting
LiveHubSpot
CRM
LiveSalesforce
CRM
BetaDeputy
Workforce
LiveDropbox
Storage
BetaServiceM8
Field service
When it does not work
Known snags, and what to do
Most MCP write-ups stop at the happy path. These are the things that genuinely catch people out with Claude.
Claude Desktop sits on Connect after you signed in
The sign-in has usually succeeded. Check the profile in your dashboard: if the grant is there the connection is live, and restarting the desktop app clears the stale button. It is a client-side issue, not something the server can fix.
The connector saves but no tools appear
Disconnect and reconnect it once. If it is still empty, check in the dashboard that the connection behind the profile is still connected and that you are an assigned member of that profile.
The first load is slow on a very large profile
A profile exposing hundreds of tools takes longer to load, and a model given too many tools chooses worse. Split the work across two profiles rather than exposing everything at once. This is the failure mode most MCP write-ups name and never solve.
Questions, answered
Do I need to run my own MCP server to use Claude with my tools?
No. FloConnector is a hosted MCP server. You add a URL to Claude as a custom connector; there is nothing to deploy, and no local process that has to stay running for the connection to work.
Does this work in Claude Desktop and the web app?
Both. The connector follows your Claude account rather than the device, so adding it once covers you in either. Custom connectors are a paid-plan feature in Claude.
Does Claude see my passwords or API keys?
No. FloConnector holds each vendor credential, encrypted before it is stored, and calls the vendor on the model's behalf. Claude only ever sees the tools and their results.
Can I control what Claude is allowed to change?
Yes. A profile carries only the tools you switch on, so you can expose reads and leave every write tool off. You can also run separate profiles for separate jobs and point Claude at just one.
Not using Claude only
The same endpoint works in other clients
A FloConnector profile is a standard MCP server, not a Claude integration. Nothing about it changes between clients, so you authorise each one once and they all reach the same tools.
