Skip to main content
Glama
birajrai

lipi-mcp

by birajrai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to lipi-mcp

No user-submitted related servers found.

    Related Servers

    • notes-box

      g-konstkd
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables managing a local notes file through add, get, update, delete, and list operations via MCP.
      MIT

    • notes-box

      Schvisus
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables managing notes through add, get, update, delete, and list tools via MCP.
      -

    • agent-notes-mcp

      mitszo
      A
      license
      Not graded
      quality
      C
      maintenance
      Lets MCP clients search, read, create, append, replace, move, and batch-update local Markdown notes safely, with conflict detection via SHA-256 and optional managed update blocks, without requiring a vector database.
      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

    A4.1/5.0

    Scored across 9 tools

    Disambiguation4/5

    Each tool maps to a distinct action/resource pair: create, read, update, rename, delete, list, search, and login are clearly separated. The only mild overlap is between lipi_read_note and lipi_read_note_by_name, but their id-vs-name distinction is described well enough to avoid real confusion.

    Naming Consistency4/5

    All tools share the lipi_ prefix and mostly follow a verb_noun pattern like lipi_create_note and lipi_delete_note. lipi_login and lipi_search are verb-only exceptions, but the overall style remains predictable and uniform.

    Tool Count5/5

    Nine tools is a well-scoped set for a note management server: authentication, CRUD, renaming, listing, and search are all covered without unnecessary duplication. Each tool earns its place.

    Completeness5/5

    The tool surface covers the full note lifecycle: create, read by id, read by name, update with optimistic concurrency, rename/move, delete, list, and search. Auth is handled via lipi_login, and no obvious dead-end operations are missing for the stated domain.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources