Skip to main content
Glama
lukebmandel-debug

Alto Connector

by lukebmandel-debug
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Related Servers

Alternatives to Alto Connector

No user-submitted related servers found.

    Related Servers

    • brain

      Lautaro005
      A
      license
      A
      quality
      C
      maintenance
      Runs locally on your Mac to give AI agents a shared, private memory of your profile, notes, projects, and saved web pages, with semantic search and version history.
      14
      MIT

    • Rhylthyme MCP Server

      rhylthyme
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables the creation of interactive schedule visualizations on rhylthyme.com featuring parallel tracks, dependencies, and resource constraints. Users can import recipes or protocols from external sources and define custom workspace environments to generate shareable timelines with live execution timers.
      Apache 2.0

    • Sutrana

      sdntsng
      A
      license
      Not graded
      quality
      B
      maintenance
      Local-first ambient memory for Mac that captures screen content, indexes it on-device, and provides MCP tools for searching memory, timeline, and open tasks.
      MIT

    • Project Memory

      Dankaro-projects
      A
      license
      A
      quality
      C
      maintenance
      Project Memory stores decisions, evidence, outcomes and reviewed lessons in local SQLite. Assistants retrieve bounded context through three MCP tools. People follow and plan work in a live workspace with an overview, sprint board, decision history, readable documents, skills and project maps. Offline exports remain available.
      3
      772 PyPI
      MIT
    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 19 tools

    Disambiguation4/5

    Each tool targets a clearly distinct resource or workflow phase: auth, project/timeline lifecycle, content authoring, preview/build/publish, and deletion. The only mild risk is the cluster of preview/build/publish tools plus run_layout_preview, which are related but have sufficiently explicit descriptions to choose correctly.

    Naming Consistency5/5

    All tools follow a consistent lowercase snake_case verb-first pattern: create_, get_, list_, set_, add_, delete_, preview_, publish_, build_, run_, record_, sign_. Even the more compound names like run_layout_preview and record_materials_consent fit the same convention without mixing styles.

    Tool Count4/5

    Nineteen tools is above the typical 3–15 sweet spot, but the breadth is justified by the full authoring/publishing workflow: account linking, project and timeline management, consent, entity/axis/node/connection authoring, preview, build, publish, and delete. It feels slightly heavy rather than bloated.

    Completeness3/5

    The core flow from project creation through authoring, consent, preview, build, and publish is well covered, and add_nodes/set_axis_values support incremental edits. However, there is no way to revise a timeline's top-level brief or project metadata after creation, and unpublishing effectively requires re-publishing with a different visibility or full deletion.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources