
Physical Agency
io.github.max7819v0.2.0Updated Oct 9, 2026
Human workforce for AI agents: field checks, user testing and device tests. Operator-reviewed work.
Overview
AI-generated overview
Connects an AI assistant to a remote service that arranges human workers for field checks, user testing, and device tests.
- What it does
- This remote MCP server gives an assistant access to a human workforce service. According to its description, it covers field checks, user testing, and device tests, with work reviewed by an operator. No tool list is published in the manifest, so the exact operations available are not documented here.
- When to use it
- Consider it when a task needs real-world human verification rather than automated checks, such as confirming something on site, gathering user feedback, or testing on physical devices. It is less relevant for purely software or data tasks that an assistant can complete on its own.
- Requirements
- A remote streamable HTTP endpoint; no local package, runtime, environment variables, or headers are declared. The manifest declares no authentication, so no credentials are documented.
Before you install
The manifest declares no authentication and no credentials, which is unusual for a service that dispatches human work; verify how access is controlled before use. Because the service arranges people to perform tasks, there may be costs or contractual terms not shown here, and any details sent to it leave your environment.
Installation
In SourceWeft
- Open Physical Agency in the dashboard and add it to a workspace.
- 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.
Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"manpower": {
"type": "http",
"url": "https://physical-agency-141382386601.asia-southeast1.run.app/api/mcp"
}
}
}Tools
0Tool metadata has not been indexed yet.
Version history
1- v0.2.0LatestOct 9, 2026

