Before a client call
A client call prepared from real records.
Before calling Delcourt, Léa asks Claude for the deal, its contacts and the latest activities in Squario, and drafts her talking points from what is actually there.
MCP server
Checking availabilityComing soonBring your workspace into the AI you already use.
Connect Claude and other MCP clients over OAuth 2.1. They get Squaria’s tools and your permissions, so they can only read or change what your role allows.
One connection, the same rules as Squaria
Some of your team already works in Claude or another AI client. With the MCP server, that client can search records, read a pipeline, run a report or update a task in Squario, without exports or copy and paste. Every call runs as the member who approved the connection.
Connected over OAuth 2.1, revoked when you want
Copy the server URL from Account → Connected apps and add it to a client that supports remote MCP servers. The client opens Squario’s consent screen, where you sign in, choose the workspace and approve.
Paste one URL into your client
The MCP server URL is in Account → Connected apps, ready to add to your client.
Approve on Squario’s own screen
You sign in to Squario, pick the workspace and approve, with no API key to copy.
Rechecked on every call
Membership, record visibility and field permissions are checked again each time a tool runs.
Revoke at any time
Each connection is listed in Account → Connected apps, where you can revoke it when you want.
Squaria’s tools, inside your own client
Your client discovers the tools on its own: search and read records, check a change before writing it, save views and run reports. Writes follow your client’s approval settings, and Drive tools see metadata only.
Search and read records
Find companies, deals, projects or custom records from a prompt in your client.
Check, then write
A client can validate a change against your schema before it creates or updates a record.
Views and reports
Ask your client for a pipeline report and it runs it on live workspace data.
Metered in AI credits
Each tool call uses 1 AI credit from the workspace pool, and a failed call is refunded.
When the work happens in Claude
Your team keeps the AI client it likes, and Squario stays the place where the records live.
After the workshopWorkshop notes turned into project tasks.
Max pastes his notes into Claude and asks for tasks on P-118. Claude checks each change with Squario, and creates the tasks once he approves them in the client.
Monday, 8:30The weekly numbers, asked in plain words.
The founder asks Claude how many deals were won last week and what is still at Proposal. The figures come from a report run on the workspace, within her own permissions.
Your AI client, with your workspace rules.
In a 30-minute demo, we connect Claude to a workspace and show what it can read and change under each role. MCP is included on paid plans.
Questions about the MCP server
What is MCP?
The Model Context Protocol is an open standard that lets AI clients like Claude use tools. Squario’s MCP server gives them Squaria’s tools, limited by your permissions. Actions that only make sense in the app, like page navigation and record page layouts, stay with Squaria.
Which clients can connect?
Claude, and other clients that support remote MCP servers with OAuth. You add the server URL shown in Account → Connected apps.
Can a connected client do more than I can?
No. The grant acts as you: your membership, record visibility and field permissions are rechecked on every call. Drive tools see file metadata, never file contents.
Which plans include MCP?
MCP is included on paid plans, not on Free. Each tool call uses 1 AI credit from the workspace’s monthly allowance, which credit packs can top up.