check_order_statusLABSCO SUMMARY
The whole return path, in one conversation instead of five tabs.
Checking the order, cutting the return, mailing the label, raising the case and telling the team are five screens in Salesforce and Slack. Here they are five calls an agent can make in order, on standard objects rather than a custom returns model.
What it is
A Node server over a Salesforce org, shaped around one job: the return desk. It reads order and shipping status, creates a standard Salesforce ReturnOrder, emails the label, opens or updates the support case, and posts a Slack alert.
What you get
- Order status with shipping details and tracking information
- Return orders created as standard Salesforce ReturnOrder records
- Return shipping labels emailed to the customer
- Support cases opened from a return, and existing cases updated with new priority or assignment
- Formatted alerts posted to a Slack channel
Requirements
A Salesforce login: SF_LOGIN_URL, SF_USERNAME, SF_PASSWORD and SF_SECURITY_TOKEN in the client config, plus SLACK_WEBHOOK_URL if you want the alerts. Built with npm install and npm run build. Custom fields and flows ship as optional Salesforce metadata you can deploy with the sf CLI.
Setup effort
Build from source — git clone https://github.com/gellasangameshgupta/sf_mcp_oc.git
USE CASES
01
Telling a customer where their order is
Read the order's status, shipping detail and tracking in one call, so the answer comes back with the tracking number already attached.
02
Starting a return while the customer is still on the line
Create the ReturnOrder against the order, then send the shipping label to their inbox without opening the label tool.
03
Escalating a return that needs a human
Open a support case from the return record, so the case carries the return it came from rather than a pasted summary.
04
Keeping a queue moving
Change a case's status, priority or owner from the conversation, and post the change to the channel that watches it.
6 tools
Listed in project docs. Your client may show a different list.
create_returnemail_return_labelupdate_case_statuscreate_case_from_returnsend_slack_alertBEFORE YOU INSTALL
What to know first
Tools you get
6 tools named in the project's documentation.
Requires
- node on PATH
- Node.js 18+
- SF_USERNAME in your environment
- SF_PASSWORD in your environment
- SF_SECURITY_TOKEN in your environment
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
You clone and build this one yourself.
Server setup
TERMINAL
git clone https://github.com/gellasangameshgupta/sf_mcp_oc.git
cd sf_mcp_oc
npm install
npm run buildMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"salesforce-order-concierge": {
"command": "node",
"args": [
"<YOUR_PATH_TO_SF_MCP_OC>/dist/index.js"
],
"env": {
"SF_LOGIN_URL": "https://login.salesforce.com",
"SF_USERNAME": "<YOUR_SF_USERNAME>",
"SF_PASSWORD": "<YOUR_SF_PASSWORD>",
"SF_SECURITY_TOKEN": "<YOUR_SF_SECURITY_TOKEN>",
"SLACK_WEBHOOK_URL": "<YOUR_SLACK_WEBHOOK_URL>"
}
}
}
}<YOUR_PATH_TO_SF_MCP_OC> is the absolute path of your clone. SF_LOGIN_URL is https://test.salesforce.com for a sandbox, and <YOUR_SF_SECURITY_TOKEN> is under Setup → My Personal Information. SLACK_WEBHOOK_URL is optional — drop the line if you do not want Slack alerts.
