Skip to main content
Glama
garland3

atlas-introspect-mcp

by garland3
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to atlas-introspect-mcp

No user-submitted related servers found.

    Related Servers

    • hermes-gpt

      n0geegee
      A
      license
      A
      quality
      D
      maintenance
      Enables MCP-based interaction with a local Hermes Agent installation, providing file read/search, skill management, and optional sandboxed write, terminal, and memory tools.
      9
      MIT

    • Codex Local Gateway

      sleda
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables ChatGPT Web or another MCP client to inspect and develop a local workspace, read local Codex task history, and use the complete installed XcodeBuildMCP catalog through a small set of stable tools.
      MIT

    • hermes-gpt

      DeployFaith
      A
      license
      C
      quality
      D
      maintenance
      MCP sidecar for Hermes Agent exposing operator tools (cron, skills, config, workspace) with tiered read-only/operator/owner modes and dry-run by default for safe local development.
      43
      1
      MIT

    • Atlas MCP Server

      good2idnan
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents and users to manage workspace files, monitor system metrics, take persistent notes, and retrieve weather data via MCP tools and resources.
      -
    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

    A3.9/5.0

    Scored across 21 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: conversations, workspaces, custom prompts, prompt files, and MCP config are cleanly separated. Even similar operations like search_conversations vs list_conversations are differentiated by their descriptions (search vs browse). No two tools appear to do the same thing.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (list_, get_, create_, update_, delete_, read_, write_, search_, upsert_, replace_) with snake_case throughout. Only 'atlas_status' deviates slightly, but it's a special health-check tool and still fits the imperative style.

    Tool Count4/5

    At 21 tools, the server is on the heavier side, but the scope (managing conversations, workspaces, prompts, prompt files, and MCP config) justifies the count. Each tool addresses a specific need, and there is no obvious duplication or bloat.

    Completeness4/5

    Workspaces, custom prompts, and MCP config all have full CRUD (or equivalent) coverage. Conversations lack create/delete, and tags are read-only, but those may be intentionally absent for an introspection tool. The ability to read and write prompt files covers the on-disk prompt management need. Minor gaps exist, but agents can work around them.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources