Skip to main content
Glama
alexpriest

swarm-mcp

by alexpriest
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to swarm-mcp

No user-submitted related servers found.

    Related Servers

    • mcp-foursquare

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Foursquare Places MCP server enabling AI agents to search and retrieve venue data via the 2025 Places API through the Pipeworx gateway.
      168 npm
      MIT

    • BeeMCP

      OkGoDoIt
      A
      license
      Not graded
      quality
      D
      maintenance
      Unofficial MCP server that bridges AI assistants with Bee wearable lifelogging data, enabling retrieval and management of conversations, facts, todos, and locations.
      49
      MIT
    • PinMeTo Location MCP by PinMeTo

      PinMeTo Location MCPofficial

      PinMeTo
      A
      license
      A
      quality
      A
      maintenance
      An MCP server that connects your PinMeTo locations to AI assistants, enabling natural language queries for insights from Google, Facebook, and Apple Maps.
      12
      15
      MIT

    • google-activity-assistant

      Daemon-Killer
      A
      license
      A
      quality
      B
      maintenance
      MCP server for querying your local Google Takeout activity (Search/YouTube history) via SQLite/FTS5. Provides tools for keyword search, activity stats, and database info, enabling AI assistants to cite your personal history.
      3
      MIT

    • RewindMCP

      pedramamini
      F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that interfaces with the Rewind.ai SQLite database to provide access to audio transcripts, screen OCR data, and activity tracking. It enables AI models to search personal memory, retrieve past conversations, and analyze application usage history.
      19
      -
    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

    A4/5.0

    Scored across 11 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: get_all_checkins vs get_checkins differ in pagination cost, get_checkins_by_date_range vs get_recent_checkins target different time ranges, and others cover categories, stats, venues, and server info. Descriptions explicitly clarify overlaps.

    Naming Consistency5/5

    All tool names follow a consistent get_verb_noun pattern in snake_case (e.g., get_all_checkins, get_categories, get_checkin_stats). No mixing of naming conventions, making it easy to infer function.

    Tool Count5/5

    With 11 tools, the server covers all major retrieval needs for check-in history and venue data without being bloated. The count is well-scoped for a focused analytics domain.

    Completeness4/5

    The server provides comprehensive read access: full history, filtered, stats, categories, top venues, and venue details. Missing write/update tools aligns with use case. A minor gap is no direct tool to list check-ins for a specific venue, but search_checkins can approximate this.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources