MCP Server for Squadcast
About
MCP Server for Squadcast is a basic Model Context Protocol server that provides tools to interact with Squadcast, an incident management platform. It is intended for personal use only.
Details
- Author
- DEEJ4Y
- Downloads
- 157
- Categories
- Other
Jump to
- Authenticate with OAuth using a refresh token
- List and select teams
- Check who is on call
- Get, acknowledge, and resolve incidents
- Update status pages
- Create schedules
Clone the repository, install dependencies with npm install, rebuild TypeScript with npm rebuild typescript, then run the dev server with npm run dev. Configure your OAuth refresh token in config.json. Connect your MCP client (e.g., Claude Desktop) to the built dist/index.js file.
MCP Server for Squadcast
This is a basic MCP Server for Squadcast. It is intended for personal use only.
Video Demo
Available tools:
- Authenticate with OAuth (Configure your refresh token in config.json.)
- List Teams
- Select Team
- Who is on call?
- Get Incidents
- Acknowledge Incidents
- Resolve Incidents
- Update Status Page
- Create Schedules
Installation - For local development
Build using NodeJS v20.19.0
1. Clone the repository
2. Install dependencies
npm install
3. Rebuild Typescript dependencies
npm rebuild typescript
4. Run the dev server
npm run dev
Build files (MCP Server) will be in the ./dist directory. You can use this to connect to your MCP Client.
Connecting with Claude Desktop
Refer to the "Testing your server with Claude for Desktop" to set up a local server with Claude Desktop. Point it to the dist/index.js file on your computer.
Configuration
I used the following personal preferences for Claude Desktop. Replace Your Team Name in the template:
Help me with using Squadcast.
Ensure I am authenticated before using tools.
Once authenticated, ensure a team is selected. Select <Your Team Name Here> Team by default.
Once a team is selected, answer questions related to the selected team only.
If searching for incidents, don't use periods of more than 1 day. To get the latest incidents, you can use a future end date/time
When greeted, check for any triggered incidents and let the user know. Also remind the user of any acknowledged incidents (not been resolved yet.)
When creating resources, guide the user through the options they have and request for their inputs or confirmations before creation.
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.



