Skip to main content
Glama

Related Servers

Alternatives to omni-mcp-server

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      A unified MCP server with composable tools for GitHub operations, file management, shell execution, kanban boards, Discord messaging, and package management. Features role-based security, HTTP/stdio transports, and a web-based development UI.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      A secure, git-aware MCP server for working with local repositories, enabling file management, shell commands, and full git operations within allowed directories.
      146 npm
      1
      GPL 3.0
    • F
      license
      Not graded
      quality
      C
      maintenance
      A production-ready MCP server providing 8 tools for file operations, shell command execution, web search and fetching, plus AI-powered code review and text summarization, with built-in security controls.
      -
    • A
      license
      Not graded
      quality
      A
      maintenance
      This self-hosted MCP server connects an MCP client such as ChatGPT to approved local project folders, enabling file reading and editing, code search, shell command execution, and Git worktree workflows without uploading code to a third party. It also supports mounting external stdio or Streamable HTTP MCP servers as dynamic capabilities.
      1,521 npm
      MIT
    • F
      license
      B
      quality
      D
      maintenance
      A config-driven, zero-dependency MCP server with plugin architecture that enables filesystem operations, shell commands, HTTP requests, and utilities through simple JSON configuration.
      3
      1
      -

    TDQS

    B3.4/5.0

    Scored across 13 tools

    Disambiguation5/5

    Each tool has a unique domain prefix (github_, slack_, system_, web_, memory_, git_) and a distinct action, making it clear which tool to use for a given task. There is no overlap in functionality between tools from different domains.

    Naming Consistency3/5

    Most tools follow a <domain>_<verb> or <domain>_<verb>_<object> pattern (e.g., github_search_repos, slack_send_message), but git tools use nouns (git_status, git_diff, git_log) instead of verbs, breaking the consistency. Memory tools also use verbs without objects (memory_store) rather than verb_noun.

    Tool Count4/5

    With 13 tools covering 6 different domains, the count is reasonable for an omnibus server. It provides a focused set of utilities without overwhelming the user, though some domains could benefit from a few more tools.

    Completeness2/5

    Each domain has significant gaps: GitHub only offers search and get issue (no create/update/delete), Slack only send message (no read/list), system only read and list dir (no write/delete), and git lacks add, push, pull, and branch operations. This can cause agent failures when users request common operations.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive