ActionBox Human Input
cloud.actionboxPublished by actionbox.cloudOfficial publisherv0.2.1Updated Oct 24, 2026
Human review for AI agents: ask through ActionBox and retrieve a typed decision before proceeding.
Overview
Lets an AI assistant request human review through ActionBox and retrieve a typed decision before continuing.
- What you can do
- This remote MCP server connects an assistant to ActionBox so it can ask a person for input and wait for a typed decision before proceeding. The registry description frames it as human review for AI agents: the assistant submits a request and receives a structured answer it can act on. No individual tools are listed in the manifest, so the exact request and response shapes are not documented here.
- When to use it
- Use it when an automated workflow needs a human checkpoint, such as approving an action, resolving ambiguity, or supplying a judgment the model should not make alone. It fits agents that must pause and resume on a person's decision rather than run fully unattended.
- Requirements
- A remote streamable HTTP endpoint at api.actionbox.cloud, reachable over the network. Authentication is required: a bearer token sent in the Authorization header, described as an ActionBox Source key. No local package, runtime, or environment variables are declared.
Installation
In SourceWeft
- Open ActionBox Human Input 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/cloud.actionbox%2Fhuman-input/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": {
"actionbox-human-input": {
"type": "http",
"url": "https://api.actionbox.cloud/mcp",
"headers": {
"Authorization": "Bearer <YOUR_TOKEN>"
}
}
}
}Tools
0Version history
1- v0.2.1LatestOct 13, 2026
Score
67% 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.
- 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.