Everforth GitHub MCP Server

Created By
Everfortha year ago
Overview

What is Everforth GitHub MCP Server?

The Everforth GitHub MCP Server is a simple server that allows secure GraphQL access to GitHub, designed to handle access tokens securely without exposing them to the Cursor Agent.

How to use Everforth GitHub MCP Server?

To use the server, add the github-cli section to your Cursor's mcp.json configuration, insert your GitHub personal access token, and restart Cursor. You can also customize the server by building it from the provided Dockerfile.

Key features of Everforth GitHub MCP Server?

  • Secure handling of GitHub access tokens
  • Simple setup with Docker
  • Customizable through Dockerfile

Use cases of Everforth GitHub MCP Server?

  1. Integrating GitHub GraphQL API with Cursor.
  2. Customizing GitHub interactions in development environments.
  3. Managing GitHub repositories and data securely.

FAQ from Everforth GitHub MCP Server?

  • Can I use my own Docker image?

Yes! You can customize the Dockerfile and build your own image.

  • Is there a public image available?

Yes! A public image is provided for easy setup.

  • How do I secure my access token?

The server is designed to handle access tokens securely, ensuring they are not exposed.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Everforth
Star
0
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)

a day ago