Skip to main content
Glama
benstaniford

CodeTour

by benstaniford
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to CodeTour

No user-submitted related servers found.

    Related Servers

    • Ferry

      danowicz
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to turn codebase changes into animated, narrated presentations that open in a browser and update live as the agent builds them, including stepped diffs, sequence diagrams, and review feedback loops.
      18
      MIT

    • MCP Walkthrough

      Stefan-Nitu
      A
      license
      A
      quality
      F
      maintenance
      Enables AI agents to present interactive code walkthroughs with voice narration, opening files, highlighting code, and showing inline explanations with synchronized text-to-speech.
      5
      11 npm
      MIT

    • showntell

      rahimnathwani
      A
      license
      A
      quality
      A
      maintenance
      Enables coding agents to turn explanations of code, pull requests, or concepts into narrated slide walkthroughs voiced locally with Kokoro, returning a link that starts playing in about a second while the remaining slides are still being written. Slides are grounded in real files and git history, checked for errors, and exportable as static folders with captions.
      7
      MIT

    • Code Review MCP Server

      danielefavi
      A
      license
      B
      quality
      C
      maintenance
      Connects LLMs to GitHub and GitLab to analyze pull and merge requests for logic, security, and architectural alignment. It provides tools for fetching diffs, file contents, and project metadata, alongside guided prompts for professional code reviews.
      10
      8 npm
      ISC
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A4.2/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a distinctly different role: fetching PR metadata, fetching file diffs, starting the tour, showing overview/step/end screens, and checking diagnostics. No two tools overlap in purpose, making selection unambiguous.

    Naming Consistency4/5

    Most tools follow a clear verb_noun pattern (get_pr_info, get_file_diff, start_tour, show_overview, show_step, end_tour). 'tour_status' is the one outlier, reading as a noun phrase rather than a verb-driven action.

    Tool Count5/5

    Seven tools is well-scoped for a PR tour workflow: two for data retrieval, four for tour progression, and one for diagnostics. Each tool serves a necessary function without redundancy.

    Completeness5/5

    The tool surface covers the full tour lifecycle: retrieving PR context, reading diffs, starting the tour, showing overview and steps, ending cleanly, and diagnosing state. No obvious dead ends or missing operations for the stated purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources