M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionC64 Bridge MCP ServerMCP server to control and program the Commodore 64 from AI clientsGitHub MCP ServerGitHub's official MCP server for managing repos, issues, PRs, and workflows via natural language
FMRS58 / 100 · C76 / 100 · B
Reliability7 / 2013 / 20
Security and permissions10 / 2014 / 20
Maintenance11 / 2018 / 20
Documentation17 / 2017 / 20
Setup experience13 / 2014 / 20
Best for
  • Retrocomputing enthusiasts who own Ultimate-family hardware or run VICE and want AI-assisted C64 development
  • Developers working with BASIC / 6502 assembly, SID music, or PETSCII graphics
  • Teams automating C64 program testing across real hardware and emulators with an AI agent
  • Teams that want an AI assistant to directly operate on GitHub repos and collaboration workflows
  • Users already in the GitHub Copilot ecosystem who want a zero-deployment remote option
Not for
  • Users without any C64 hardware or the VICE emulator (no backend is available)
  • Beginners seeking a fully hosted cloud service with no local setup
  • Retro platforms other than the Commodore 64 (this server is C64-specific)
  • Scenarios where you don't want the assistant to have write access to repos (enable only read-only toolsets)
  • Environments with strict network isolation for private repos that can't reach the official remote endpoint
Required permissions
  • Network access to C64 Ultimate / Ultimate 64 / U2 cartridges via REST (default port 80), with an optional network password sent as an X-Password header
  • Ability to launch and manage a local VICE emulator process and its Binary Monitor (default 127.0.0.1:6502)
  • Local file access for config files, memory/screen dumps, diagnostics, and output artifacts
  • Optional: GITHUB_TOKEN for RAG discovery against GitHub; optional use of sidplayfp for audio generation
  • A personal access token (PAT) or OAuth App token; effective scope depends on the token's own permissions
  • Enabling toolsets like actions/issues/pull_requests grants write access — request tokens on a least-privilege basis
Risks and side effects
  • The server can write memory, control power/reset, and manage drives; misuse may disrupt running C64 programs or firmware state
  • Network passwords and GitHub tokens are passed in plaintext via environment variables, so credential handling matters
  • The optional HTTP bridge is disabled by default; if enabled without protection, local clients could invoke tools
  • U2-family cartridges have reduced capability (no machine input, debug registers, power-off, or streaming), and some operations require recent firmware (e.g., U64 3.15+), so older firmware makes certain tools unavailable
  • Write toolsets (creating/merging PRs, triggering workflows) can cause accidental changes if the token is overscoped — try a read-only toolset first
  • In hosted mode, credentials travel via the Authorization header — make sure the client-to-api.githubcopilot.com connection is trusted
Supported clientsGitHub Copilot, Claude Code, Cursor, Visual Studio, VS Code InsidersClaude Desktop, Claude Code, VS Code, Cursor, Windsurf, JetBrains IDEs, Zed, Amp
Tools1715