Developer · Remote MCP server
AgentBuilders
Deploy full-stack web apps with database, file storage, auth, and RBAC via a single API call.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.sirarchiemccarthy-oss/agentbuilders- Version
- 0.6.1
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-03-06
- Updated
- 2026-03-06
- Publisher
- sirarchiemccarthy-oss (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/sirarchiemccarthy-oss) · how
- Repository
- github.com/sirarchiemccarthy-oss/clawd
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://api.agentbuilders.app/mcp | Authorization (required, secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 403)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 403
- Checked on
- 2026-10-05
How to connect AgentBuilders
AgentBuilders is a remote MCP server: there is nothing to install. Its endpoint is https://api.agentbuilders.app/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: Authorization (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| agent-toolEncoding-aware, indentation-file tools for AI coding agents with SSH, SFTP, and 20+ tools. | Local · stdio |
| AgentAegisPay-per-call cybersecurity for AI agents: vuln scans, threat intel, compliance, code security. | Remote · HTTPLive check: ✓ handshake |
| AgentBrain HandoffsExact, durable handoffs between AI coding agents: one turn in the right session, never twice. | Local · stdio |
| AgentbuildersDeploy full-stack AI agent apps with database, auth, storage, and Edge AI on one platform. | Local · stdio |
| agentbuiltFree AI-readiness audit of any URL: AI crawler rules, JS-free text, JSON-LD, llms.txt. Tool catalog. | Remote · HTTPLive check: ✓ handshake |
| AgentcastStructured-output enforcer: extract and validate JSON from messy LLM text. | Local · stdio |
| AgentCatAnalytics and debugging for your MCP server - explore usage and sessions, then root-cause errors. | Remote · HTTPLive check: sign-in required |
| agentchanLets one coding agent talk to another: Claude Code, Codex or Grok. | Local · stdio |