Swit MCP

🚀 Swit MCP( Model Context Protocol ) Server

Swit MCP Server is a server based on the Model Context Protocol, which enables seamless integration and interaction with Swit applications, providing users with a convenient way to manage OAuth authentication and access Swit APIs.

🚀 Quick Start

1. Register a new app in the Swit Developer Console

1. Create a new app at https://developers.swit.io.
2. Obtain the client ID and secret.
3. Set the redirect URI to http://localhost:3000/callback.

2. Configure the MCP client

Claude Desktop

Edit the ~/Library/Application Support/Claude/claude_desktop_config.json file as follows:

{
  "mcpServers": {
    "swit": {
      "command": "npx",
      "args": ["-y", "swit-mcp"],
      "env": {
        "SWIT_CLIENT_ID": "your-client-id",
        "SWIT_CLIENT_SECRET": "your-client-secret"
      }
    }
  }
}

3. Authentication process

1. When you run the first Swit tool in Claude Desktop, the OAuth web server will start automatically.
2. Run the swit-oauth-start tool to get the authentication URL.
3. Log in with your Swit account in the browser.
4. The token will be saved automatically, and you can check it using the swit-oauth-status tool.

✨ Features

🔐 OAuth Management

• swit-oauth-status: Check the OAuth authentication status and view token information.
• swit-oauth-start: Start the OAuth authentication process (returns the browser authentication URL).

💼 Swit API Integration

• swit-workspace-list: List accessible workspaces.
• swit-channel-list: List channels in a specified workspace (supports filtering).
• swit-message-create: Send a new message to a channel (supports text/HTML).
• swit-message-comment-create: Add a comment to an existing message.

💡 Usage Tip

You can ask Claude to "Inform the Swit development team channel about the project progress", and it will automatically send the message.

🔧 Technical Details

• MCP SDK: Model Context Protocol TypeScript SDK
• OAuth: Uses the @swit-api/oauth package.
• Type Safety: Performs runtime type validation using Zod.
• Web Server: Built - in Express web server for OAuth callback handling.
• Testing: Conducts HTTP mocking tests using Jest + Nock.