Alto Connector
Related Servers
Alternatives to Alto Connector
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables 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.71MIT
- AlicenseCqualityBmaintenanceEnables 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.37Apache 2.0

DayDreamofficial
AlicenseNot gradedqualityBmaintenanceA 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.12MIT- AlicenseBqualityDmaintenanceEnables users to maintain append-only content history with verified publication and social follow-through outcomes, search for overlaps, and run read-only integrity verification of stored snapshots.16MIT
- AlicenseBqualityCmaintenanceEnables AI agents to query a local, continuously recorded Mac audio timeline, including speaker-labeled transcripts, topic-organized events, projects, todos, daily summaries, insights, and long-term memories.11MIT
- AlicenseNot gradedqualityCmaintenanceGives AI agents a durable, locally hosted temporal memory built from a markdown vault you own, exposing hybrid semantic/lexical/entity search over events, threads, transcripts, entity relationships with validity dates, and patterns with confidence decay. Writes are approval-gated, so agents can draft, commit, and sync new memories while keeping every index rebuildable and nothing leaving your machine.MIT
TDQS
Scored across 19 tools
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.
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.
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.
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.