Skip to main content
Glama
nampd3

Project Knowledge MCP Server

by nampd3
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Project Knowledge MCP Server

No user-submitted related servers found.

    Related Servers

    • arch-viewer

      axumquant
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides AI-powered architecture analysis and visualization of codebases, exposing 17 MCP tools for querying components, dependencies, and generating interactive diagrams.
      602 npm
      3
      MIT

    • Processkit

      raintr91
      A
      license
      Not graded
      quality
      B
      maintenance
      Standalone MCP harness for cross-system process evidence, code-change impact review, and natural-language repository checkout mapping, with optional accelerators like CodeGraph.
      1
      MIT

    • architectos

      cgseyhan
      F
      license
      Not graded
      quality
      A
      maintenance
      Analyzes repositories, explains architecture, calculates change impact, and enforces guardrails for AI Agents like Claude Code, Cursor, and Codex via MCP tools.
      -

    • ontomics

      EtienneChollet
      A
      license
      A
      quality
      C
      maintenance
      Extract domain knowledge from codebases to reduce LLM token consumption by 20x and time in agentic search by 10x — gathers and makes concepts, naming conventions, and vocabulary queryable via MCP.
      19
      41
      MIT

    • DevIntel

      marames25
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables natural language analysis of local software repositories, providing insights into project structure, technologies, code, tests, and Git history through MCP tools.
      -
    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/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool has a clear, distinct purpose: retrieving specific project details (dependencies, I/O, profile, purpose), listing projects, listing conflicts, and triggering refreshes. No overlap or ambiguity.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern: 'get_project_*', 'list_*', 'refresh_*'. The naming is clear and predictable across all tools.

    Tool Count5/5

    With 8 tools, the set is well-scoped for a project knowledge server. It covers retrieval, listing, conflict detection, and refresh operations without being too many or too few.

    Completeness5/5

    The tool surface fully covers the domain: retrieving project knowledge, listing projects, detecting conflicts, and refreshing data. No obvious gaps like missing search or update are expected given the server's purpose.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources