Salesforce Order Concierge

A Model Context Protocol (MCP) server that provides Salesforce order management capabilities for Claude Desktop, including order status checking, return creation, case management, and Slack notifications.

This MCP server enables Claude Desktop to interact with Salesforce for:

- Order status checkingwith shipping details and tracking information
- Return order creationusing standard Salesforce ReturnOrder objects
- Case management integrationfor customer service escalation
- Slack notification systemfor real-time alerts
- Return label email automationfor customer convenience
- check_order_status- Check order status, shipping details, and tracking information
- create_return- Create return orders using standard Salesforce objects
- email_return_label- Email return shipping labels to customers
- update_case_status- Update case status with priority and assignment changes
- create_case_from_return- Create support cases from return orders
- send_slack_alert- Send formatted alerts to Slack channels

2. Deploy Salesforce Metadata (Optional)

If you want to use the enhanced features:

# Authenticate to your Salesforce org sf org login web --alias MyOrg # Deploy custom fields and flows sf project deploy start --target-org MyOrg

Add to your Claude Desktopclaude_desktop_config.json:

{ "mcpServers": { "salesforce-order-concierge": { "command": "node", "args": ["dist/index.js"], "cwd": "/path/to/sf_mcp_oc", "env": { "SF_LOGIN_URL": "https://login.salesforce.com", "SF_USERNAME": "your-salesforce-username@example.com", "SF_PASSWORD": "your-salesforce-password", "SF_SECURITY_TOKEN": "your-salesforce-security-token", "SLACK_WEBHOOK_URL": "your-slack-webhook-url-optional" } } } }

After adding the configuration, restart Claude Desktop to load the MCP server.

The MCP Inspector is a powerful tool for testing and debugging MCP servers. Here's how to use it:

- Server Command:node
- Arguments:["dist/index.js"]
- Working Directory:/path/to/sf_mcp_oc
- Environment Variables:

SF_LOGIN_URL=https://login.salesforce.com SF_USERNAME=your-username@example.com SF_PASSWORD=your-password SF_SECURITY_TOKEN=your-token SLACK_WEBHOOK_URL=your-webhook-url

- Click "Connect" to establish connection
- Browse available tools in the left panel
- Test each tool with sample data
- View requests/responses in real-time

{ "orderId": "00000100" }

{ "orderId": "801xx0000000001", "lineItemId": "802xx0000000001", "reason": "Defective", "quantity": 1, "description": "Product stopped working" }

{ "message": "Test alert from MCP Inspector", "priority": "info" }

- Connection Issues:Check environment variables and Salesforce credentials
- Tool Failures:Review error messages in the inspector's response panel
- Permissions:Ensure your Salesforce user has access to required objects
- Network:Verify Salesforce and Slack connectivity

- Salesforce org with Service Cloud or Field Service license
- Order Management enabled
- API access for the configured user
- Standard objects: Order, OrderItem, ReturnOrder, ReturnOrderLineItem, Case

- Node.js 18+ installed
- Salesforce CLI (optional, for metadata deployment)
- Claude Desktop application

- ReturnOrder- Standard Salesforce object for return management
- ReturnOrderLineItem- Individual return items
- Case- Customer service integration
- Order/OrderItem- Order relationships

- ReturnOrder.LabelEmailSent__c- Tracks if return label was emailed
- ReturnOrder.LabelEmailSentDate__c- Email timestamp
-

"Server disconnected while setting up"

# Check if server builds successfully npm run build # Verify file permissions chmod +x dist/index.js # Test server startup node dist/index.js

- Verify Salesforce credentials
- Check security token (get new one from Setup → My Personal Information)
- Use correct login URL for your org type

- Ensure Service Cloud license is active
- Enable Order Management in Setup → Sales → Order Settings
- Verify user has access to ReturnOrder objects

- Test with MCP Inspector to see detailed error messages
- Check Salesforce debug logs
- Verify required fields are populated

- Use MCP Inspector for detailed debugging
- Check Claude Desktop logs for connection issues
- Review Salesforce debug logs for API errors
- Test Salesforce connectivity with simple SOQL queries

sf_mcp_oc/ ├── src/ │ ├── index.ts # Main MCP server │ ├── salesforce-client.ts # Salesforce API client │ └── types.ts # TypeScript schemas ├── force-app/main/default/ # Salesforce metadata │ ├── objects/ReturnOrder/ # Custom fields │ └── flows/ # Automation flows ├── dist/ # Compiled JavaScript ├── package.json # Node.js dependencies ├── tsconfig.json # TypeScript config └── CLAUDE.md # Project instructions

- Never commit credentials to version control
- Use environment variables for all sensitive data
- Rotate Salesforce security tokens regularly
- Use dedicated API users with minimal required permissions

MIT License - see LICENSE file for details.

- Model Context Protocol Documentation
- MCP Inspector
- Claude Desktop Documentation
- Salesforce ReturnOrder Documentation

The Feedspace MCP server lets AI assistants read, manage, and display your reviews and testimonials through natural language. Instead of navigating dashboards, simply ask your AI assistant to filter reviews, create widgets, build Wall of Love pages, and more