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
      C
      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
      B
      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.
      20 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

    Each tool targets a distinct resource (projects, documents, scheduled tasks) and action (list, get, create, update, delete, etc.). There is no ambiguity between tools within the same resource group, and cross-resource tools are clearly separated by naming.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (e.g., list_projects, create_project, read_document, delete_scheduled_task). The naming is predictable and adheres to the same convention throughout, making it easy to infer functionality.

    Tool Count4/5

    With 17 tools, the server sits slightly above the ideal 3-15 range, but each tool serves a distinct and necessary purpose within the three resource domains (projects, documents, scheduled tasks). The count is justified and not bloated.

    Completeness5/5

    The tool surface provides full lifecycle coverage for all three resource types: projects have complete CRUD operations, documents support list/read/write/rename/delete plus sync operations (pull/push), and scheduled tasks have full CRUD. There are no obvious gaps that would hinder agent workflows.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources