Salesforce Headless 360 MCP server gives AI agents the connecting user's access
Start here
Salesforce's Headless 360 MCP server lets an AI agent act inside a Salesforce org as the user who connected it, inheriting that user's object permissions, field-level security, sharing rules and permission sets; the audit trail attributes every action to that user. Four tools — discover, describe, dispatch and dispatch_readonly — carry an intent through to an executed API call, and discover returns ranked candidates at runtime rather than a fixed list. The server is off by default org-wide and must be activated by an admin under Setup > MCP Servers, and it requires an External Client App with the mcp_api scope. By default, any user in the org can authenticate through that app, and refresh tokens remain valid indefinitely. The server is a Beta Service. Because the reachable surface depends on the connecting user's existing permissions, it cannot be fully listed before the server is turned on; the practical question is whether an admin activated it, and when.
Generated from reports · updated 41 min ago
Report timeline
Follow the reports to see the event from different sides.
- Hacker News · AIWhat an AI Agent Can Reach Through Salesforce's Headless 360 MCP Server
Salesforce's Headless 360 MCP server lets an AI agent act inside an org as the user who connected it, inheriting that user's object permissions, field-level security, sharing rules and permission sets, with the audit trail attributing every action to that user. Four tools — discover, describe, dispatch and dispatch_readonly — carry an intent through to an executed API call, and discover returns ranked candidates at runtime rather than a fixed list. The server is off until an admin activates it under Setup > MCP Servers and requires an External Client App with the mcp_api scope.
Heat for this event
Not enough continuous observations yet to draw a trend.