gotoHuman MCP Server

Created By
andyciggya year ago
Overview

what is gotoHuman MCP Server?

The gotoHuman MCP Server is a tool that facilitates the integration of human approvals into AI workflows, allowing for a human-in-the-loop process in agentic systems.

how to use gotoHuman MCP Server?

To use the gotoHuman MCP Server, install it via npm with the command npx @gotohuman/mcp-server, and configure it with your API key to request human approvals from your AI workflows.

key features of gotoHuman MCP Server?

  • Fully-managed async human-in-the-loop workflow
  • Customizable approval user interface
  • Built-in authentication, webhooks, and notifications
  • Team collaboration features
  • Evolving training dataset for improved performance

use cases of gotoHuman MCP Server?

  1. Integrating human review steps in AI-generated content workflows.
  2. Enhancing decision-making processes in automated systems with human oversight.
  3. Streamlining approval processes in software development environments.

FAQ from gotoHuman MCP Server?

  • Can I use gotoHuman with any AI agent?

Yes! gotoHuman can be integrated with various AI agents and workflows.

  • Is there a cost associated with using gotoHuman MCP Server?

gotoHuman MCP Server is free to use, but may have premium features in the future.

  • How do I get support for gotoHuman MCP Server?

Support can be accessed through the GitHub repository and the official website.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
andyciggy
Star
0
Language
JavaScript
License
MIT license

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago