DeepYard

GitHub MCP vs Memory MCP

Side-by-side comparison built from DeepYard's structured catalog. Content updated Aug 21, 2026.

Direct Answer

GitHub MCP suits teams needing open-source access, repo management focus, and 32,422 GitHub stars in current listing data. Memory MCP suits teams needing open-source access, persistent memory focus, and 89,768 GitHub stars in current listing data. This summary reflects catalog metadata only for decision support, not independent testing.

What this comparison weighs

  • Pricing and free-tier availability
  • License model and deployment fit
  • GitHub adoption and contributor depth
  • Catalog tags, integrations, and supported workflows
G

GitHub MCP

Full GitHub API access — repos, issues, PRs, and code search via MCP

OSSFree
32.4K28.0K/wtoday155
M

Memory MCP

Persistent knowledge graph memory across AI coding sessions

OSSFree
89.8K15.0K/w2d ago426
MetricGitHub MCPMemory MCP
GitHub Stars32.4K89.8K
Contributors155426
Last CommitAug 21, 2026Aug 20, 2026
Open Issues327533
Licenseopen-sourceopen-source
Pricingopen-sourceopen-source
Free TierYesYes
Categorymcp-serversmcp-servers
TrendingNoNo

Choose GitHub MCP if you need

  • GitHub MCP is the stronger pick when Repo Management matters because that capability is listed only on its profile.
  • GitHub MCP is the cleaner fit if you specifically need Github workflows from the catalog tags.

Choose Memory MCP if you need

  • Memory MCP is the stronger pick when Persistent Memory matters because that capability is listed only on its profile.
  • Memory MCP shows broader GitHub adoption with 89,768 stars versus 32,422 for GitHub MCP.
  • Memory MCP has a larger visible contributor base (426 vs 155).

Meaningful differences

  • GitHub adoption: GitHub MCP shows 32,422 stars versus 89,768 for Memory MCP.
  • Contributor count: GitHub MCP lists 155 contributors and Memory MCP lists 426.

Shared capabilities

  • • No shared capabilities are explicitly listed in the stored metadata.

Shared Tags

No shared tags

Only in GitHub MCP

githubversion-controlpull-requestsissuescode-searchdevops

Only in Memory MCP

memoryknowledge-graphpersistenceanthropicreference-servercontext-management

Limitations and evidence

  • DeepYard compares structured public metadata; this is not an independent benchmark unless a test record is shown.
  • Signals such as stars, contributors, and last commit indicate public activity, not purchase fit or runtime quality.
  • Pricing and feature coverage reflect the stored listing snapshot and may lag vendor changes between refreshes.

About GitHub MCP

GitHub's official MCP server brings the entire GitHub API surface into your AI coding workflow. Create and review pull requests, manage issues, search code across repositories, read file contents, list branches, and trigger Actions runs — all without leaving your editor. Authenticate once with a GitHub Personal Access Token and let Claude Code interact with any repository you have access to.

View full listing

About Memory MCP

The official Anthropic memory MCP server gives AI assistants persistent, cross-session memory using a local knowledge graph stored as a JSON file. Claude can create entities (people, projects, concepts), record relations between them, and add observations over time — then recall that information in future sessions. Ideal for long-running projects where continuity matters: the assistant remembers your architecture decisions, team conventions, and in-progress work without you having to repeat context.

View full listing