Folderly AI · Assistant connection
Your campaign context, inside your assistant.
Use selected saved briefs, voice, and approved proof to prepare email with ChatGPT or Claude. Review the copy and keep useful work in your Folderly AI account.
A useful first request
“Folderly AI, find my agency campaign, review this follow-up, and save it as a new draft for my review.”
Connection setup
Any Folderly AI account can find custom connection instructions in its settings. Available connection features depend on your assistant account and workspace. Directory availability is separate from a custom connection.
The hosted endpoint is https://generate.folderly.com/api/mcp.
- Sign in and open ChatGPT and Claude in your Folderly AI settings for your assistant’s OAuth client ID and setup steps. The server URL alone is not enough.
- Add the endpoint and that client ID in your assistant’s custom connector settings.
- Sign into Folderly AI and review the requested permissions. Only connect an assistant you intend to authorize.
- Select a campaign explicitly. Review and save use no generation credits. Folderly AI generation requires the current API entitlement and the operation’s stated allowance.
- Use the same operation identifier after a generation timeout so an existing result can be recovered.
What the connection does
It can list and retrieve your campaigns, review email text, generate one email when requested, save an unapproved version, and report available usage. Saving does not approve or send email. Copy review does not verify facts or measure inbox placement.
Your suite context and sending evidence
With separate suite-read permission, your assistant can find your remembered domains, recent work and product connection states. It can read dated observations for a selected domain or saved campaign version and show what is missing or out of date.
Ask: “Show the evidence for my selected sending domain, explain any gaps, and give me the Folderly link to run a fresh check.” Fresh checks and native product actions open in Folderly for you to complete. The connection does not run them automatically.
Existing connections keep their original access. Refresh the tools and approve the additional permission when your assistant requests it. Reading campaign evidence also requires campaign-read permission. These suite reads use no generation credits.
Fresh Lens scans are a separate capability and permission. If they are not available in your tool list, the suite-read connection cannot run one.
Local HTML template preflight
With the existing folderly:emails:review permission, check_template accepts one strict {html} input that is non-empty and at most 64 KiB in UTF-8. It runs bounded, deterministic observations on the supplied markup.
The result reports counts for active elements, inline event attributes, scriptable URL schemes, references and image alt states, plus distinct spam-trigger counts by severity using Folderly's existing deliverability vocabulary on parsed text. Script, style and template text are excluded from the spam heuristic. Hidden text can still be included, and malformed markup, conditional comments or analysis limits can make coverage partial.
This is a local AI preflight. It returns bounded findings without raw HTML, snippets, URL values or addresses. It does not fetch, render or execute the supplied markup, call a provider, save content or results, send email, or consume generation credits. It does not establish rendered-visible text, inbox placement or a safety certification; standard account, permission and rate checks still apply.
Flash seed-test readiness
Fresh Flash test readiness is a separate capability and permission. If it is not in your tool list, this connection cannot create or read a Flash seed test. The capability remains disabled until its native contract, consent and account-owned pilot are separately approved.
Campaign content is shared with the assistant when you request it. Read how the connection uses your data before connecting confidential client material.
Open saved campaignsHow this connection uses your data
This describes the current Folderly AI MCP connection. Read it alongside the Folderly Privacy Policy, which remains the authoritative privacy policy. Your assistant account has its own data settings and policies.
Account access and information returned to your assistant
Clerk handles sign-in and OAuth consent. The connection checks your account and granted permissions for each tool. Listing campaigns returns their titles, identifiers and update times. Opening a selected campaign returns its client name, offer, audience, goal, voice, approved proof, available assets and current saved result, together with its revision, approval state and workspace link. It does not return the full saved version history. Usage checks return generation availability, remaining credits and operation costs.
Suite-read access additionally returns bounded remembered-domain observations, recent-work references, product connection states and dated saved Lens evidence. It does not return mailbox addresses, native product credentials or raw message content. Product connection labels describe navigation; they do not prove current native access, paid entitlement or a verified fix. Public DNS observations do not measure inbox placement.
check_template returns bounded observations and counts to the assistant without the supplied markup, snippets, URL values or addresses. The tool does not save the supplied content or result. Standard account, permission and rate checks still apply.
Reviewing and generating copy
Review processes the subject and body supplied to the tool using Folderly's content rules. It does not call Folderly's AI generation provider or save a campaign. When you explicitly request Folderly generation, the submitted offer, audience, goal, voice, proof and available assets are used by OpenAI to prepare the email. Offer, audience and goal information is also used for template matching through OpenAI embeddings. Template searches may cache search text and embeddings in server memory. Generation returns the copy to your assistant; saving it to a campaign is a separate action. Review and save use no generation credits.
Saved campaigns and temporary generation results
Saving stores your title, brief and current result in your Folderly account. Each save creates an unapproved version; a campaign keeps up to ten saved versions, and further saves remove the oldest versions. These saved campaigns are separate from the temporary copy kept to recover a generation request.
Once a generation operation has completed or failed and is more than 24 hours old, its temporary result is eligible for clearing during maintenance or a later retry. This is not a promise that all data is deleted at exactly 24 hours: unresolved operations can retain results while reconciliation is pending. Operation identifiers, account and connection identifiers, input hashes, status, timestamps and credit records can remain after the generated text is cleared to support recovery and prevent duplicate charges.
Disconnecting and deletion requests
Manage the connection in your assistant and connected-account settings. Revoking refresh access prevents token renewal, but already-issued access tokens may remain usable until they expire; the current OAuth access-token lifetime is one day. Disconnecting does not delete saved Folderly campaigns or copies already returned to the assistant. The MCP tools do not provide a delete action. For data rights and deletion requests, use the contact information in the Folderly Privacy Policy.