MCP access is read-only. Connected clients can search and fetch your Statisfy data but cannot create, update, or delete records.
What You Can Do
Once connected, an MCP client can ask natural-language questions that are answered against your live Statisfy workspace. Examples:- “Summarize what’s happened with Acme Corp in the last 30 days”
- “Show me all open opportunities over $50k closing this quarter”
- “Which contacts at Globex are champions?”
- “What are the latest support tickets for accounts in the ‘At Risk’ segment?”
How Connections Are Created
Statisfy implements the standard MCP authorization spec (OAuth 2.1 + PKCE) plus RFC 7591 Dynamic Client Registration. You do not manually mint API keys — every connection is created by completing an OAuth flow from inside your AI assistant. The high-level flow:- Sign in to the Statisfy app at app.statisfy.com so you have an active session ready for the authorization step.
- In your MCP client (e.g., Claude), add the Statisfy MCP server once, then click Connect (if it’s already added, just click Connect).
- The client redirects your browser to Statisfy and asks you to authorize the connection.
- Approve the request if it is the client you want to give access to.
- The client receives a long-lived API key, scoped to your user and your organization.
- From now on, the client can call MCP tools on your behalf.
Adding Statisfy to Claude
First, sign in to the Statisfy app at app.statisfy.com so you have an active session ready for the authorization step.One-time setup: add the Statisfy MCP server
If you haven’t added Statisfy before, add it as a connector once:- Open Claude’s Settings → Connectors (or equivalent in your client).
- Click Add custom connector.
- Enter the Statisfy MCP server URL provided to your admin.
- Save the connector.
Connecting
Once Statisfy is in your connector list (including any time after the one-time setup):- Find Statisfy in the connector list and click Connect.
- Claude opens a browser tab pointing at Statisfy.
- Review the requested permissions, and click Authorize.
- The connector is now active. Try a prompt like “Show me my top 5 at-risk accounts in Statisfy.”
Managing Your Connections
Navigate to Admin → Settings → MCP Connections to view and revoke active connections. The settings page shows:| Column | Description |
|---|---|
| Client | Which application created the connection (e.g., Claude Desktop, Claude.ai) |
| Key owner | The Statisfy user the connection acts on behalf of |
| Created | When the connection was authorized |
| Last used | When the client last called the MCP server |
| Expires | When the connection automatically expires |
Revoking a Connection
- Find the connection in the list.
- Click Revoke.
- The connection is invalidated immediately — the client must re-authorize to regain access.
Permissions and Scope
| Aspect | Behavior |
|---|---|
| Per user | Each connection acts as the user who authorized it. The client sees only what that user can see in Statisfy. |
| Per org | Connections never cross organizations. Each authorization is scoped to a single workspace. |
| Read-only | Tools cannot create, update, or delete records. |
| Admin visibility | Admins can list and revoke every connection in the org. Non-admins see only their own. |
Available Tools
The MCP server exposes a stable set of tools that mirror Statisfy’s data model:| Tool | Purpose |
|---|---|
whoami | Identify the connected user and org |
list_objects | List accounts, people, opportunities, tasks, activities, projects, etc. |
search_objects | Keyword search across object names and key fields |
get_objects | Fetch full details for one or more records by ID |
search_properties | Discover available fields (including custom fields) for an object type |
list_custom_object_types | Enumerate your custom object types |
get_custom_object_instances | Fetch rows from a specific custom object |
get_group_membership | List which groups a person belongs to |
get_task_comments | Read the comment thread on a task |
get_product_usage | Pull product-usage telemetry for an account or user |
semantic_search | Vector search across meeting transcripts and knowledge-base documents |
Your AI assistant decides which tools to call based on your question — you don’t need to invoke them directly.
Troubleshooting
My client can't connect
My client can't connect
- Confirm you copied the full MCP server URL.
- Make sure you have a valid Statisfy login (Clerk session).
- Try authorizing again — short-lived authorization codes expire in 5 minutes.
The connection works but returns 'unauthorized'
The connection works but returns 'unauthorized'
Why don't I see writes (creating tasks, sending emails)?
Why don't I see writes (creating tasks, sending emails)?
The MCP server is intentionally read-only. For write actions, use the Statisfy UI, Stella, or Agent Studio automations.
Where do I find the MCP server URL?
Where do I find the MCP server URL?
Ask your Statisfy admin or contact support. The URL is the same for every user in your organization — authorization happens at the user level after you connect.
Security Notes
- Statisfy never stores raw API keys — only a salted hash. A revoked key cannot be recovered.
- The OAuth flow uses PKCE (RFC 7636) to protect the authorization code from interception.
- Dynamic client registration follows RFC 7591; clients identify themselves and Statisfy validates redirect URIs before issuing tokens.
- All MCP traffic is HTTPS-only.