apply_to_build
Apply to build with noui.bot. Open to developers, agent operators, and companies.
LABSCO SUMMARY
An agent can ship code to a URL and check on it.
The deploy tools are the reason to install it: repo in, live URL out, with a status call to follow the run. The rest is platform-facing — statistics, service health, and a channel for saying what blocked you.
What it is
The MCP surface of noui.bot, a commerce and deployment layer for agents: a deploy rail that ships a GitHub repo to a live URL, platform and service status, and channels for reporting blockers or applying to build.
What you get
- Code deployed from a GitHub repo to a live URL
- A deployment's status, by action ID
- Deploy rail statistics: total deploys, success rate, agents registered
- The services running, with status, endpoints and descriptions
- Platform statistics — waitlist signups, feedback reports, applications — with no personal data
- A wall or obstacle reported back from the agent hitting it
- An application to build on the platform
Requirements
npx to run it. Reading the platform and service figures needs nothing; deploying needs a ShipRail API key.
Setup effort
One command — npx -y @forthebots/mcp-server
USE CASES
01
Getting something you built onto a live URL
Point it at the repo and the deploy runs from the conversation, returning an action ID to follow.
02
Following a deployment to completion
Status by action ID, so a long build is checked rather than waited out blind.
03
Checking the platform is up before you rely on it
Service status and endpoints, alongside the platform's own figures.
04
Judging whether the deploy rail actually works
Total deploys and success rate answer the question the marketing page cannot.
05
Reporting what is blocking your agent
The obstacle goes back to the operators from the agent that hit it, rather than through a human writing a ticket.
7 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
deploy
Deploy code from a GitHub repo to a live URL via Deploy Rail. Requires a ShipRail API key.
deploy_rail_stats
Get Deploy Rail statistics — total deploys, success rate, agents registered.
deploy_status
Check the status of a Deploy Rail deployment by action ID.
list_services
List all noui.bot services with status, endpoints, and descriptions.
platform_stats
Get noui.bot platform statistics — waitlist signups, feedback reports, applications. No PII.
report_wall
Report a wall or obstacle you're hitting as an AI agent. Tell us what's blocking you.
BEFORE YOU INSTALL
What to know first
Tools you get
7 tools when we connected. The documentation describes an HTTP billing API rather than these tools and uses dot names such as wallet.balance. The 14 Bazaar marketplace tools it mentions belong to third-party providers, not this server.
Requires
npx on PATH
CONTEXT COST
Light Standing cost
Rated by the size of the 7 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Add the block to your client, or run the command directly.
Server setup
Configuration file
JSON
{
"mcpServers": {
"forthebots": {
"command": "npx",
"args": [
"-y",
"@forthebots/mcp-server"
]
}
}
}npx
TERMINAL
npx -y @forthebots/mcp-server
