
SoftwareForge
io.github.shailesh-opseraPublished by GitHub account shailesh-opserav1.0.0Updated Oct 24, 2026
AI-native Day 0 modernization platform for PRDs, architecture, work orders, and code transformation.
The publisher's own server: Opsera
Overview
A remote MCP endpoint for an AI-native software modernization platform covering PRDs, architecture, work orders, and code transformation.
- What you can do
- SoftwareForge is a hosted, AI-native Day 0 modernization platform. According to its registry description, it covers product requirement documents, architecture, work orders, and code transformation. No tool list is published, so the exact operations an assistant can call are not documented here.
- When to use it
- Consider it when a team is planning or running a legacy-to-modernization effort and wants an assistant to work with PRDs, architecture artifacts, work orders, or code transformation through one hosted service.
- Requirements
- A remote streamable HTTP endpoint at the provider's hosted address; nothing is installed locally. It requires an Authorization header carrying a Bearer token for MCP authentication. No accounts, environment variables, or packages are declared.
Installation
In SourceWeft
- Open SoftwareForge in the dashboard and add it to a workspace.
- Connect Authorization token credentials. They are stored privately and never shown on public pages.
- 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/io.github.shailesh-opsera%2Fsoftwareforge/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": {
"softwareforge": {
"type": "http",
"url": "https://refactory.agent.opsera.dev/api/mcp",
"headers": {
"Authorization": "Bearer <YOUR_TOKEN>"
}
}
}
}README
This repository has no README.
Tools
0Version history
1- v1.0.0LatestSep 16, 2026
Score
60% 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
- Auth declaredRequired10 pts
- 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.
- License10 pts
Declare a license in the repository or the registry entry.
