- Home
- MCP servers
- Swit MCP( Model Context Protocol ) Server
Swit MCP( Model Context Protocol ) Server
- typescript
0
GitHub Stars
typescript
Language
7 months ago
First Indexed
3 months ago
Catalog Refreshed
Documentation & install
Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.
Installation
Add the following to your MCP client configuration file.
Configuration
View docs{
"mcpServers": {
"tykann-swit-mcp": {
"command": "npx",
"args": [
"-y",
"swit-mcp"
],
"env": {
"SWIT_CLIENT_ID": "YOUR_CLIENT_ID",
"SWIT_CLIENT_SECRET": "YOUR_CLIENT_SECRET"
}
}
}
}You can run a Swit MCP Server to connect Claude with Swit for OAuth-based workspace actions and messaging. This server lets you manage OAuth tokens, list workspaces and channels, and post messages or comments through a standardized MCP interface.
How to use
You operate this MCP server from your MCP client (for example, Claude Desktop) by starting the MCP process and using the tool set to manage OAuth and Swit API actions. Begin with authenticating your Swit account, then use the available commands to list workspaces, fetch channels, and create messages or comments in channels you specify. The workflow is designed to let Claude issue natural language requests that map to these MCP actions.
How to install
Prerequisites: you need Node.js and npm installed on your system.
-
Ensure Node.js and npm are installed. You can verify with
node -vandnpm -v. -
Create the Swit MCP client configuration file for Claude Desktop. On macOS, place the following in the path
~/Library/Application Support/Claude/claude_desktop_config.json.
{
"mcpServers": {
"swit": {
"command": "npx",
"args": ["-y", "swit-mcp"],
"env": {
"SWIT_CLIENT_ID": "your-client-id",
"SWIT_CLIENT_SECRET": "your-client-secret"
}
}
}
}
Additional setup and security
This server uses OAuth to authorize access to Swit on behalf of your workspace. You will configure a client ID and client secret in the Swit Developer Console, and you will specify a redirect URI for the OAuth flow. The OAuth process is initiated by the tool swit-oauth-start, and you can check token status with swit-oauth-status.
Environment variables and credentials are stored securely by the MCP client. Keep your SWIT_CLIENT_ID and SWIT_CLIENT_SECRET confidential and rotate them periodically according to your security policy.
Configuration snippet (MCP server config)
{
"mcpServers": {
"swit": {
"command": "npx",
"args": ["-y", "swit-mcp"],
"env": {
"SWIT_CLIENT_ID": "your-client-id",
"SWIT_CLIENT_SECRET": "your-client-secret"
}
}
}
}
Available tools
swit-oauth-status
Checks OAuth authentication status and retrieves token information for the Swit MCP integration.
swit-oauth-start
Initiates OAuth authentication, returning a browser URL to complete sign-in.
swit-workspace-list
Lists accessible Swit workspaces for the authenticated account.
swit-channel-list
Lists channels within a specified workspace, with optional filtering.
swit-message-create
Sends a new message to a specified channel (supports text/HTML content).
swit-message-comment-create
Adds a comment to an existing message in a channel.