Log inSubmit server
GitHubCard logo

GitHubCard

Create GitHub profile and repository cards with live data, customizable templates, and embed links for READMEs and social posts.

InstallRepositoryWebsite
Get support Full README Compare alternatives Embed widget

Install GitHubCard

Pick your client, then add it in one click or paste the config.

Streamable HTTP (Remote)
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "githubcard": {
      "command": "npx",
      "args": [
        "-y",
        "@ghcardhq/ghcard"
      ],
      "env": {
        "GHCARD_API_KEY": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Hosted endpointLive · 1d agoLive Remote EndpointOur automated health check connected to this remote MCP endpoint successfully.Last checked 1d ago · Nov 12, 2026, 19:02 UTC

Clients with native remote MCP support can connect directly to this URL.

Remote endpoint
https://githubcard.com/mcp
We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx -y @ghcardhq/ghcard

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked .

Overview

GitHubCard MCP server creates profile and repository card images from live GitHub data through GitHubCard. Use the hosted Streamable HTTP endpoint without installation, or run the MCP server locally through the ghcard CLI over stdio. It supports templates, palettes, widgets, custom designs, and optional README updates. Reach for it when an agent needs to generate or maintain visual GitHub previews for documentation, link previews, or social content.

Use cases

  • Create profile cards for a GitHub README
  • Generate repository previews for social posts
  • Customize repository cards with templates and palettes
  • Validate card designs before using quota
  • Update README card embeds from a local MCP process

Key features

  • Creates profile and repository cards from live GitHub data
  • Returns SVG, PNG, Markdown, and HTML embed links
  • Supports templates, palettes, widgets, and custom designs
  • Provides hosted Streamable HTTP and local stdio modes
  • Updates Markdown README files locally
  • Offers idempotent card creation and quota validation

Tools10

What GitHubCard lets your agent do. Expand a tool for its parameters.

Verified live~1.3k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked

Recent health check succeeded.

4/4 checks healthy over the last 13d

What it can do

From the 10 tools this server returned when we ran it.

Can delete or modify data · 1Read-only tools · 9
Tool definitions changed on 2026-11-08. Review them if you approved this server earlier.

Observed 2026-11-08 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 13d ago via OSV.dev · @ghcardhq/ghcard (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars15Stargazers on the source repository.
npm downloads944Package downloads in the last 30 days.
Last commit5d agoMost recent push to the default branch.
MaintenanceActively maintainedStatus declared by the project or listing owner.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Tools exposed10Callable tools this server registers over MCP.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How GitHubCard works

What GitHubCard MCP server does

GitHubCard turns a GitHub username or owner/repo identifier into a profile or repository card. Generated cards include links to SVG and PNG images, along with Markdown and HTML snippets for embedding in READMEs, websites, link previews, and social posts. The rendered cards use live GitHub data, so an existing card can reflect updated repository or profile information without being recreated.

The service supports selectable templates, background palettes, widget types, custom backgrounds, and design documents. Repository cards can use options such as compact layouts, while callers can control which visual components appear. A local-only operation can insert or update a card reference in a Markdown README file.

How it works

The hosted endpoint is available at https://githubcard.com/mcp using Streamable HTTP. A local installation runs through npx -y @ghcardhq/ghcard mcp and communicates over stdio. Local execution requires Node.js 20 or newer. Add --allow-file-writes to the local command when the update_readme tool needs to modify files.

Creating or managing cards requires a GitHubCard API key, passed as a bearer token to the hosted service or through GHCARD_API_KEY for the local process. Calls that only inspect templates, palettes, and component types can be used without a key. Card creation is idempotent: repeated requests with the same inputs return the same card and link.

Setup and configuration

Create an API key from the GitHubCard dashboard, then configure it in the MCP client as an authorization header or environment variable. The hosted connection avoids local installation. The local command is useful when an agent must update files on disk, and it can also be used in clients that need environment-based credential configuration.

Claude Code, Cursor, VS Code, Windsurf, Codex CLI, and Claude Desktop each have documented connection patterns. Claude Desktop's custom connector does not provide custom headers, so use the local configuration with GHCARD_API_KEY when authentication is required. VS Code can prompt for the key and store it securely.

Tools and capabilities

  • create_card creates or reuses a profile or repository card and returns image and embed links. It consumes one unit of the daily quota.
  • validate_card checks identifiers, Pro-only options, and custom designs without creating a card or using quota.
  • list_templates, list_palettes, and list_components expose available layouts, backgrounds, and widget types.
  • get_template_design returns an editable design document for a template.
  • get_card_design retrieves the design document for one of the user's cards.
  • list_cards, delete_card, and get_usage manage cards and show plan and remaining daily quota.
  • update_readme inserts or updates a card in a Markdown file and is available only from the local server with file writes enabled.

Failed calls report an error flag, a stable error code, whether retrying is appropriate, and a hint for the next action.

Limitations and notes

The Free plan allows 100 cards per day and adds a small watermark; the Pro plan allows 5,000. Quotas reset at 00:00 UTC, and failed calls do not count toward the limit. Deleting a card stops its generated links from working. An API key is needed for card creation and account-scoped operations, while catalog tools remain available without one.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about GitHubCard

GitHubCard is an MCP server that connects GitHub profile and repository data with the GitHubCard image service. Its main tools create cards, validate designs, browse templates and palettes, manage generated cards, check usage, and optionally update a local README through the stdio server.

Use the hosted endpoint at `https://githubcard.com/mcp` without installing anything, or run `npx -y @ghcardhq/ghcard mcp` locally. The local option needs Node.js 20 or later and uses stdio; add `--allow-file-writes` for README updates.

Yes, GitHubCard has documented configurations for Claude Desktop, Cursor, and VS Code, as well as Claude Code, Windsurf, and Codex CLI. Claude Desktop requires the local setup for authenticated requests because its custom connector does not support custom headers.

Yes, creating cards requires a free GitHubCard API key. Supply it as an Authorization bearer token for the hosted endpoint or set `GHCARD_API_KEY` for the local server. Template, palette, and component listing tools can be used without a key.

Yes, the local server can insert or update a card in a Markdown file through `update_readme`. Start the command with `--allow-file-writes`; the hosted endpoint does not provide this local file operation.

Related MCP servers

All in Version Control All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewGitHubCard AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/githubcard?style=directory)](https://allmcps.com/mcp/githubcard)
HTML Embed
<a href="https://allmcps.com/mcp/githubcard"><img src="https://allmcps.com/api/badge/githubcard?style=directory" alt="GitHubCard on AllMCPs" /></a>