mcp-sling
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mcp-sling Show me today's schedule for all users."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP Sling Server
Model Context Protocol (MCP) server for the Sling API - a comprehensive scheduling and workforce management platform.
Quick Start: New to this? See QUICK_START.md for a 5-minute setup guide!
Features
This MCP server provides tools to interact with all major Sling API endpoints:
Calendar & Scheduling
get_calendar - Retrieve calendar and shift data for users
create_shift - Create new shifts for employees
get_timesheets - View timesheet data and actual hours worked
update_timesheet - Modify timesheet entries
User Management
get_users - List all users in your organization
create_user - Add new users
update_user - Modify user information
Organization Management
get_organization - View organization details
get_organization_by_id - Get specific organization info
switch_organization - Switch between organizations
get_groups - List organizational groups
Reporting & Analytics
get_reports - Access various reports (labor, schedule, attendance)
create_sales_record - Record sales data for analytics
get_tags - Retrieve available tags for categorization
Settings
update_settings - Modify organization or user settings
Advanced
sling_api_call - Make custom API calls to any Sling endpoint
Related MCP server: Officient MCP Server
Installation
Clone this repository:
git clone <repository-url>
cd mcp-slingInstall dependencies:
npm installBuild the project:
npm run buildGet your Sling authorization token:
IMPORTANT: Due to CAPTCHA requirements on the Sling login endpoint, you need to obtain your authorization token from your browser.
Follow the detailed guide: TOKEN_GUIDE.md
Create a
.envfile with your token:
cp .env.example .envEdit .env and add your token:
SLING_TOKEN=your-token-from-browser
SLING_SERVER=apiConfiguration
Environment Variables
Recommended approach (avoids CAPTCHA):
SLING_TOKEN (required) - Your Sling authorization token from browser
See TOKEN_GUIDE.md for instructions
SLING_SERVER (optional) - API server to use (default: "api", use "test-api" for staging)
Alternative (requires CAPTCHA - not recommended):
SLING_EMAIL - Your Sling account email
SLING_PASSWORD - Your Sling account password
Note: Currently not working due to CAPTCHA requirement on
/account/loginendpoint
Claude Desktop Configuration
Add this to your Claude Desktop configuration file:
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%/Claude/claude_desktop_config.json
Recommended: Using token
{
"mcpServers": {
"sling": {
"command": "node",
"args": ["/absolute/path/to/mcp-sling/dist/index.js"],
"env": {
"SLING_TOKEN": "your-token-from-browser"
}
}
}
}Alternative: Using .env file
{
"mcpServers": {
"sling": {
"command": "node",
"args": ["/absolute/path/to/mcp-sling/dist/index.js"]
}
}
}(Requires .env file with SLING_TOKEN configured)
Usage Examples
Once configured, you can use the Sling tools through Claude. Here are some example queries:
Get All Users
Can you get the list of all users in my Sling organization?View Calendar
Show me the calendar for user ID 12345 in organization 67890 for dates 2024-01-15Create a Shift
Create a shift for user 12345 starting at 2024-01-20T09:00:00Z and ending at 2024-01-20T17:00:00Z for the "Cashier" positionGet Reports
Get the labor report for the period from 2024-01-01 to 2024-01-31Custom API Call
Make a GET request to /custom/endpoint with params {"filter": "active"}Authentication
This server handles authentication automatically using your configured credentials. The authentication flow:
On first request, the server logs in to Sling using your email/password
The authentication token is cached and reused for subsequent requests
If a token expires (401 error), the server automatically refreshes it
Tokens are typically valid for 1 hour
Note: The Sling API uses email/password authentication as documented in their official examples.
About CAPTCHA
Important Update: As of November 2024, Sling has added CAPTCHA protection to the /account/login API endpoint. This means direct email/password authentication no longer works without solving a CAPTCHA challenge.
Solution: Use a pre-obtained authorization token from your browser instead. See TOKEN_GUIDE.md for detailed instructions.
Why this approach works:
Tokens obtained from browser sessions don't require CAPTCHA
Tokens typically remain valid for weeks or months
You only need to get a new token when it expires or you change your password
This is the recommended approach until Sling provides an alternative API authentication method
API Documentation
For detailed information about the Sling API endpoints and data formats, refer to:
Development
Build
npm run buildWatch Mode
npm run watchRun Development Server
npm run devTest Authentication
To verify your credentials work before using with Claude:
node test-auth.jsThis will attempt to authenticate and show detailed debug information.
Permissions
Your API access level matches your Sling user permissions:
Admin tokens - Full access to all organization data
Employee tokens - Limited to that user's information only
Troubleshooting
"No authorization token received from Sling API"
The server now includes detailed debug logging. Check your MCP server logs (Claude Desktop Developer Console) for:
Response status code
Response headers
Response body
This will help identify where the token should be.
Quick fixes:
Verify credentials in
.envare correct (no extra quotes/spaces)Test login with curl:
curl -i -X POST https://api.getsling.com/account/login \ -H "Content-Type: application/json" \ -d '{"email":"your@email.com","password":"password"}'Look for
authorization:header in the response
For detailed troubleshooting steps, see TROUBLESHOOTING.md
Authentication Issues
Verify your email and password are correct in
.envCheck that you can log in to Sling web app with these credentials
Ensure you're using the correct server (api vs test-api)
Make sure you're not using OAuth provider credentials (Google/Facebook)
API Errors
Check the error message for specific details
Verify your user has permission to access the requested resource
Ensure date formats are in ISO 8601 format (e.g., "2024-01-20T09:00:00Z")
Connection Issues
Verify you have internet connectivity
Check if api.getsling.com is accessible
Try using SLING_SERVER=test-api for the staging environment
Debugging
The server logs detailed authentication information to stderr:
All response headers from Sling API
Response body content
Token extraction attempts
View these logs in:
Claude Desktop: Help → Developer Tools → Console
Terminal: stderr output from the MCP server process
License
MIT
Contributing
Contributions are welcome! Please feel free to submit a Pull Request.
Support
For issues with:
This MCP server: Open an issue in this repository
Sling API: Refer to Sling API documentation
MCP Protocol: See MCP documentation
Available Tools
16 toolscreate_sales_recordC
Create a sales record. Used for tracking sales data and labor analytics.
Inputs: date (required), amount (required), location, data.
create_shiftB
Create a new shift for a user. Shifts represent scheduled work periods.
Inputs: userId (required), startTime (required), endTime (required), position, +2 more.
create_userB
Create a new user in the organization.
Inputs: email (required), name (required), role, data.
get_calendarB
Get calendar information for a specific user in an organization. Returns schedule and shift data for the specified date range.
Inputs: org (required), user (required), dates (required).
get_groupsA
Get list of groups in the organization. Groups are used to organize users.
Inputs: no named parameters.
get_organizationB
Get organization information. Returns details about your organization.
Inputs: no named parameters.
get_organization_by_idB
Get organization information by specific organization ID.
Inputs: orgId (required).
get_reportsC
Get reports data. Reports provide analytics and insights about schedules, labor costs, etc.
Inputs: reportType, startDate, endDate, params.
get_tagsA
Get list of available tags. Tags are used to categorize and organize shifts, users, etc.
Inputs: no named parameters.
get_timesheetsC
Get timesheet data. Timesheets track actual hours worked.
Inputs: startDate, endDate, userId.
get_usersA
Get list of users in the organization. Returns user information based on your access level.
Inputs: no named parameters.
sling_api_callA
Make a custom API call to any Sling endpoint. Use this for endpoints not covered by specific tools.
Inputs: method (required), path (required), params, data.
switch_organizationC
Switch to a different organization context.
Inputs: orgId (required).
update_settingsC
Update organization or user settings.
Inputs: settingType (required), data (required).
update_timesheetC
Update timesheet data for a user.
Inputs: timesheetId (required), data (required).
update_userB
Update an existing user in the organization.
Inputs: userId (required), data (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 16 tools
Most tools have distinct purposes (e.g., create_shift, get_timesheets, update_user), but two organization retrieval tools (get_organization, get_organization_by_id) overlap slightly, and the generic sling_api_call could be confused with specific tools. Overall, the set is well-disambiguated.
All tools follow a consistent verb_noun pattern in snake_case (e.g., create_shift, get_users, update_timesheet). The only exception is sling_api_call, which still uses a noun_noun structure but is clearly named. The pattern is uniform and predictable.
With 16 tools, the count is slightly above the ideal 3-15 range but still appropriate for the domain. Each tool covers a distinct function (users, shifts, timesheets, settings, etc.), and no tool feels redundant.
The tool set covers core CRUD operations for users, shifts, timesheets, organizations, and settings, plus reporting and a generic API call. Missing delete operations and shift updates are minor gaps, but the generic API call mitigates them. Coverage is good for common workflows.
Related MCP Connectors
Check shifts, time clock entries, time-off requests, swaps and availability, and manage shifts.
Connects AI assistants to TrackingTime for querying time entries, projects, tasks, customers, and team data using natural language.
Manage projects, tasks, time tracking, and team collaboration through natural language.
Read Connecteam users, shifts, time clock, jobs, time off, tasks and forms; create shifts and tasks.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceIntegrates Tanda Workforce API with AI assistants to manage employee schedules, timesheets, leave requests, clock in/out operations, and workforce analytics through natural language with OAuth2 authentication.2MIT
- AlicenseBqualityDmaintenanceEnables interaction with the Officient HR API to manage people, days off, and salary slips through natural language.9MIT
- AlicenseNot gradedqualityDmaintenanceProvides 50+ tools for interacting with Rippling's HR platform, including employee management, payroll, time tracking, benefits, recruiting, learning, devices, groups, and custom objects, all through natural language.MIT
- AlicenseCqualityDmaintenanceEnables natural language interaction with UKG Pro Workforce Management APIs. It detects intent, resolves missing inputs, hydrates related objects, and returns complete, validated operational answers across scheduling, timekeeping, attendance, and more.1ISC