Skip to main content
Glama
pierreb4

seven-dpt-mcp

by pierreb4
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to seven-dpt-mcp

No user-submitted related servers found.

    Related Servers

    • hive-exp

      who96
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server enabling AI agents to record, query, and share structured problem-solving experiences with human review and confidence decay.
      5 npm
      MIT

    • Vibecoders MCP

      RaedBerjaoui
      A
      license
      A
      quality
      B
      maintenance
      One MCP that turns Claude Code into your whole dev stack by swallowing other MCP servers, delegating to Codex & Gemini on your CLI subscriptions, remembering projects in a searchable knowledge graph, and carrying setup across sessions — secret-free by design.
      23
      3
      MIT

    • project-memory-mcp

      kaaustubh
      A
      license
      A
      quality
      A
      maintenance
      Local MCP server giving AI coding agents (Claude Code, Cursor, VS Code/JetBrains Copilot) a shared, persistent memory of your projects and every bug/issue faced during development. Stateless, plain-file storage (AGENTS.md + issues.jsonl) — no database.
      16
      207 npm
      1
      MIT

    • SuperBased Observer

      superbasedapp
      F
      license
      Not graded
      quality
      A
      maintenance
      Local MCP server that lets your AI coding agent query its own cross-tool project history - file/command freshness, past test failures, cost & token spend, cache status, and session handoff - over stdio, 100% local, no telemetry.
      45
      -
    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 6 tools

    Disambiguation5/5

    Each tool targets a distinct action: adding problems, capturing sparks, recalling problems with evocation, viewing one problem, listing all, and updating spark outcomes. No two tools serve overlapping purposes.

    Naming Consistency4/5

    Most tools follow snake_case verb_noun pattern (add_problem, capture_spark, get_problem, list_problems, update_spark), but 'evoke' is a single verb without a noun, breaking the pattern slightly.

    Tool Count5/5

    With 6 tools, the set is well-scoped for the problem management domain it serves. Each tool has a clear role without redundancy, and the count feels neither too sparse nor too heavy.

    Completeness4/5

    The tools cover core workflows: add problems, generate and update sparks, and list/retrieve. Missing are deletion capabilities and the ability to modify spark ideas directly, but these are minor gaps given the specific methodology.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources