Salesforce MCP UI Automation
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SALESFORCE_ORG_URL | Yes | The URL of your Salesforce org (e.g., https://your-domain.my.salesforce.com). Required. | |
| SALESFORCE_PROFILE | No | Browser profile name for persistent session. Default: default | default |
| SALESFORCE_HEADLESS | No | Run browser headless (true/false). Default: false | false |
| SALESFORCE_API_VERSION | No | Salesforce API version (e.g., 61.0). Default: 61.0 | 61.0 |
| SALESFORCE_ACCESS_TOKEN | No | Salesforce access token for API calls (optional if using browser session token or OAuth). | |
| SALESFORCE_INSTANCE_URL | No | The instance URL for API calls. Defaults to SALESFORCE_ORG_URL if not set. | |
| SALESFORCE_OAUTH_SCOPES | No | OAuth scopes. Default: api refresh_token | api refresh_token |
| SALESFORCE_OAUTH_CLIENT_ID | No | OAuth client ID for Connected App (required for OAuth token flow). | |
| SALESFORCE_DATACLOUD_API_URL | No | Data Cloud tenant URL for Query/Metadata API. | |
| SALESFORCE_OAUTH_REDIRECT_URI | No | OAuth redirect URI. Default: http://localhost:1717/oauth/callback | http://localhost:1717/oauth/callback |
| SALESFORCE_DATACLOUD_QUERY_URL | No | Legacy Data Cloud query URL (optional). | |
| SALESFORCE_OAUTH_CLIENT_SECRET | No | OAuth client secret for Connected App. | |
| SALESFORCE_JOURNAL_REDACT_FIELDS | No | Comma-separated list of field names to redact in journal logs. Default: token,password,secret,access_token,refresh_token,authorization | token,password,secret,access_token,refresh_token,authorization |
| SALESFORCE_DATACLOUD_ACCESS_TOKEN | No | Access token for Data Cloud API calls. | |
| SALESFORCE_DATACLOUD_INGESTION_URL | No | Data Cloud ingestion tenant URL. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| open_orgC | Open a Salesforce org URL with the persistent browser profile. |
| snapshotB | Return the current page state, visible text, optional screenshot, warnings, and next actions. |
| clickC | Click a visible element by text, CSS selector, or accessibility role. |
| fillC | Fill an input by label, CSS selector, or placeholder. |
| selectC | Select an option in a native select field by selector or label. |
| wait_forC | Wait for page stability, a selector, or visible text. |
| search_setupC | Open Salesforce Setup and search the Quick Find box. |
| open_datacloud_areaC | Search Setup for a known Data Cloud area such as Data Streams or Identity Resolution. |
| diagnose_datacloudA | Collect a Data Cloud-oriented diagnostic snapshot of the current page. |
| close_browserB | Close the persistent browser context for the current MCP server process. |
| browser_auth_statusA | Report masked browser/runtime authentication status for the active Playwright session. |
| use_browser_session_tokenA | Use the Salesforce sid cookie from Playwright as an in-memory API session token. |
| start_oauth_token_flowC | Start OAuth Authorization Code + PKCE in Playwright and store tokens in memory. |
| refresh_oauth_tokenB | Refresh the in-memory OAuth access token using the runtime refresh token. |
| clear_runtime_tokensA | Clear in-memory Salesforce and Data Cloud runtime tokens. |
| plan_requestC | Create a supervised execution plan and run journal for a user request. |
| list_capabilitiesA | List supported supervised Data Cloud workflow capabilities. |
| execute_planB | Execute a planned run until completion, failure, or approval is required. |
| get_run_statusC | Return the current run journal state. |
| approve_stepC | Approve one supervised run step. |
| rollback_runC | Prepare or execute rollback for resources tracked in a run journal. |
| query_salesforceC | Run a Salesforce SOQL query using configured OAuth access token environment variables. |
| query_datacloudC | Run a Data Cloud query against the configured Data Cloud query endpoint. |
| datacloud_submit_queryB | Submit a Data Cloud SQL query and return query metadata or a query id. |
| datacloud_query_statusC | Return status for a submitted Data Cloud SQL query. |
| datacloud_query_rowsB | Return paginated rows for a submitted Data Cloud SQL query. |
| datacloud_cancel_queryC | Cancel a submitted Data Cloud SQL query. |
| datacloud_metadataC | Retrieve Data Cloud metadata for DLOs, DMOs, Calculated Insights, fields, and relationships. |
| assert_recordsC | Validate records with count, contains, required field, freshness, and no-error checks. |
| compare_before_afterC | Compare before/after query evidence captured in a run journal. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Deviank88/Salesforce-MCP-UI-Automation'
If you have feedback or need assistance with the MCP directory API, please join our Discord server