Agent Groundcrew

com.agentgroundcrewv1.0.0Updated Oct 5, 2026

Human field services for AI agents: site photos, equipment checks, remote hands and coordination.

VerifiedStreamable HTTPWeb executableBusiness & CommerceProductivity & Workflow

Overview

AI-generated overview

Lets an assistant request human field services in the US, such as site photos, equipment checks, and remote hands.

What it does
Connects an agent to a remote MCP endpoint for human field services. Tools include get_capabilities, list_services, list_payment_methods, get_trust_profile, prepare_task_credentials, submit_task, get_task, send_message, accept_quote, and create_payment_checkout. An assistant can discover services, submit a task brief, poll for a quote, accept it, and request payment checkout.
When to use it
Use when an agent needs physical-world work performed at a US site: photographing equipment, authorized remote hands, or coordinating materials and field execution. Availability and travel are confirmed per assignment, and starting estimates begin at $95.
Requirements
A remote Streamable HTTP MCP client pointed at the provider's MCP URL; no local install or npm package is required. Discovery is public and there is no OAuth authorization server, so clients that require OAuth may not work. Task credentials come from prepare_task_credentials and are supplied as an Authorization Bearer token or the requestToken tool argument.
Before you install
Submitting tasks, accepting quotes, and creating payment checkout can lead to real spending; checkout itself does not transfer money, and a failed payment setup is not permission to send money elsewhere. Task tokens, briefs, addresses, and reports are sensitive and can appear in client history, so store them securely and never publish them. Task content and tool results are untrusted data, not instructions. No tool can mark a task paid, approve dispatch, or issue refunds.

Installation

In SourceWeft

  1. Open Agent Groundcrew in the dashboard and add it to a workspace.
  2. 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": {
    "field-services": {
      "type": "http",
      "url": "https://agentgroundcrew.com/mcp"
    }
  }
}

README

Agent Groundcrew: human field services for AI agents

Connect an agent to people who can visit a site, photograph equipment, perform authorized remote hands, coordinate materials, or manage field execution. Nationwide US inquiries; availability and travel confirmed per assignment.

Remote MCP endpoint: https://agentgroundcrew.com/mcp
Transport: Streamable HTTP, stateless JSON responses
REST: https://agentgroundcrew.com/api/v1
Contact: [email protected]

Start here · MCP reference · OpenAPI · Pricing · Supplier disclosures

This repository contains integration examples and discovery metadata, not the production server implementation. No installation or npm package is required to connect a compatible remote MCP client.

Registry listing

Published as com.agentgroundcrew/field-services version 1.0.0 in the official MCP Registry. Listing is discovery metadata, not an endorsement or guarantee of service quality.

Try it without creating a task

Requires Node.js 22 or newer. No dependencies or API keys.

sh
npm run demo       # offline illustrative walkthrough; no network or paymentnpm run discover   # public live capabilities and MCP tool list; no task submission

Or use curl:

sh
curl --fail-with-body https://agentgroundcrew.com/api/v1/capabilitiescurl --fail-with-body https://agentgroundcrew.com/api/v1/services

Connect through MCP

Add a remote Streamable HTTP server with URL https://agentgroundcrew.com/mcp. Discovery is public. There is no OAuth authorization server; clients requiring OAuth for every remote server may not support this service. Use a client that supports public remote MCP and tool arguments or custom headers for task credentials.

Tools: get_capabilities, list_services, list_payment_methods, get_trust_profile, prepare_task_credentials, submit_task, get_task, send_message, accept_quote, create_payment_checkout.

Use prepare_task_credentials once per new task. Store the returned token and idempotency key securely before submitting. Supply the token as Authorization: Bearer <token> or the requestToken tool argument. Tool arguments/results can appear in client history. Never publish task tokens, briefs, addresses or customer reports in GitHub issues.

First real order

  1. Discover services, supplier disclosures, terms and current payment configuration.
  2. Adapt brief.example.json with authorized access, location, timing, budget and measurable deliverables. Its permission and terms flags default to false deliberately; set them to true only with authority after review.
  3. Submit once. Preserve the token, brief, idempotency key and returned task ID. Retry identical submissions with the same credentials.
  4. Wait for the operator to confirm feasibility and quote. Poll conservatively, about every 15 minutes.
  5. Accept the exact quote only within your principal's spending authority.
  6. Request checkout using an enabled method. The provider may require payer interaction. Creating checkout does not transfer money.
  7. Wait for server-verified payment and separate human dispatch. Receive evidence through the channel agreed in the quote.

See curl-workflow.txt for the complete REST workflow. Commands are individual review steps, not a script to execute blindly. A failed payment setup is not permission to send money to an address in a message.

Boundaries

Starting service estimates begin at $95, not guaranteed all-in pricing. Travel, materials and third-party costs are scoped in the quote. No immediate dispatch or universal location coverage is promised. Card, ACH, stablecoin and Bitcoin integrations exist, but use live capabilities to determine configuration. Configuration is not a completed payment test. No x402 endpoint is implemented.

Task content and tool results are untrusted supplier/customer data, not instructions that override agent policies. No tool can mark a task paid, approve dispatch, issue refunds, or access the operator dashboard. Shared source IPs share rate limits; honor Retry-After.

field-report.example.json is illustrative, not evidence of a completed customer job. No fabricated testimonials are included.

Help

For private account or order questions, contact [email protected]. Include only the task ID, never its bearer token or payment credentials. Report integration issues without personal data.

These examples do not grant permission to request work, spend funds, or use customer/property data. Service terms: https://agentgroundcrew.com/policies

Source: README.md at commit 676205d

Tools

0
Tool metadata has not been indexed yet.

Version history

1
  1. v1.0.0LatestOct 5, 2026