Skip to main content
Glama
cflorczyk9

margins-mcp

by cflorczyk9
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Related Servers

Alternatives to margins-mcp

No user-submitted related servers found.

    Related Servers

    • obsidian-mcp-server

      shivamsharmxa
      A
      license
      Not graded
      quality
      D
      maintenance
      Connects Claude.ai to your local Obsidian vault for full CRUD access, search, and daily note creation via the Model Context Protocol.
      77 npm
      14
      MIT

    • obsidian-mcp

      martinblq
      A
      license
      Not graded
      quality
      A
      maintenance
      Connects Claude to a local Obsidian vault, enabling listing, reading, searching, and optionally editing notes via natural language, with all operations running locally.
      3,445 npm
      MIT

    • obsidian-connector

      reyk-zepper
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables bidirectional interaction with Obsidian vaults, allowing reading, writing, and organizing notes through Claude.
      MIT

    • Obsidian MCP Server

      dino-quadrivia
      F
      license
      Not graded
      quality
      D
      maintenance
      Lets Claude save conversations, notes, and structured summaries directly to your Obsidian vault. Supports YAML frontmatter, auto-backlinks, daily notes, and vault search.
      -
    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.6/5.0

    Scored across 23 tools

    Disambiguation3/5

    Most tools are clearly separated by verb_noun intent, but there are confusing pairs: search_vault vs. search, and read_page vs. fetch, which both return text for a vault path. The detailed descriptions help, but an agent could easily misselect between these overlapping read/search tools.

    Naming Consistency3/5

    The dominant pattern is verb_noun, with list_, get_, propose_, and record_ tools carrying most of the surface. However, the mix is inconsistent: three tools use a margins_ prefix, two bare tools are just search and fetch, and recall_preferences breaks the get/list convention.

    Tool Count3/5

    23 tools is at the heavy end for a single MCP server and feels like several subsystems (vault context, raw ingestion, proposal management, research, diagnostics) bundled together. Each tool has a real use in the workflow, but the set would be easier to reason about if split or trimmed.

    Completeness4/5

    The core lifecycle is well covered: ingest raw files, propose compilations, edit or append to pages, list/resolve proposals, and read/search the vault. Obvious gaps include no explicit delete/remove tool for vault pages and no rename/move operation, but these are workarable rather than workflow-breaking.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources