Skip to main content
Glama
Swit MCP Server

Swit MCP Server

by TykanN
  ░██████╗░██╗░░░░░░░██╗██╗████████╗  ███╗░░░███╗░█████╗░██████╗░
  ██╔════╝░██║░░██╗░░██║██║╚══██╔══╝  ████╗░████║██╔══██╗██╔══██╗
  ╚█████╗░░╚██╗████╗██╔╝██║░░░██║░░░  ██╔████╔██║██║░░╚═╝██████╔╝
  ░╚═══██╗░░████╔═████║░██║░░░██║░░░  ██║╚██╔╝██║██║░░██╗██╔═══╝░
  ██████╔╝░░╚██╔╝░╚██╔╝░██║░░░██║░░░  ██║░╚═╝░██║╚█████╔╝██║░░░░░
  ╚═════╝░░░░╚═╝░░░╚═╝░░╚═╝░░░╚═╝░░░  ╚═╝░░░░░╚═╝░╚════╝░╚═╝░░░░░

🚀 설정 가이드

1. Swit Developer Console 앱 등록

  1. https://developers.swit.io 에서 새 앱 생성

  2. 클라이언트 ID, 시크릿 발급

  3. 리다이렉트 URI: http://localhost:3000/callback 설정

2. MCP 클라이언트 설정

Claude Desktop

~/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"
      }
    }
  }
}

3. 인증 과정

  1. Claude Desktop에서 첫 Swit 도구 실행 시 OAuth 웹서버가 자동 시작

  2. swit-oauth-start 도구 실행하여 인증 URL 획득

  3. 브라우저에서 Swit 계정으로 로그인

  4. 토큰이 자동으로 저장되며 swit-oauth-status로 확인 가능

Related MCP server: MCP Google Suite

🛠️ 사용 가능한 도구

🔐 OAuth 관리

  • swit-oauth-status - OAuth 인증 상태 확인 및 토큰 정보 조회

  • swit-oauth-start - OAuth 인증 시작 (브라우저 인증 URL 반환)

💼 Swit API 연동

  • swit-workspace-list - 접근 가능한 워크스페이스 목록 조회

  • swit-channel-list - 지정된 워크스페이스의 채널 목록 조회 (필터링 지원)

  • swit-message-create - 채널에 새 메시지 전송 (텍스트/HTML 지원)

  • swit-message-comment-create - 기존 메시지에 댓글 작성

🎯 활용 예시: Claude에게 "Swit의 개발팀 채널에 프로젝트 진행 상황을 알려줘"라고 요청하면 자동으로 메시지를 전송할 수 있습니다.

기술 스택

  • MCP SDK: Model Context Protocol TypeScript SDK

  • OAuth: @swit-api/oauth 패키지 사용

  • Type Safety: Zod를 활용한 런타임 타입 검증

  • Web Server: OAuth 콜백 처리를 위한 Express 내장 웹서버

  • Testing: Jest + Nock을 활용한 HTTP mocking 테스트

Available Tools

9 tools
swit-channel-listC

Retrieve list of channels

Inputs: workspace_id (required), offset, limit, type, +3 more.

swit-message-comment-createC

Create comment on message

Inputs: message_id (required), content (required), body_type, assets, +1 more.

swit-message-comment-listC

Retrieve list of comments on message

Inputs: message_id (required), offset, limit.

swit-message-createC

Send message to channel

Inputs: channel_id (required), content, body_type, assets, +2 more.

swit-oauth-logoutA

Logout from OAuth authentication and delete stored tokens. Use when re-authentication is required.

Inputs: no named parameters.

swit-oauth-startA

Start OAuth authentication. Returns authentication URL that can be opened in browser.

Inputs: no named parameters.

swit-oauth-statusA

Check OAuth authentication status

Inputs: no named parameters.

swit-project-listC

Retrieve list of projects

Inputs: workspace_id (required), offset, limit, activity, +2 more.

swit-workspace-listC

Retrieve list of workspaces

Inputs: offset, limit, name.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.1/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool has a clear and distinct purpose: channel management, message operations (create, comment), OAuth flow (start, status, logout), and listing of projects and workspaces. There is no overlap in functionality.

    Naming Consistency4/5

    All tools use the 'swit-' prefix with snake_case. Most follow a noun-verb pattern (e.g., 'swit-channel-list', 'swit-project-list'), while some have compound nouns (e.g., 'swit-message-comment-create'). The pattern is mostly consistent but has minor deviations.

    Tool Count5/5

    With 9 tools covering channels, messages, comments, projects, workspaces, and OAuth, the count is appropriate for a collaboration server. Each tool serves a necessary function without redundancy.

    Completeness3/5

    The tool set includes list operations for channels, projects, and workspaces, as well as message creation and commenting. However, it lacks update/delete for messages and channels, and does not provide retrieval of individual messages or search functionality, leaving notable gaps.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server implementation that enables AI assistants to interact with Slack workspaces, allowing them to browse channels, send messages, reply to threads, add reactions, and retrieve user information.
      9
      65 npm
      2
      Apache 2.0
    • A
      license
      A
      quality
      D
      maintenance
      A Model Context Protocol server that provides seamless integration with Google Workspace, allowing operations with Google Drive, Docs, and Sheets through secure OAuth2 authentication.
      8
      38 PyPI
      3
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that runs on Cloudflare Workers with OAuth login, allowing AI assistants like Claude to execute tools remotely through HTTP connections.
      -
    • A
      license
      A
      quality
      B
      maintenance
      A server implementing Model Context Protocol that enables AI assistants to interact with Slack API through a standardized interface, providing tools for messaging, channel management, user information retrieval, and more.
      11
      109
      Apache 2.0