GitHub Mapper MCP Server

Created By
dazeba year ago
MCP GitHub Mapper is a MCP tool that will map any repository remotely and import the map directly into your code editor.
Overview

What is GitHub Mapper MCP Server?

GitHub Mapper MCP Server is a Model Context Protocol (MCP) tool designed to map and analyze GitHub repositories, allowing users to import repository maps directly into their code editors.

How to use GitHub Mapper MCP Server?

To use the GitHub Mapper, set your GitHub Personal Access Token, start the server, and use the provided commands to map and analyze repositories.

Key features of GitHub Mapper MCP Server?

  • Set GitHub Personal Access Token for authentication
  • Map and analyze GitHub repository structure
  • Retrieve summary information about repositories (stars, forks, language, etc.)
  • Provide detailed repository file structure

Use cases of GitHub Mapper MCP Server?

  1. Analyzing the structure of open-source projects on GitHub.
  2. Importing repository maps into local development environments.
  3. Generating summary statistics for project management.

FAQ from GitHub Mapper MCP Server?

  • How do I set my GitHub token?

You can set your GitHub token using the set-github-token command in your IDE.

  • What happens if I don't set my GitHub token?

You will receive an error message prompting you to set the token before proceeding.

  • Can I use GitHub Mapper with any repository?

Yes, as long as you have the appropriate permissions set in your GitHub Personal Access Token.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
dazeb
Star
16
Language
TypeScript
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago