Start with production.
Connect your primary org and discover its visible sandboxes. Sign in to each sandbox separately before you or your agent can use it.
For you. And your agents.
Connect your Salesforce orgs. Create users, configure access, and review leads in your chat. Let your agent prepare the work, with your approval before a change is applied.
Production and sandboxes. One workspace. You hold the controls.
| NAME | COMPANY | STATUS |
|---|---|---|
| Maya Chen | Orbit Labs | Working |
| Alex Rivera | Nova Systems | Open |
| Sam Okafor | Altitude Co. | Open |
“Show me the leads in my QA sandbox.”
YOUR ORGS. YOUR HEADSPACE.
Headful Cloud brings users, access setup, permission sets, and leads into a focused workspace beside your conversation or in your browser. Your agent works with the same saved workflows and the orgs you choose.
Your Salesforce orgs
One authenticated MCP connection
Your favorite chat
Connect an OAuth-compatible MCP host.
Connect your primary org and discover its visible sandboxes. Sign in to each sandbox separately before you or your agent can use it.
Save your Salesforce application credentials in Setup. Headful Cloud stores them encrypted; the plugin carries no org tokens or client secrets.
Your agent can prepare a user draft or access change. You review the exact fields and permissions before choosing Create or Apply.
YOUR ORGS, IN THE CONVERSATION
Choose an org. Inspect a lead. Prepare a permission change. Follow a fictional session, then try the small controls inside it.
Show my production org and its sandboxes.
Looking at the connected orgs
list_orgsReadlist_sandboxesReadNorthstar Production is connected. UAT is visible, but it needs its own Salesforce login and consent before I can use it.
Sandbox discovery is limited by Salesforce privileges. A visible sandbox is not a connected org.
Choose the right org. Completed fictional example.
A USEFUL HEAD FOR THE WORK AT HAND
Complete a focused form in chat, then continue the same saved task in the detailed Headful workspace. Your org, user, draft, and verified operations stay together.
Keep production and sandbox connections together. Switch orgs in Setup or use the focused org picker in a compatible chat.
Separate Salesforce consent for each orgRead the sandbox inventory visible from your production org. Connect each sandbox with an application configured for it.
Discovery does not grant sandbox accessSearch leads by name or company, sort a returned list, and inspect record details from an org you connected.
Unconverted leads · read-onlyComplete a compact form with the org’s available profiles, licenses, and supported settings. Review the exact user fields before choosing Create.
User created. Access setup is pending.Open the same user and workflow in the detailed workspace. Inspect current assignments, choose compatible permission sets, and review additions or removals.
Verified operations remain savedBrowse permission sets and their object and field access. Prepare changes to custom labels, descriptions, and supported permission flags.
Custom permission sets only for editsSee the current values beside the proposed values. Approve or reject the review; an approved change is checked again in Salesforce.
Agents prepare. You approve.Grant access to selected orgs and decide whether the agent can prepare reviews. Revoke its Headful Cloud connection from Setup.
Read and proposal access are separateSTART WITH SOMETHING USEFUL
Ask which sandboxes are visible from production. Connect the QA org you need, then grant your agent access to that org.
“List the sandboxes visible from my production org.”
Choose an org and browse its unconverted leads. Open a record to see its company, status, and available contact details.
“Show the leads in my QA sandbox.”
Inspect a custom permission set, prepare the intended Lead or field access change, and review it before applying.
“Prepare Lead read access in our Sales Review permission set.”
Review the new user’s fields in a compact App. After creation is verified, continue in the workspace to assign or remove permission sets.
“Create a user for Maya Chen in my UAT sandbox.”
FROM HEADLESS TO HEADFUL
Headful Cloud supplies the MCP. You bring a Salesforce OAuth application and choose who can use your orgs.
Sign in with your invited email. Add your Salesforce OAuth application and authorize production, then connect the sandboxes you need.
Follow your host’s setup guide. Add headful.cloud/mcp through OAuth, sign in, and choose which orgs the agent may access.
Complete a compact creation form, then continue access setup in the detailed workspace. Read leads and review exact permission changes with the same org and workflow context.
A SMALL PACKAGE. A USEFUL HEAD.
The Agent Plugin pairs the authenticated MCP connection with four focused skills: Salesforce admin, user creation and access, lead review, and permission-set review.
Download the package for a supported local plugin workflow, or connect the MCP directly through your chat host’s custom connector setup.
Invitation-only beta. Headful Cloud is not yet listed or approved in the ChatGPT plugin directory. Manual installation and App rendering depend on your host and workspace.
YOUR SALESFORCE ADMIN PLUGIN
Your org access comes from your account and consent. The download contains no credentials.
A FEW THINGS TO GET YOUR HEAD AROUND
Know what connects, what your agent can do, and where you stay in control.
Read the full setup guide ↗Headful Cloud is a Salesforce admin workspace with an authenticated MCP and an Agent Plugin. Connect your orgs, create Salesforce users, continue their access setup, inspect permission sets, and review leads. Compact chat Apps and the detailed workspace share the same saved workflows.
No. Headful Cloud supplies the MCP and Apps your agent uses. You configure a Salesforce OAuth application, save its client ID and secret in Headful Cloud Setup, and authorize each org through Salesforce.
Yes. Start with production to discover the sandbox inventory visible to that Salesforce user. Each sandbox needs its own login and OAuth consent, using an application configured for it. You can also connect a sandbox manually.
Agents can read records and, if you grant proposal access, prepare supported permission-set changes. Approval happens in Headful Cloud, where you review the exact before and after. Lead changes and general Salesforce writes are outside this initial scope.
Headful Cloud exposes an authenticated MCP for compatible hosts. Use your host’s custom MCP connection workflow and follow the setup guide for available plugin installation paths. The examples above simulate ChatGPT and Claude; native host acceptance and store approval are separate from this preview.
Application secrets and connected-org tokens are stored encrypted on the server. They are not included in the plugin or returned to your agent. Salesforce permissions still determine what the connected user can read or change.
Yes. Revoke its Headful Cloud connection from Agent Access in Setup. To give an agent access to an org you add later, connect the agent again and select that org during consent.
Join the launch list below. The beta is invitation-only. You can inspect the setup guide and download the plugin package while you wait for your invitation.
HEADS UP. YOUR CLOUD IS GETTING READY.
Join the launch list for Salesforce admins.
We’ll email you when your invitation is ready.