
AgentBuilders
io.github.sirarchiemccarthy-ossPublished by GitHub account sirarchiemccarthy-ossv0.6.1Updated Oct 24, 2026
Deploy full-stack web apps with database, file storage, auth, and RBAC via a single API call.
Overview
AgentBuilders is a remote MCP endpoint that lets an assistant deploy full-stack web apps with database, file storage, auth and RBAC through a single API call.
- What you can do
- Deploy full-stack web applications through a single API call, with database, file storage, authentication and role-based access control provisioned as part of the deployment. The manifest lists no individual tools, so the exact operations available are not documented here; the description centers on one-call app deployment rather than separate management commands.
- When to use it
- Useful when you want an assistant to stand up a complete web application with its backing database, storage and access control without assembling each piece by hand.
- Requirements
- A remote streamable HTTP endpoint at api.agentbuilders.app. Authentication is required: a bearer token sent in the Authorization header in the format Bearer followed by an API key. No packages, local runtime or environment variables are declared.
Installation
In SourceWeft
- Open AgentBuilders 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.sirarchiemccarthy-oss%2Fagentbuilders/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": {
"agentbuilders": {
"type": "http",
"url": "https://api.agentbuilders.app/mcp",
"headers": {
"Authorization": "Bearer <YOUR_TOKEN>"
}
}
}
}README
This repository has no README.
Tools
0Version history
1- v0.6.1LatestSep 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 listedRequired15 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.