Skip to main content

MCP Server Release Notes

New features and notable improvements in the Cirra AI MCP Server, newest release first. Releases are rolled out automatically — there is nothing to install or upgrade on your side.

4.9.0 — October 22, 2026​

All Team Orgs. Team owners and admins on the Salesforce Organizations page have an All Team Orgs tab. It lists every Salesforce connection on the team and its sub-teams. You can search, filter, export the list, and delete one connection or several. Members still see only their own connections. See Managing orgs.

Rotate a custom app's key and secret together. Rotating a custom External Client App or Connected App asks for the new Consumer Key and Consumer Secret together. Salesforce issues them as a pair. The current Consumer Key is filled in, so you can still replace only the secret. See Registering your own External Client App.

Invite a Basic member to Admin or Owner. On the team page, an owner can invite a Basic member to become an Owner or an Admin. An admin can invite a Basic member to become an Admin. The invitation stays pending until they sign up and accept it, and their role does not change before that. Accepting an invitation opens the team they were invited to. See Managing team users.

Personal accounts follow the company. The top-level team's setting is Allow personal accounts for domain members? It covers everyone on the company's email domain. A sub-team shows the top-level team's choice and cannot change it. People who already have a personal account keep it. Someone who is invited joins the team without a personal workspace. Someone who signs in on the web without an invitation, on a domain where personal accounts are not allowed, sees Ask for an invitation, with the company's owners and admins and a link to email them. Someone refused during an AI client's connection flow is still blocked, and sees that flow's setup-failed message.

A conversation stays on its team. Cirra AI keeps a conversation on the team and Salesforce connection it started with, even if you later change the default team. If you have more than one place to work — more than one team, or a team and a personal account — and a request does not name one, Cirra AI lists the choices. With only a personal account, or only one team, the request runs there. A bulk CSV upload stays on the team it was started for. See Switching between Cirra AI teams.

Credit Usage for the whole period. Credit Usage shows 500 events at a time. When the period has more, Previous and Next move through them. Export CSV downloads every event in the period. The search box filters the page on screen and leaves the export whole. The team, user, and connection totals cover the whole period.

Starting access rules for new accounts. New teams and new personal accounts start with production access rules. Accounts you already have keep their current rules. Sandbox, developer, and scratch orgs stay unrestricted for every role. A more specific rule can relax these starting rules. See Access Rules.

On a new team, production access for Member and Basic starts at:

  • Metadata, User data, and Business data — Read only
  • Personal setup data — Read and write
  • DevOps — No access

Owners and admins have no starting restriction on those categories.

A new personal account, in production, starts at Read only for Metadata and Business data, and Read and write for User data, Personal setup data, and DevOps.

Clearer Salesforce results.

  • A query keeps fields Salesforce returned empty, so an empty value is distinct from a field that was not returned.
  • A bulk query returns yes/no fields as true and false, the same as an ordinary query. A text value that is exactly true or false is treated the same way.
  • Reading metadata that does not exist is reported as not found.
  • When a page size is requested, the first page of a long list follows that size, up to what fits in one response. With no page size, the first page is a short preview.
  • A 15-character Salesforce id and its 18-character form name the same record. A short user id finds the connection, and a short profile id is applied when you set field or record-type access.

Safer profile and field updates.

  • After a profile update, Cirra AI checks that Salesforce applied it. If part of the change was ignored, you are told which part.
  • Adding the first Login IP Range on a profile requires confirmation. Those ranges are an allowlist and can lock people out. Trusted ranges for the org belong in Network Access. Cirra AI does not remove a profile Login IP Range or change its addresses; delete the range in Setup. Changing only the range's description is allowed.
  • A profile update keeps the profile's tab settings, and can address a tab, record type, Apex class, Visualforce page, app, or flow by name.
  • Setting a field to Hidden for a profile removes that field permission. Hidden is the absence of the permission, and Salesforce rejects a field-permission row that is not readable.

Sign-in errors. When sign-in is refused, the page shows the reason and Try again.

Critical and high severity fixes. Dependency updates in this release close the critical and high severity issues below.

Critical:

High:

4.8.0 — September 25, 2026​

Bulk data loads from a CSV file. When you ask Cirra AI to load a large number of records, it can now hand you a secure upload page for your CSV file instead of passing the data through the chat. The file goes straight to Salesforce's Bulk API, so large loads no longer fill up your AI client's context. For small loads that fit in the chat, Cirra AI tells the AI client the upload is not needed.

Clearer, more forgiving SOQL queries.

  • When a query names a field that does not exist, the error now lists the object's real field names so the AI can correct itself on the next try.
  • A field you cannot see because of Field-Level Security is now reported as such, rather than as a missing field.
  • Queries sent to the wrong Salesforce API (for example, a setup object that only the Tooling API can query) are redirected with guidance instead of failing.
  • Valid WHERE clauses that were previously rejected as unsafe now run.

Promotion codes at checkout. You can now enter a promotion code when you activate a paid plan.

Shared - global is for production orgs. The Shared - global sharing option is now available for production Salesforce orgs only. Sandbox orgs that were set to Shared - global are now Shared with your team. See Sharing an org.

4.7.0 — September 2, 2026​

Refer Cirra AI and earn rewards. A new Refer Cirra AI link in the sidebar gives you a personal referral link. People who sign up through it get 10% off, and you earn up to $100 per referral — $25 for a Professional plan or $100 for a Team plan.

4.6.0 — August 18, 2026​

Separate ChatGPT web and desktop setup. The setup walkthrough now has its own steps for ChatGPT on the web and in the desktop app. See ChatGPT.

A first task to try. When setup is complete, the You're All Set! screen suggests a first task to run in your AI client.

Smoother Salesforce connection. Cirra AI asks the questions that decide which Salesforce app to use before sending you to Salesforce, and when a connection fails it now shows you why instead of a generic error page.

Easier access-rule review. The Access Rules filters link to each other, and the Effective access panel is easier to read. See Access Rules.

Better Flow and metadata editing. Repeating metadata elements are now always returned as lists, and edits can target child elements by name — making targeted updates to large Flows and other metadata more reliable. Cirra AI now uses Salesforce REST API version 67.0.

4.5.1 — August 9, 2026​

New Salesforce Connect and CMS tools. Three new tools let the AI work with more of Salesforce:

  • connect_rest — call the Salesforce Connect REST API (Experience Cloud sites, Files, Personalization, Commerce, and more).
  • cms_content — create, update, publish and organize Salesforce CMS content.
  • cms_delivery — search and read published CMS content.

Faster access-rule authoring. Create one rule for several objects or fields at once, with type-ahead search over your org's schema. Rules are now sorted from most to least specific, and team administrators can inspect the access that applies to any team member.

4.5.0 — August 7, 2026​

Access Rules. A new Access Rules page controls exactly what the MCP Server may read and write in your Salesforce orgs — by environment type, connection, role, and user, down to individual objects and fields. The strictest matching rule always wins. See Access Rules.

Run Apex and Flow tests. The new run_tests tool runs Apex tests and Flow tests in your org — specific classes and methods, or org-wide — and reports the results.

Field-Level Security errors are no longer hidden. When Salesforce refuses part of a change because of Field-Level Security, Cirra AI now reports it instead of silently skipping it.

Gemini Enterprise. Gemini Enterprise is now a supported AI client. See Gemini Enterprise.

Your organization ID on the Team page. The team header now shows your Cirra AI organization ID.

4.4.0 — August 2, 2026​

Field-level access control. Allow the MCP Server to work with an object while denying it specific fields on that object. The restriction applies to queries and record changes, including bulk operations.

Faster edits to large metadata. Large metadata such as Flows can now be changed with small, targeted patches instead of resending the whole definition, making edits faster and more reliable.

Paste any Salesforce URL when connecting. Lightning and Setup URLs are automatically resolved to your org's My Domain.

Continue with Google. You can sign in to the MCP Server with your Google account.

Safer authorization. The consent screen now shows where you will be sent after approving access, so you can spot a suspicious request.

4.3.0 — July 26, 2026​

External Client Apps. Connect your Salesforce orgs through Salesforce's External Client Apps — either the shared Cirra AI app or one you register yourself. See Using an External Client App.

Log in with Salesforce, and Shared - global orgs. Share an org with every Salesforce user of that org. They sign in with Log in with Salesforce and can start using Cirra AI from their AI client without a separate Cirra AI password. See Sharing an org.

Start a free trial from your AI client. New users can sign up and connect their first Salesforce org directly from the AI client's connection flow.

Permission-aware guidance. Cirra AI checks what your Salesforce user is allowed to do. When your permissions are limited, the AI uses read-only alternatives and tells you when a request needs elevated Salesforce permissions, instead of retrying calls that will fail.

Encrypted fields stay masked. Values of Salesforce encrypted fields are masked in query results and reports.

Clearer connection status and errors. Org cards now show when an org does not have API access enabled, and OAuth errors include the provider's reason and troubleshooting hints.

Sort and filter team members. The team members list can be sorted and filtered by role.