Connecting...
Tags: ai automation

AI Assistants

Run FolioReady from the AI assistant you already work in. Connect ChatGPT, Claude, Claude Code or Cursor to your FolioReady account, then ask in plain words: "send Jane Smith the onboarding pack", "who hasn't returned their tax organizer?", "what EIN did Acme give us?"

The assistant connects to FolioReady over MCP, the Model Context Protocol. ChatGPT and Claude, including the Claude desktop app, connect by signing in. Claude Code and Cursor use your company API key, and so does Claude Desktop when you set it up through its config file.

What the assistant can do

Ask it toWhat happens
List your templatesShows your published templates, and whether sending one emails the client
Find a clientSearches your clients by name or email
Add a clientCreates a client, owned by your company's primary contact
Send a folioCreates a folio for a client from a template and, when the template sends requests, emails the client
Check a folioShows the status of one folio, or of every folio for a client
Show a folio's historyLists what has happened: emails sent, the client opening it, submissions, AI extraction
Read what came backReturns each field the client filled in or AI extracted, by its label, plus the files uploaded

Sending emails a real client. Your assistant is told so, and well-behaved assistants ask you to confirm before sending. A template that files against a CRM record you pick when sending still has to be sent from the FolioReady app.

Before you start

ChatGPT and Claude need nothing set up in advance. Any member of your team can connect their own by signing in; see ChatGPT and Claude below.

Claude Code, Cursor and Claude Desktop's config file need your company API key, on Company Details → API Key in FolioReady. Only a manager can see it. The same page shows each setup below with your server URL and key already filled in, ready to copy.

Each setup, ready to copy, on Company Details → API Key

Claude Code

Run this in a terminal, with your own key:

claude mcp add --transport http folioready https://folioready.com/mcp --header "Authorization: Bearer <your-api-key>"

Start Claude Code and run /mcp to check that folioready is connected.

Cursor

Add FolioReady to ~/.cursor/mcp.json, or to .cursor/mcp.json in a project:

{
  "mcpServers": {
    "folioready": {
      "url": "https://folioready.com/mcp",
      "headers": { "Authorization": "Bearer <your-api-key>" }
    }
  }
}

Claude Desktop

Claude Desktop can sign in like Claude on the web; see ChatGPT and Claude below. To use the API key instead, set it up through the config file. Claude Desktop reaches a remote server through the mcp-remote bridge, which needs Node.js installed. Open Settings → Developer → Edit Config and add:

{
  "mcpServers": {
    "folioready": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://folioready.com/mcp", "--header", "Authorization:${AUTH_HEADER}"],
      "env": { "AUTH_HEADER": "Bearer <your-api-key>" }
    }
  }
}

Restart Claude Desktop. FolioReady appears in the tools menu.

ChatGPT and Claude

ChatGPT and Claude (on the web, desktop and mobile) connect by signing in, with no API key. Any member of your team can connect their own.

Claude: open Customize → Connectors, choose Add custom connector, and enter https://folioready.com/mcp. Claude sends you to FolioReady to sign in and approve.

ChatGPT: in developer mode, add a connector with the URL https://folioready.com/mcp. ChatGPT sends you to FolioReady to sign in and approve.

The approval screen names the app, the company it will reach, and what it may do. Adding clients and sending folio requests share one checkbox. Untick it and the assistant can look things up but can't add a client or email anyone. The assistant acts as you, so it can do no more than you can in FolioReady.

Claude's approval screen, with sending ticked by default

To disconnect, open User Settings → Connected Apps and choose Revoke. A manager can do the same for any team member from their page under Team Members.

Your connected apps, under User Settings → Connected Apps
A team member's connected apps, on their page under Team Members

Keeping it secure

  • The API key acts for your whole company. Anyone holding it can do everything listed above. Keep it out of shared files and repositories.
  • Regenerating the key disconnects every assistant set up with it. Regenerate it from Company Details → API Key if it leaks, then update each assistant's setup with the new key. Assistants connected by signing in are not affected; revoke those under Connected Apps.
  • Your assistant's provider handles the data it retrieves. See "AI Assistants You Connect" in our privacy policy.

Related