Skip to main content
Glama
lukebmandel-debug

Alto Connector

by lukebmandel-debug
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Alto Connector

No user-submitted related servers found.

    Related Servers

    • lifedb-mcp

      SPA3K
      A
      license
      B
      quality
      A
      maintenance
      Enables any MCP-capable agent to read and write a local personal timeline — GPS tracks, photos, workouts, health metrics, and stays — through seven indexed tools for monthly timelines, cross-modal lookups around a moment, geo-track retrieval, atlas exports, and idempotent JSONL ingestion. All data stays in a single on-device SQLite file, with no arbitrary SQL and no cloud.
      7
      1
      MIT

    • Plot & Kin

      jestatsio
      A
      license
      C
      quality
      A
      maintenance
      Enables researchers to turn property-history questions into reviewable evidence dossiers by gathering sources, tracing people and places, linking conclusions to supporting or opposing passages, and exporting portable backups.
      37
      Apache 2.0
    • DayDream by getnorthlight

      DayDreamofficial

      getnorthlight
      A
      license
      Not graded
      quality
      A
      maintenance
      A native macOS app with a read-only stdio MCP server for searching a local work timeline by app, document, optional Chrome page context and time. Requires Apple silicon and macOS 15+; it runs on the user’s Mac, rather than in Docker or as a hosted endpoint.
      9
      MIT

    • Continuity by Ouroboros Apps

      LAHutchins91
      A
      license
      Not graded
      quality
      B
      maintenance
      Continuity by Ouroboros Apps (https://ouroborosapps.com). Story continuity for fiction writers: a series bible and novel memory that keeps characters, places, timelines, and plot facts consistent across chats. Connect by pasting https://continuitywriter.com/mcp into Claude, Cursor, Grok, or ChatGPT (OAuth). Docs: https://ouroborosapps.com/docs/continuity
      2 npm
      MIT
    Deploy Server
    Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    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