Documentation
Frida in your AI assistant
Read deals, prepare customer meetings and track changes from ChatGPT or Claude. With separate permission, request specific changes too.
Custom MCP connection · not yet listed or officially approved in the ChatGPT or Claude directory.
Quickstart
From your account to the first answer using your own Frida data.
Workflows and examples
Start with a specific question. Your assistant chooses the tools; below you can also inspect the call structure.
Data, access and limits
Understand exactly which information the connection can use and what consent means.
Troubleshooting
Start with connection status. Never repeat a possible change with a new ID before checking what happened.
Changelog and compatibility
Changes to the public connection and what they mean for consent.
Tool reference
Search the current conversation tools. Schemas, descriptions and read-only annotations come directly from the generated contract.
Choose your next step
Start with Quickstart to connect your account. Workflows show useful requests. Tools is the searchable reference with actual input and output schemas.
One connection to stored data
The connection reads stored Frida deals and authorised mail evidence. It does not search your whole Outlook mailbox. Another mail integration in your chatbot has its own login and permissions.
You need no API key to add the connection. Sign in at Frida and approve access. Reading documentation grants no account access.
Building your own integration?
Use OAuth and the MCP tool contract. The URL is an MCP endpoint, not a REST endpoint for individual tools. Unrecognised clients receive narrower access and can only propose changes for approval in Frida. No public sandbox is documented here; use a test account with fictional data for change tests.