
Codepet Mcp
io.github.mrfentmenPublished by GitHub account mrfentmenv1.0.7Updated Oct 30, 2026
Local MCP companion for CodePet status, quests, and source-free coding events. Tools include get...
Overview
Local MCP companion for the CodePet Chrome extension that exposes pet status, quest progress, and metadata-only coding events.
- What you can do
- Read local pet metadata and current status
- Record coding events with language, line count, test count, file count and status
- List quests and their progress
- Clear the local pet metadata history
- When to use it
- Use it when you already run the CodePet Chrome extension and want an assistant to read pet status and quest progress or log coding activity metadata locally. It is not a general-purpose coding or source-analysis tool.
- Requirements
- Runs as a local stdio process installed from the npm package codepet-mcp (build with npm install and npm run build, then run the built entry point). State is stored in a local file defaulting to ~/.codepet/state.json, which can be changed with the CODEPET_STATE_FILE environment variable. No API key and no network access are needed.
Installation
In SourceWeft
- Open Codepet 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
CodePet MCP
A local MCP companion for the CodePet Chrome extension. It exposes pet status, quests, and source free coding events.
Tools
get_pet_statusreads local pet metadatarecord_coding_eventrecords language, line count, test count, file count, and statuslist_questsshows progressclear_pet_historyremoves local metadata history
Do not send source code to this server. It intentionally accepts metadata only.
Run
The state file defaults to ~/.codepet/state.json. Set CODEPET_STATE_FILE to use another local path.
Privacy
No API key is required. The server makes no network requests. It never executes or stores source code.
Source: README.md at commit 383039f
Tools
0Version history
2- v1.0.7LatestOct 29, 2026
- v1.0.1Sep 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.