Skip to main content
Glama
Attacktive

claude-projects-mcp-server

by Attacktive
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to claude-projects-mcp-server

No user-submitted related servers found.

    Related Servers

    • Local Dev Bridge MCP

      talentedmrweb
      A
      license
      A
      quality
      D
      maintenance
      Provides Claude Desktop with direct access to your local file system for development tasks, enabling file operations (read, write, edit), directory browsing, command execution, and codebase search within a configured projects directory.
      6
      MIT

    • obsidian-mcp

      bbdaniels
      A
      license
      A
      quality
      C
      maintenance
      Enables Claude Code read/write access to an Obsidian vault, including creating, editing, searching, and browsing notes.
      8
      MIT

    • workspace-mcp

      shanmukhdatta
      A
      license
      A
      quality
      B
      maintenance
      Bridges Claude AI with the local filesystem for direct file and project management, enabling incremental saves and automatic work logs to overcome token limits.
      22
      2
      MIT

    • XLMCP

      xLydianSoftware
      A
      license
      B
      quality
      D
      maintenance
      Enables Claude Code to interact with Jupyter notebooks, perform semantic search over knowledge files, and manage research projects.
      33
      4
      MIT
    • Axme-code by AxmeAI

      Axme-codeofficial

      AxmeAI
      A
      license
      Not graded
      quality
      D
      maintenance
      Persistent project memory + architectural decisions + pre-execution safety hooks for Claude Code. Local-only storage, multi-repo workspace, automatic knowledge extraction via background auditor.
      14 npm
      14
      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.2/5.0

    Scored across 17 tools

    Disambiguation5/5

    Every tool targets a distinct resource-action pair: projects, documents, and scheduled tasks each have separate create/read/update/delete/list or equivalent operations. Even similar-sounding tools like read_document vs list_documents have clearly differentiated behaviors, with no overlapping purposes.

    Naming Consistency5/5

    All tool names follow the verb_noun snake_case pattern consistently: list_projects, get_project, update_project, read_document, write_document, push_documents, etc. The only pluralization (list_* tools take plural nouns) follows a predictable list-versus-singular convention.

    Tool Count4/5

    17 tools is slightly above the typical well-scoped range, but the count is justified by covering three distinct resource types (projects, documents, scheduled tasks) with near-complete lifecycle operations. Each tool serves a clear need and the set remains navigable.

    Completeness5/5

    The tool surface is comprehensive for the domain: projects have full CRUD, documents cover read/write/rename/delete/list/pull/push, and scheduled tasks have create/read/update/delete/list. Edge cases like overwrite safety, local backups, and search threshold handling are baked into descriptions, leaving no obvious dead ends.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources