Skip to main content
Glama
idleprocesscc

Shared Margin

by idleprocesscc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Shared Margin

No user-submitted related servers found.

    Related Servers

    • nvim-mcp

      schuay
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables coding agents and human reviewers to share a single live view of code, letting the agent open and annotate specific lines while the human marks ranges to ask about, all without any write access to the underlying files.
      1
      MIT

    • shared_memories

      RealSid08
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables trusted Codex clients to share selected Markdown memory snapshots across machines through a private, self-hosted SQLite store reached over local stdio or SSH. Exposes tools to list, read, and search shared memory and to add append-only cross-machine notes, while keeping a read-only offline cache available when the server is unreachable.
      Apache 2.0

    • agent-bridge

      LEO0047
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables Codex and Claude Code to collaborate autonomously as persistent peers that research, exchange questions and challenges, jointly edit a shared versioned report or coding repository, and record disagreements and evidence. A deterministic coordinator enforces the lifecycle and a dual approval gate on an exact artifact version before exporting an immutable final result.
      1
      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

    B3.3/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: begin starts a session, capture saves a moment, export exports data, finish closes a session, and trail lists sessions or moments. There is no overlap or ambiguity.

    Naming Consistency5/5

    All tools follow a consistent pattern: 'shared_margin_' prefix followed by an imperative verb (begin, capture, export, finish, trail) in snake_case. No deviations.

    Tool Count5/5

    5 tools is appropriate for the domain of shared-attention sessions, covering creation, capture, export, closing, and listing. Neither too sparse nor excessive.

    Completeness4/5

    The tools cover the main lifecycle (begin, capture, export, finish, list/read). Missing update or delete operations for moments/sessions, but these are not essential for basic use. Minor gap.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources