Skip to main content

Cirra AI Salesforce Admin MCP Server

Overview Discussions Admin

Server Details

Comprehensive Salesforce administration and management

Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status: Unhealthy
Uptime: 0.0% over 37 days
OAuth: Works in Glama
Last Tested: 2026-09-23 03:44
Transport: Streamable HTTP
URL

TDQS

A3.9/5.0

Scored 2026-05-08 09:49 across 40 tools

Disambiguation5/5

Each tool targets a distinct Salesforce administrative operation (e.g., metadata management, object/field manipulation, user/permission management, reporting, etc.) with no significant overlap. The descriptions clearly differentiate the tools, making it easy for an agent to select the correct one.

Naming Consistency5/5

All tool names follow a consistent `object_action` or `action_object` snake_case pattern (e.g., `group_create`, `metadata_list`, `user_update`). Even compound names like `page_layout_clone` and `permission_set_assignments` maintain the pattern, with only minor plural variations (`sobjects_list` vs `sobject_describe`) that do not hinder readability.

Tool Count5/5

The 40 tools are well-scoped for a comprehensive Salesforce admin server, covering a wide range of functionalities (metadata, objects, users, permissions, reports, etc.). Each tool serves a distinct purpose without unnecessary duplication, justifying the count for the complexity of the domain.

Completeness5/5

The tool set provides extensive coverage of Salesforce administrative tasks, including CRUD operations for metadata, custom objects/fields, user/permission management, page layouts, value sets, reports, and Tooling API access. While some niche features (e.g., email templates) may be missing, the core workflows are fully supported with no obvious gaps for typical admin use cases.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

38 tool updatesJul 27, 2026

Changedgroup_create1 field changed

addedInput schema / properties / cirra_ai_team

Added value: +{
+  "description": "(optional) Cirra team ID or name that owns the Salesforce connection to use for this call. Must be provided together with 'sf_user'. Use it to run against a specific team's connection without changing your default team — e.g. to keep separate chats on Salesforce orgs in different teams. Omit to use your current/default team.",
+  "type": "string"
+}

Changedgroup_members1 field changed

addedInput schema / properties / cirra_ai_team

Added value: +{
+  "description": "(optional) Cirra team ID or name that owns the Salesforce connection to use for this call. Must be provided together with 'sf_user'. Use it to run against a specific team's connection without changing your default team — e.g. to keep separate chats on Salesforce orgs in different teams. Omit to use your current/default team.",
+  "type": "string"
+}

Changedgroup_update1 field changed

addedInput schema / properties / cirra_ai_team

Added value: +{
+  "description": "(optional) Cirra team ID or name that owns the Salesforce connection to use for this call. Must be provided together with 'sf_user'. Use it to run against a specific team's connection without changing your default team — e.g. to keep separate chats on Salesforce orgs in different teams. Omit to use your current/default team.",
+  "type": "string"
+}

Changedlink_build1 field changed

addedInput schema / properties / cirra_ai_team

Added value: +{
+  "description": "(optional) Cirra team ID or name that owns the Salesforce connection to use for this call. Must be provided together with 'sf_user'. Use it to run against a specific team's connection without changing your default team — e.g. to keep separate chats on Salesforce orgs in different teams. Omit to use your current/default team.",
+  "type": "string"
+}

Changedmetadata_create1 field changed

addedInput schema / properties / cirra_ai_team

Added value: +{
+  "description": "(optional) Cirra team ID or name that owns the Salesforce connection to use for this call. Must be provided together with 'sf_user'. Use it to run against a specific team's connection without changing your default team — e.g. to keep separate chats on Salesforce orgs in different teams. Omit to use your current/default team.",
+  "type": "string"
+}

Changedmetadata_delete1 field changed

addedInput schema / properties / cirra_ai_team

Added value: +{
+  "description": "(optional) Cirra team ID or name that owns the Salesforce connection to use for this call. Must be provided together with 'sf_user'. Use it to run against a specific team's connection without changing your default team — e.g. to keep separate chats on Salesforce orgs in different teams. Omit to use your current/default team.",
+  "type": "string"
+}

Changedmetadata_describe1 field changed

addedInput schema / properties / cirra_ai_team

Added value: +{
+  "description": "(optional) Cirra team ID or name that owns the Salesforce connection to use for this call. Must be provided together with 'sf_user'. Use it to run against a specific team's connection without changing your default team — e.g. to keep separate chats on Salesforce orgs in different teams. Omit to use your current/default team.",
+  "type": "string"
+}

Changedmetadata_list1 field changed

addedInput schema / properties / cirra_ai_team

Added value: +{
+  "description": "(optional) Cirra team ID or name that owns the Salesforce connection to use for this call. Must be provided together with 'sf_user'. Use it to run against a specific team's connection without changing your default team — e.g. to keep separate chats on Salesforce orgs in different teams. Omit to use your current/default team.",
+  "type": "string"
+}

Changedmetadata_read1 field changed

addedInput schema / properties / cirra_ai_team

Added value: +{
+  "description": "(optional) Cirra team ID or name that owns the Salesforce connection to use for this call. Must be provided together with 'sf_user'. Use it to run against a specific team's connection without changing your default team — e.g. to keep separate chats on Salesforce orgs in different teams. Omit to use your current/default team.",
+  "type": "string"
+}

Changedmetadata_update1 field changed

addedInput schema / properties / cirra_ai_team

Added value: +{
+  "description": "(optional) Cirra team ID or name that owns the Salesforce connection to use for this call. Must be provided together with 'sf_user'. Use it to run against a specific team's connection without changing your default team — e.g. to keep separate chats on Salesforce orgs in different teams. Omit to use your current/default team.",
+  "type": "string"
+}

Changedpage_layout_clone1 field changed

addedInput schema / properties / cirra_ai_team

Added value: +{
+  "description": "(optional) Cirra team ID or name that owns the Salesforce connection to use for this call. Must be provided together with 'sf_user'. Use it to run against a specific team's connection without changing your default team — e.g. to keep separate chats on Salesforce orgs in different teams. Omit to use your current/default team.",
+  "type": "string"
+}

Changedpage_layout_update1 field changed

addedInput schema / properties / cirra_ai_team

Added value: +{
+  "description": "(optional) Cirra team ID or name that owns the Salesforce connection to use for this call. Must be provided together with 'sf_user'. Use it to run against a specific team's connection without changing your default team — e.g. to keep separate chats on Salesforce orgs in different teams. Omit to use your current/default team.",
+  "type": "string"
+}

Changedpermission_set_assignments1 field changed

addedInput schema / properties / cirra_ai_team

Added value: +{
+  "description": "(optional) Cirra team ID or name that owns the Salesforce connection to use for this call. Must be provided together with 'sf_user'. Use it to run against a specific team's connection without changing your default team — e.g. to keep separate chats on Salesforce orgs in different teams. Omit to use your current/default team.",
+  "type": "string"
+}

Changedpermission_set_update1 field changed

addedInput schema / properties / cirra_ai_team

Added value: +{
+  "description": "(optional) Cirra team ID or name that owns the Salesforce connection to use for this call. Must be provided together with 'sf_user'. Use it to run against a specific team's connection without changing your default team — e.g. to keep separate chats on Salesforce orgs in different teams. Omit to use your current/default team.",
+  "type": "string"
+}

Changedprofile_clone1 field changed

addedInput schema / properties / cirra_ai_team

Added value: +{
+  "description": "(optional) Cirra team ID or name that owns the Salesforce connection to use for this call. Must be provided together with 'sf_user'. Use it to run against a specific team's connection without changing your default team — e.g. to keep separate chats on Salesforce orgs in different teams. Omit to use your current/default team.",
+  "type": "string"
+}

Changedprofile_describe1 field changed

addedInput schema / properties / cirra_ai_team

Added value: +{
+  "description": "(optional) Cirra team ID or name that owns the Salesforce connection to use for this call. Must be provided together with 'sf_user'. Use it to run against a specific team's connection without changing your default team — e.g. to keep separate chats on Salesforce orgs in different teams. Omit to use your current/default team.",
+  "type": "string"
+}

Changedprofile_update1 field changed

addedInput schema / properties / cirra_ai_team

Added value: +{
+  "description": "(optional) Cirra team ID or name that owns the Salesforce connection to use for this call. Must be provided together with 'sf_user'. Use it to run against a specific team's connection without changing your default team — e.g. to keep separate chats on Salesforce orgs in different teams. Omit to use your current/default team.",
+  "type": "string"
+}

Changedrecord_type_create1 field changed

addedInput schema / properties / cirra_ai_team

Added value: +{
+  "description": "(optional) Cirra team ID or name that owns the Salesforce connection to use for this call. Must be provided together with 'sf_user'. Use it to run against a specific team's connection without changing your default team — e.g. to keep separate chats on Salesforce orgs in different teams. Omit to use your current/default team.",
+  "type": "string"
+}

Changedrecord_type_update1 field changed

addedInput schema / properties / cirra_ai_team

Added value: +{
+  "description": "(optional) Cirra team ID or name that owns the Salesforce connection to use for this call. Must be provided together with 'sf_user'. Use it to run against a specific team's connection without changing your default team — e.g. to keep separate chats on Salesforce orgs in different teams. Omit to use your current/default team.",
+  "type": "string"
+}

Changedreport_run1 field changed

addedInput schema / properties / cirra_ai_team

Added value: +{
+  "description": "(optional) Cirra team ID or name that owns the Salesforce connection to use for this call. Must be provided together with 'sf_user'. Use it to run against a specific team's connection without changing your default team — e.g. to keep separate chats on Salesforce orgs in different teams. Omit to use your current/default team.",
+  "type": "string"
+}

Changedsf_connection_manage1 field changed

addedInput schema / properties / cirra_ai_team

Added value: +{
+  "description": "(optional) Cirra team ID or name that owns the Salesforce connection to use for this call. Must be provided together with 'sf_user'. Use it to run against a specific team's connection without changing your default team — e.g. to keep separate chats on Salesforce orgs in different teams. Omit to use your current/default team.",
+  "type": "string"
+}

Changedsobject_create1 field changed

addedInput schema / properties / cirra_ai_team

Added value: +{
+  "description": "(optional) Cirra team ID or name that owns the Salesforce connection to use for this call. Must be provided together with 'sf_user'. Use it to run against a specific team's connection without changing your default team — e.g. to keep separate chats on Salesforce orgs in different teams. Omit to use your current/default team.",
+  "type": "string"
+}

Changedsobject_describe1 field changed

addedInput schema / properties / cirra_ai_team

Added value: +{
+  "description": "(optional) Cirra team ID or name that owns the Salesforce connection to use for this call. Must be provided together with 'sf_user'. Use it to run against a specific team's connection without changing your default team — e.g. to keep separate chats on Salesforce orgs in different teams. Omit to use your current/default team.",
+  "type": "string"
+}

Changedsobject_dml1 field changed

addedInput schema / properties / cirra_ai_team

Added value: +{
+  "description": "(optional) Cirra team ID or name that owns the Salesforce connection to use for this call. Must be provided together with 'sf_user'. Use it to run against a specific team's connection without changing your default team — e.g. to keep separate chats on Salesforce orgs in different teams. Omit to use your current/default team.",
+  "type": "string"
+}

Changedsobject_field_create1 field changed

addedInput schema / properties / cirra_ai_team

Added value: +{
+  "description": "(optional) Cirra team ID or name that owns the Salesforce connection to use for this call. Must be provided together with 'sf_user'. Use it to run against a specific team's connection without changing your default team — e.g. to keep separate chats on Salesforce orgs in different teams. Omit to use your current/default team.",
+  "type": "string"
+}

Changedsobject_field_update1 field changed

addedInput schema / properties / cirra_ai_team

Added value: +{
+  "description": "(optional) Cirra team ID or name that owns the Salesforce connection to use for this call. Must be provided together with 'sf_user'. Use it to run against a specific team's connection without changing your default team — e.g. to keep separate chats on Salesforce orgs in different teams. Omit to use your current/default team.",
+  "type": "string"
+}

Changedsobject_update1 field changed

addedInput schema / properties / cirra_ai_team

Added value: +{
+  "description": "(optional) Cirra team ID or name that owns the Salesforce connection to use for this call. Must be provided together with 'sf_user'. Use it to run against a specific team's connection without changing your default team — e.g. to keep separate chats on Salesforce orgs in different teams. Omit to use your current/default team.",
+  "type": "string"
+}

Changedsobjects_list1 field changed

addedInput schema / properties / cirra_ai_team

Added value: +{
+  "description": "(optional) Cirra team ID or name that owns the Salesforce connection to use for this call. Must be provided together with 'sf_user'. Use it to run against a specific team's connection without changing your default team — e.g. to keep separate chats on Salesforce orgs in different teams. Omit to use your current/default team.",
+  "type": "string"
+}

Changedsoql_query1 field changed

addedInput schema / properties / cirra_ai_team

Added value: +{
+  "description": "(optional) Cirra team ID or name that owns the Salesforce connection to use for this call. Must be provided together with 'sf_user'. Use it to run against a specific team's connection without changing your default team — e.g. to keep separate chats on Salesforce orgs in different teams. Omit to use your current/default team.",
+  "type": "string"
+}

Changedtooling_api_describe1 field changed

addedInput schema / properties / cirra_ai_team

Added value: +{
+  "description": "(optional) Cirra team ID or name that owns the Salesforce connection to use for this call. Must be provided together with 'sf_user'. Use it to run against a specific team's connection without changing your default team — e.g. to keep separate chats on Salesforce orgs in different teams. Omit to use your current/default team.",
+  "type": "string"
+}

Changedtooling_api_dml1 field changed

addedInput schema / properties / cirra_ai_team

Added value: +{
+  "description": "(optional) Cirra team ID or name that owns the Salesforce connection to use for this call. Must be provided together with 'sf_user'. Use it to run against a specific team's connection without changing your default team — e.g. to keep separate chats on Salesforce orgs in different teams. Omit to use your current/default team.",
+  "type": "string"
+}

Changedtooling_api_query1 field changed

addedInput schema / properties / cirra_ai_team

Added value: +{
+  "description": "(optional) Cirra team ID or name that owns the Salesforce connection to use for this call. Must be provided together with 'sf_user'. Use it to run against a specific team's connection without changing your default team — e.g. to keep separate chats on Salesforce orgs in different teams. Omit to use your current/default team.",
+  "type": "string"
+}

Changedtooling_api_search1 field changed

addedInput schema / properties / cirra_ai_team

Added value: +{
+  "description": "(optional) Cirra team ID or name that owns the Salesforce connection to use for this call. Must be provided together with 'sf_user'. Use it to run against a specific team's connection without changing your default team — e.g. to keep separate chats on Salesforce orgs in different teams. Omit to use your current/default team.",
+  "type": "string"
+}

Changeduser_create1 field changed

addedInput schema / properties / cirra_ai_team

Added value: +{
+  "description": "(optional) Cirra team ID or name that owns the Salesforce connection to use for this call. Must be provided together with 'sf_user'. Use it to run against a specific team's connection without changing your default team — e.g. to keep separate chats on Salesforce orgs in different teams. Omit to use your current/default team.",
+  "type": "string"
+}

Changeduser_describe1 field changed

addedInput schema / properties / cirra_ai_team

Added value: +{
+  "description": "(optional) Cirra team ID or name that owns the Salesforce connection to use for this call. Must be provided together with 'sf_user'. Use it to run against a specific team's connection without changing your default team — e.g. to keep separate chats on Salesforce orgs in different teams. Omit to use your current/default team.",
+  "type": "string"
+}

Changeduser_update1 field changed

addedInput schema / properties / cirra_ai_team

Added value: +{
+  "description": "(optional) Cirra team ID or name that owns the Salesforce connection to use for this call. Must be provided together with 'sf_user'. Use it to run against a specific team's connection without changing your default team — e.g. to keep separate chats on Salesforce orgs in different teams. Omit to use your current/default team.",
+  "type": "string"
+}

Changedvalue_set_create1 field changed

addedInput schema / properties / cirra_ai_team

Added value: +{
+  "description": "(optional) Cirra team ID or name that owns the Salesforce connection to use for this call. Must be provided together with 'sf_user'. Use it to run against a specific team's connection without changing your default team — e.g. to keep separate chats on Salesforce orgs in different teams. Omit to use your current/default team.",
+  "type": "string"
+}

Changedvalue_set_update1 field changed

addedInput schema / properties / cirra_ai_team

Added value: +{
+  "description": "(optional) Cirra team ID or name that owns the Salesforce connection to use for this call. Must be provided together with 'sf_user'. Use it to run against a specific team's connection without changing your default team — e.g. to keep separate chats on Salesforce orgs in different teams. Omit to use your current/default team.",
+  "type": "string"
+}

1 tool updateJun 12, 2026
- Removedlogout
1 tool updateJun 12, 2026
- Addedlogout

1 tool updateMay 29, 2026

Changedcirra_ai_init1 field changed

changedInput schema / properties / cirra_ai_team / description

Previous value: -"(optional) The Cirra AI team to use. Use the literal value `__Personal__` to select the user's personal account. Omit this to use the previously selected default team (if any)."New value: +"(optional) The Cirra AI team to use. Use the literal value `__Personal__` to select the user's personal account (not allowed for team-only users). Omit this to use the previously selected default team (if any)."

1 tool updateMay 21, 2026

Changedsf_connection_manage1 field changed

changedInput schema / properties / action / description

Previous value: -"The action to perform. Options: 'list' (list all connections), 'describe' (provide details of the connection), 'add' (add a new connection), 'reauthenticate' (refresh auth for a connection), 'remove' (remove a connection)"New value: +"The action to perform. Options: 'list' (list all connections), 'describe' (provide details of the connection, including org info and current org limits such as data/file storage, daily API request usage, async job slots, etc.), 'add' (add a new connection), 'reauthenticate' (refresh auth for a connection), 'remove' (remove a connection)"

41 tool updatesMay 8, 2026
- Addedcirra_ai_init
- Removedcirra_ai_retry_connection
- Addedfetch_more
- Addedgroup_create
- Addedgroup_members
- Addedgroup_update
- Addedlink_build
- Addedmetadata_create
- Addedmetadata_delete
- Addedmetadata_describe
- Addedmetadata_list
- Addedmetadata_read
- Addedmetadata_update
- Addedpage_layout_clone
- Addedpage_layout_update
- Addedpermission_set_assignments
- Addedpermission_set_update
- Addedprofile_clone
- Addedprofile_describe
- Addedprofile_update
- Addedrecord_type_create
- Addedrecord_type_update
- Addedreport_run
- Addedsf_connection_manage
- Addedsobject_create
- Addedsobject_describe
- Addedsobject_dml
- Addedsobject_field_create
- Addedsobject_field_update
- Addedsobject_update
- Addedsobjects_list
- Addedsoql_query
- Addedtooling_api_describe
- Addedtooling_api_dml
- Addedtooling_api_query
- Addedtooling_api_search
- Addeduser_create
- Addeduser_describe
- Addeduser_update
- Addedvalue_set_create
- Addedvalue_set_update
41 tool updatesMay 8, 2026
- Removedcirra_ai_init
- Addedcirra_ai_retry_connection
- Removedfetch_more
- Removedgroup_create
- Removedgroup_members
- Removedgroup_update
- Removedlink_build
- Removedmetadata_create
- Removedmetadata_delete
- Removedmetadata_describe
- Removedmetadata_list
- Removedmetadata_read
- Removedmetadata_update
- Removedpage_layout_clone
- Removedpage_layout_update
- Removedpermission_set_assignments
- Removedpermission_set_update
- Removedprofile_clone
- Removedprofile_describe
- Removedprofile_update
- Removedrecord_type_create
- Removedrecord_type_update
- Removedreport_run
- Removedsf_connection_manage
- Removedsobject_create
- Removedsobject_describe
- Removedsobject_dml
- Removedsobject_field_create
- Removedsobject_field_update
- Removedsobject_update
- Removedsobjects_list
- Removedsoql_query
- Removedtooling_api_describe
- Removedtooling_api_dml
- Removedtooling_api_query
- Removedtooling_api_search
- Removeduser_create
- Removeduser_describe
- Removeduser_update
- Removedvalue_set_create
- Removedvalue_set_update

1 tool updateApr 11, 2026

Changedpage_layout_update3 fields changed

addedInput schema / properties / newLayoutName

Added value: +{
+  "description": "The new name for the layout. When provided, the layout will be renamed (via clone and delete). Can be combined with patch to rename and update in a single call",
+  "type": "string"
+}

changedInput schema / properties / patch / description

Previous value: -"The array of modifications that need to be applied. This should be provided in the `JSON Patch` format"New value: +"The array of modifications that need to be applied. This should be provided in the `JSON Patch` format. At least one of patch or newLayoutName must be provided"

changedInput schema / required

Previous value: -[
-  "layout",
-  "patch"
-]New value: +[
+  "layout"
+]

1 tool updateMar 23, 2026

Changedpermission_set_assignments1 field changed

removedInput schema / properties / pageSize

Removed value: -{
-  "description": "(optional) Maximum number of records to return per page when the response requires pagination. If omitted, page size is calculated automatically.",
-  "maximum": 9007199254740991,
-  "minimum": -9007199254740991,
-  "type": "integer"
-}

23 tool updatesMar 18, 2026

Changedfetch_more1 field changed

addedInput schema / properties / pageSize

Added value: +{
+  "description": "(optional) Number of records to return in this page. If omitted, uses the page size from the original query.",
+  "maximum": 9007199254740991,
+  "minimum": -9007199254740991,
+  "type": "integer"
+}

Addedgroup_members
Removedgroup_members_add
Removedgroup_members_list
Removedgroup_members_remove

Changedlink_build1 field changed

changedInput schema / properties / setupConfig / properties / type / enum

Previous value: -[
-  "Object",
-  "Field",
-  "Page Layout",
-  "Lightning Record Page",
-  "Button Link or Action",
-  "Link",
-  "Action",
-  "Record Type",
-  "Apex Trigger",
-  "Validation Rule",
-  "Value Set",
-  "Business Process",
-  "Flow Trigger",
-  "Permission Set",
-  "Profile",
-  "User",
-  "Flow",
-  "Class",
-  "Trigger",
-  "Group",
-  "Queue",
-  "Role",
-  "Email Template"
-]New value: +[
+  "Object",
+  "Field",
+  "Page Layout",
+  "Record Type",
+  "Apex Trigger",
+  "Validation Rule",
+  "Value Set",
+  "Business Process",
+  "Flow Trigger",
+  "Permission Set",
+  "Profile",
+  "User",
+  "Flow",
+  "Class",
+  "Trigger",
+  "Group",
+  "Queue",
+  "Role",
+  "Email Template",
+  "Report",
+  "Dashboard",
+  "Workflow Rule",
+  "Email Alert",
+  "Field Update",
+  "Outbound Message",
+  "Workflow Task"
+]

Changedmetadata_describe1 field changed

addedInput schema / properties / pageSize

Added value: +{
+  "description": "(optional) Maximum number of records to return per page when the response requires pagination. If omitted, page size is calculated automatically.",
+  "maximum": 9007199254740991,
+  "minimum": -9007199254740991,
+  "type": "integer"
+}

Changedmetadata_list1 field changed

addedInput schema / properties / pageSize

Added value: +{
+  "description": "(optional) Maximum number of records to return per page when the response requires pagination. If omitted, page size is calculated automatically.",
+  "maximum": 9007199254740991,
+  "minimum": -9007199254740991,
+  "type": "integer"
+}

Changedmetadata_read1 field changed

addedInput schema / properties / pageSize

Added value: +{
+  "description": "(optional) Maximum number of records to return per page when the response requires pagination. If omitted, page size is calculated automatically.",
+  "maximum": 9007199254740991,
+  "minimum": -9007199254740991,
+  "type": "integer"
+}

Removedpage_layout_create
Addedpermission_set_assignments
Removedpermission_set_assignments_add
Removedpermission_set_assignments_list
Removedpermission_set_assignments_remove
Removedpermission_set_create
Removedprofile_create

Changedreport_run1 field changed

addedInput schema / properties / pageSize

Added value: +{
+  "description": "(optional) Maximum number of records to return per page when the response requires pagination. If omitted, page size is calculated automatically.",
+  "maximum": 9007199254740991,
+  "minimum": -9007199254740991,
+  "type": "integer"
+}

Changedsobjects_list1 field changed

addedInput schema / properties / pageSize

Added value: +{
+  "description": "(optional) Maximum number of records to return per page when the response requires pagination. If omitted, page size is calculated automatically.",
+  "maximum": 9007199254740991,
+  "minimum": -9007199254740991,
+  "type": "integer"
+}

Changedsoql_query2 fields changed

addedInput schema / properties / havingClause

Added value: +{
+  "description": "HAVING clause to filter grouped results by aggregate conditions (e.g. 'COUNT(Id) > 5'). Requires groupBy to be set",
+  "type": "string"
+}

addedInput schema / properties / pageSize

Added value: +{
+  "description": "(optional) Maximum number of records to return per page when the response requires pagination. If omitted, page size is calculated automatically.",
+  "maximum": 9007199254740991,
+  "minimum": -9007199254740991,
+  "type": "integer"
+}

Changedtooling_api_describe1 field changed

addedInput schema / properties / pageSize

Added value: +{
+  "description": "(optional) Maximum number of records to return per page when the response requires pagination. If omitted, page size is calculated automatically.",
+  "maximum": 9007199254740991,
+  "minimum": -9007199254740991,
+  "type": "integer"
+}

Changedtooling_api_query1 field changed

addedInput schema / properties / pageSize

Added value: +{
+  "description": "(optional) Maximum number of records to return per page when the response requires pagination. If omitted, page size is calculated automatically.",
+  "maximum": 9007199254740991,
+  "minimum": -9007199254740991,
+  "type": "integer"
+}

Changedtooling_api_search1 field changed

addedInput schema / properties / pageSize

Added value: +{
+  "description": "(optional) Maximum number of records to return per page when the response requires pagination. If omitted, page size is calculated automatically.",
+  "maximum": 9007199254740991,
+  "minimum": -9007199254740991,
+  "type": "integer"
+}

Changedvalue_set_update2 fields changed

changedInput schema / properties / values / items / required

Previous value: -[
-  "fullName",
-  "default",
-  "label",
-  "isActive",
-  "converted",
-  "forecastCategory",
-  "probability",
-  "closed",
-  "won",
-  "description"
-]New value: +[
+  "fullName",
+  "default",
+  "label",
+  "isActive"
+]

changedInput schema / required

Previous value: -[
-  "name",
-  "namespace",
-  "type",
-  "values"
-]New value: +[
+  "name",
+  "values"
+]

2 tool updatesMar 13, 2026

Changedsoql_query2 fields changed

changedInput schema / properties / limit / default
```
Previous value: -100New value: +200
```

changedInput schema / properties / limit / description

Previous value: -"The maximum number of records to return. The default is 100. Note: LIMIT is automatically omitted for aggregate queries without GROUP BY."New value: +"The maximum number of records to return. The default is 200. Note: LIMIT is automatically omitted for aggregate queries without GROUP BY."

Changedtooling_api_query2 fields changed

changedInput schema / properties / limit / default
```
Previous value: -100New value: +200
```

changedInput schema / properties / limit / description

Previous value: -"The maximum number of records to return. The default is 100. Note: LIMIT is automatically omitted for aggregate queries without GROUP BY."New value: +"The maximum number of records to return. The default is 200. Note: LIMIT is automatically omitted for aggregate queries without GROUP BY."

5 tool updatesMar 11, 2026
- Addedfetch_more
- Changedmetadata_create1 field changed
  - changedInput schema / properties / metadata / items / additionalProperties
```
Previous value: -{}New value: +true
```
- Changedmetadata_list1 field changed
  - changedInput schema / required
```
Previous value: -[
-  "type",
-  "folder"
-]New value: +[
+  "type"
+]
```
- Changedmetadata_update1 field changed
  - changedInput schema / properties / metadata / items / additionalProperties
```
Previous value: -{}New value: +true
```
- Changedsobject_dml1 field changed
  - changedInput schema / properties / records / items / additionalProperties
```
Previous value: -{}New value: +true
```
1 tool updateMar 4, 2026
- Removedlogout
48 tool updatesFeb 26, 2026
- Addedcirra_ai_init
- Removedcirra_ai_retry_connection
- Addedgroup_create
- Addedgroup_members_add
- Addedgroup_members_list
- Addedgroup_members_remove
- Addedgroup_update
- Addedlink_build
- Addedlogout
- Addedmetadata_create
- Addedmetadata_delete
- Addedmetadata_describe
- Addedmetadata_list
- Addedmetadata_read
- Addedmetadata_update
- Addedpage_layout_clone
- Addedpage_layout_create
- Addedpage_layout_update
- Addedpermission_set_assignments_add
- Addedpermission_set_assignments_list
- Addedpermission_set_assignments_remove
- Addedpermission_set_create
- Addedpermission_set_update
- Addedprofile_clone
- Addedprofile_create
- Addedprofile_describe
- Addedprofile_update
- Addedrecord_type_create
- Addedrecord_type_update
- Addedreport_run
- Addedsf_connection_manage
- Addedsobject_create
- Addedsobject_describe
- Addedsobject_dml
- Addedsobject_field_create
- Addedsobject_field_update
- Addedsobject_update
- Addedsobjects_list
- Addedsoql_query
- Addedtooling_api_describe
- Addedtooling_api_dml
- Addedtooling_api_query
- Addedtooling_api_search
- Addeduser_create
- Addeduser_describe
- Addeduser_update
- Addedvalue_set_create
- Addedvalue_set_update
48 tool updatesFeb 26, 2026
- Removedcirra_ai_init
- Addedcirra_ai_retry_connection
- Removedgroup_create
- Removedgroup_members_add
- Removedgroup_members_list
- Removedgroup_members_remove
- Removedgroup_update
- Removedlink_build
- Removedlogout
- Removedmetadata_create
- Removedmetadata_delete
- Removedmetadata_describe
- Removedmetadata_list
- Removedmetadata_read
- Removedmetadata_update
- Removedpage_layout_clone
- Removedpage_layout_create
- Removedpage_layout_update
- Removedpermission_set_assignments_add
- Removedpermission_set_assignments_list
- Removedpermission_set_assignments_remove
- Removedpermission_set_create
- Removedpermission_set_update
- Removedprofile_clone
- Removedprofile_create
- Removedprofile_describe
- Removedprofile_update
- Removedrecord_type_create
- Removedrecord_type_update
- Removedreport_run
- Removedsf_connection_manage
- Removedsobject_create
- Removedsobject_describe
- Removedsobject_dml
- Removedsobject_field_create
- Removedsobject_field_update
- Removedsobject_update
- Removedsobjects_list
- Removedsoql_query
- Removedtooling_api_describe
- Removedtooling_api_dml
- Removedtooling_api_query
- Removedtooling_api_search
- Removeduser_create
- Removeduser_describe
- Removeduser_update
- Removedvalue_set_create
- Removedvalue_set_update
8 tool updatesFeb 20, 2026
- Changedgroup_create1 field changed
  - changedInput schema / properties / properties / additionalProperties
```
Previous value: -{}New value: +true
```
- Changedgroup_update1 field changed
  - changedInput schema / properties / properties / additionalProperties
```
Previous value: -{}New value: +true
```
- Changedsobject_create1 field changed
  - changedInput schema / additionalProperties
```
Previous value: -{}New value: +true
```
- Changedsobject_field_create1 field changed
  - changedInput schema / properties / properties / additionalProperties
```
Previous value: -{}New value: +true
```
- Changedsobject_field_update1 field changed
  - changedInput schema / properties / properties / additionalProperties
```
Previous value: -{}New value: +true
```
- Changedsobject_update1 field changed
  - changedInput schema / properties / properties / additionalProperties
```
Previous value: -{}New value: +true
```
- Changedtooling_api_dml1 field changed
  - changedInput schema / properties / record / additionalProperties
```
Previous value: -{}New value: +true
```
- Changeduser_update1 field changed
  - changedInput schema / properties / properties / additionalProperties
```
Previous value: -{}New value: +true
```

2 tool updatesFeb 15, 2026

Changedsoql_query3 fields changed

changedInput schema / properties / groupBy / description

Previous value: -"GROUP BY clause for aggregate queries. Required when using aggregate functions with grouping. Example: 'StageName' or 'AccountId, StageName'"New value: +"GROUP BY clause for aggregate queries. Required when using aggregate functions with grouping, optional otherwise"

changedInput schema / properties / orderBy / description

Previous value: -"ORDER BY clause. May include fields from related objects"New value: +"(optional) ORDER BY clause. May include fields from related objects"

changedInput schema / required

Previous value: -[
-  "sObject",
-  "fields",
-  "whereClause",
-  "orderBy",
-  "groupBy"
-]New value: +[
+  "sObject",
+  "fields",
+  "whereClause"
+]

Changedtooling_api_query3 fields changed

changedInput schema / properties / groupBy / description

Previous value: -"GROUP BY clause for aggregate queries. Required when using aggregate functions with grouping. Example: 'NamespacePrefix' or 'NamespacePrefix, TableEnumOrId'"New value: +"GROUP BY clause for aggregate queries. Required when using aggregate functions with grouping, optional otherwise"

changedInput schema / properties / orderBy / description

Previous value: -"ORDER BY clause"New value: +"(optional) ORDER BY clause"

changedInput schema / required

Previous value: -[
-  "sObject",
-  "fields",
-  "whereClause",
-  "orderBy",
-  "groupBy"
-]New value: +[
+  "sObject",
+  "fields",
+  "whereClause"
+]

Related MCP Connectors

agentic-opsOAuth
io.buildforce
Orchestration & technical-consulting MCP for end-to-end Salesforce, ServiceNow & HubSpot back-end.
CRM Customer Support App Automation
2
Support Agent Admin by Nova (CIVAI)C
co.civai.nova
I manage your Support Agent CRM, pipeline analytics, follow-ups, Leads Discovery, and workspace out…
CRM Customer Support
831
shopify-admin
com.mcparmory
Manage products, orders, customers, inventory, and store configuration
E-commerce & Retail CRM
2
MustertheForce MCPOAuth
com.mustertheforce
Salesforce-grounded retrieval, diagnoses, and a vetted-Force marketplace for MCP clients.
CRM RAG Systems
2

Related MCP Servers

Salesforce MCP Server
Databases ERP Systems Developer Tools
priyapanigrahy
A
license
Not graded
quality
D
maintenance
Integrates Claude with Salesforce to enable natural language querying, modification, and management of Salesforce records and metadata. It supports comprehensive operations including object/field management, SOSL searches, and Apex code execution.
Updated a year ago (2025-08-17 17:47 UTC)
1,582 npm
1
MIT
Salesforce MCP Server
Databases Developer Tools ERP Systems
JereSalguero30
A
license
A
quality
D
maintenance
Enables natural language interactions with Salesforce data and metadata, allowing users to query records, manage custom objects, and manipulate Apex code. It provides comprehensive tools for schema exploration, aggregate queries, and field-level security management.
Updated a year ago (2025-07-17 02:51 UTC)
15
1,582 npm
MIT
Salesforce MCP Server
Databases ERP Systems Developer Tools
dayal-arnav05
A
license
Not graded
quality
D
maintenance
Enables natural language interactions with Salesforce, allowing users to query and modify data, manage custom objects and fields, execute Apex code, and perform SOQL/SOSL searches across Salesforce organizations.
Updated a year ago (2025-10-27 04:55 UTC)
1,582 npm
MIT
MCP Salesforce Server
Databases Customer Data Platforms App Automation
AiondaDotCom
A
license
A
quality
C
maintenance
Enables AI assistants to interact with Salesforce through a secure interface for performing CRUD operations, executing SOQL queries, and managing schema discovery. It features a smart learning system that analyzes custom objects and fields to provide intelligent assistance tailored to specific Salesforce configurations.
Updated 6 months ago (2026-04-06 11:14 UTC)
14
50 npm
17
BSD 2-Clause "Simplified"

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?