Skip to main content
Glama
TykanN

Swit MCP Server

by TykanN
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Swit MCP Server

No user-submitted related servers found.

    Related Servers

    • Slack MCP Server

      miyatsuki
      F
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that enables LLMs to interact with Slack workspaces through OAuth 2.0 authentication. It provides tools for listing channels and posting messages while supporting secure token persistence and dynamic client registration.
      -

    • MCP Google Suite

      adexltd
      A
      license
      A
      quality
      C
      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
      52 PyPI
      3
      MIT

    • MCP Server for Slack

      z9905080
      A
      license
      B
      quality
      C
      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
      7 npm
      2
      Apache 2.0

    • Slack MCP Server

      ubie-oss
      A
      license
      A
      quality
      C
      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
      110
      Apache 2.0

    • Remote MCP Server on

      Laity624
      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.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    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 issues

    Resources