Chipp Legacy code
ai.chippPublished by chipp.aiOfficial publisherv1.0.0Updated Oct 29, 2026
Chipp: the code of an app being rebuilt: the imported GitHub repo and the legacy codebase
The publisher's own server: Alchemist Cloud Tickets
Overview
Chipp sub-MCP that gives an assistant access to the imported GitHub repository and legacy codebase of an app being rebuilt.
- What you can do
- Expose the imported GitHub repository of an app being rebuilt
- Expose the legacy codebase of that app
- Provide context on existing code during a rebuild
- No individual tools are documented, so exact operations are unclear
- When to use it
- Useful when rebuilding an existing app with Chipp and the assistant needs to see the original GitHub repository or legacy code for reference. Otherwise there is little documented to justify adding it.
- Requirements
- A remote streamable HTTP endpoint at mcp.chipp.ai; no packages, environment variables or headers are declared. The manifest declares no authentication, but access to a specific app's repository and legacy code presumably depends on the Chipp workspace it belongs to.
Installation
In SourceWeft
- Open Chipp Legacy code in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/ai.chipp%2Fchipp-legacy-code/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"chipp-legacy-code": {
"type": "http",
"url": "https://mcp.chipp.ai/mcp/legacy-code"
}
}
}Tools
0Version history
1- v1.0.0LatestOct 29, 2026
Score
28% 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 daysRequired25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declaredRequired10 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
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.
Other Chipp integrations
Alchemist Cloud Tickets
ai.chippOfficial publisher
Lets an assistant dispatch and track Alchemist Cloud tickets, watch deployments, read logs, and query a project database.
Chipp Tickets
ai.chippOfficial publisher
Chipp Tickets's hosted MCP server, published by chipp.ai; no sign-in required; Streamable HTTP.
Chipp Tags
ai.chippOfficial publisher
Chipp Tags's hosted MCP server, published by chipp.ai; no sign-in required; Streamable HTTP.
Chipp Releases
ai.chippOfficial publisher
Chipp Releases's hosted MCP server, published by chipp.ai; no sign-in required; Streamable HTTP.
Chipp Software factory projects
ai.chippOfficial publisher
Chipp Software factory projects's hosted MCP server, published by chipp.ai; no sign-in required; Streamable HTTP.