
Segaretro Mcp
io.github.mrfentmenPublished by GitHub account mrfentmenv1.0.3Updated Oct 24, 2026
Use this MCP server to Sega Retro, every Sega game, console, and unreleased hardware. Tools...
Overview
Local MCP server that gives an assistant access to Sega Retro, a reference wiki covering Sega games, consoles and unreleased hardware.
- What you can do
- Look up Sega Retro content about Sega games, consoles and unreleased hardware.
- The registry description names no individual tools, so the exact operations are not documented here.
- It runs as a local process over stdio rather than a hosted endpoint.
- When to use it
- Worth adding when you want an assistant to answer questions about Sega games, consoles or unreleased hardware using Sega Retro as the reference source.
- Requirements
- A local runtime able to run the npm package segaretro-mcp over stdio (Node.js for an npm package). No authentication, environment variables or headers are declared. Network access is likely needed to reach Sega Retro, though this is not stated.
Installation
In SourceWeft
- Open Segaretro Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
segaretro mcp
MCP server for Sega Retro, the wiki covering every Sega game, console, and unreleased hardware.
Tools
Usage
Example:
Keyless (MediaWiki API). Covers hardware revisions, prototype differences, and obscure regional releases most other wikis skip.
Source: README.md at commit 844b73d
Tools
0Version history
2- v1.0.3LatestOct 2, 2026
- v1.0.0Sep 22, 2026
Score
40% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.