Frontispice
Related Servers
Alternatives to Frontispice
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceMCP coordination primitive for multi-agent workflows. Lets multiple AI coding agents (Claude Code, Cursor, n8n, custom clients) discover each other and exchange messages and tasks via a shared SQLite-backed message bus.3795 npm4MIT
- AlicenseNot gradedqualityCmaintenanceLocal-first MCP server that enables multiple Claude agents to coordinate through a shared message bus with SQLite persistence and real-time clock anchoring.MIT
- AlicenseNot gradedqualityBmaintenanceEnables coding agents in different editors and MCP clients to share messages, project context, notes, task ownership, handoffs, and advisory file claims through a local SQLite-backed coordination server. Supports MCP stdio, MCP Streamable HTTP, a JSON HTTP API, and a local CLI for multi-project agent collaboration.MIT
- FlicenseNot gradedqualityBmaintenanceA lightweight, local-first MCP server that enforces zero-trust data privacy for AI agents by encrypting tool call payloads locally using AES-256-GCM and persisting them to a local SQLite database.-
- AlicenseBqualityAmaintenanceLocal MCP event log for multi-agent workspaces, enabling structured event publishing, cursor-based polling, and status checks via SQLite-backed sidecar.10355 PyPIMIT
- AlicenseNot gradedqualityBmaintenanceEnables coding-agent sessions on the same machine to collaborate locally and durably by exchanging requests, replies, and task results through an authenticated loopback server with SQLite-backed storage, joined via CLI or an MCP stdio bridge. It also handles message delivery by priority and wait time, deduplicates idempotent sends, enforces task versioning, and preserves artifacts by content hash.282 npmApache 2.0
TDQS
Scored across 8 tools
Each tool targets a distinct operation in the handoff lifecycle—publishing, reading, listing, routing, tracking, cursor management, and status. There is no overlap between tool purposes.
All tools follow the consistent `frontispice_<verb>_<object>` pattern (e.g., publish_handoff, list_updates, advance_cursor), with clear verbs and nouns. The naming is perfectly uniform.
Eight tools is well-scoped for a handoff management system, covering publishing, reading, routing, listing, and cursor state without redundancy. The count feels appropriate for the domain.
The surface covers the full lifecycle of handoffs: creation (publish), retrieval (read/list), routing metadata, application tracking, and consumer state management. No obvious gaps exist in the workflow.