{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"awesome-gotohuman","slug":"gotohuman","name":"gotoHuman","type":"mcp","url":"https://github.com/gotohuman/gotohuman-mcp-server","page_url":"https://unfragile.ai/gotohuman","categories":["mcp-servers"],"tags":[],"pricing":{"model":"open_source","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"awesome-gotohuman__cap_0","uri":"capability://tool.use.integration.mcp.based.human.approval.request.submission.with.dynamic.form.validation","name":"mcp-based human approval request submission with dynamic form validation","description":"Enables AI agents to submit structured approval requests to the gotoHuman platform via the Model Context Protocol, with runtime schema validation against dynamically fetched form definitions. The implementation uses a three-step workflow (list-forms → get-form-schema → request-human-review-with-form) where agents discover available approval workflows, retrieve field schemas for validation, then submit review requests with typed field data and optional user assignments. Requests are processed asynchronously with webhook callbacks, allowing agents to continue execution while awaiting human decisions.","intents":["I want my AI agent to pause and ask a human to approve generated content before proceeding","I need to route approval requests to specific team members based on request metadata","I want to validate that my agent is submitting the correct fields before sending approval requests","I need my agent to continue working on other tasks while waiting for human approval decisions"],"best_for":["AI agent developers building approval workflows in Cursor, Claude, or Windsurf IDEs","Teams automating content generation with human-in-the-loop safeguards","Developers integrating gotoHuman approval platform into MCP-compatible applications"],"limitations":["Asynchronous pattern requires webhook infrastructure on client side to receive approval responses","Form schema must be pre-configured in gotoHuman platform; no runtime schema definition from agent","Field validation happens client-side; server-side validation errors only returned after submission","No built-in retry logic for failed submissions or webhook delivery failures"],"requires":["Node.js runtime (any version supporting TypeScript transpilation)","Valid GOTOHUMAN_API_KEY environment variable from gotoHuman account","MCP-compatible IDE with stdio transport support (Cursor, Claude, Windsurf)","Pre-configured approval forms in gotoHuman platform dashboard"],"input_types":["formId (string identifier)","fieldData (object with dynamic schema-defined fields)","metadata (object for workflow correlation)","assignToUsers (array of user identifiers)"],"output_types":["Review link (URL to gotoHuman approval interface)","Review ID (for webhook correlation)","Approval/rejection response (via webhook callback)"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-gotohuman__cap_1","uri":"capability://data.processing.analysis.dynamic.form.schema.discovery.and.retrieval.for.approval.workflows","name":"dynamic form schema discovery and retrieval for approval workflows","description":"Provides agents with runtime access to form field schemas from the gotoHuman platform via the get-form-schema tool, enabling validation of required fields, field types, and constraints before submission. The implementation fetches schema definitions from the remote gotoHuman API keyed by formId, allowing agents to understand approval workflow requirements without hardcoding field definitions. Schemas include field metadata (type, required status, validation rules) that agents can use for client-side validation or to prompt users for missing data.","intents":["I want to know what fields are required for a specific approval form before submitting","I need to validate my data against the form schema to catch errors early","I want to dynamically generate prompts or UI based on form field requirements","I need to understand field types and constraints to format data correctly"],"best_for":["Agents building dynamic approval request payloads based on form requirements","Developers implementing client-side validation before submission","Teams managing multiple approval workflows with varying field requirements"],"limitations":["Schema is fetched per-request; no caching mechanism built into the MCP server","Schema changes on gotoHuman platform are immediately reflected but agents may cache old schemas in memory","No schema versioning support; agents cannot request specific schema versions","Complex nested field types or conditional field logic not documented in schema response format"],"requires":["Valid GOTOHUMAN_API_KEY environment variable","formId that exists in the gotoHuman account","Network connectivity to gotoHuman API endpoint"],"input_types":["formId (string identifier for the approval form)"],"output_types":["Schema object (JSON with field definitions, types, constraints, required status)"],"categories":["data-processing-analysis","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-gotohuman__cap_2","uri":"capability://search.retrieval.available.approval.form.enumeration.and.discovery","name":"available approval form enumeration and discovery","description":"Exposes the list-forms tool that returns all approval forms configured in the gotoHuman account, including metadata such as form names, descriptions, and IDs. This enables agents to discover available approval workflows at runtime without hardcoding form identifiers. The implementation queries the gotoHuman API to retrieve the complete form catalog, allowing agents to select appropriate forms based on context or present options to users.","intents":["I want my agent to discover what approval workflows are available in our gotoHuman account","I need to list all forms so users can choose which approval workflow to use","I want to dynamically select the right form based on content type or context","I need to understand what forms exist before requesting approvals"],"best_for":["Agents that need to support multiple approval workflows without hardcoding form IDs","Interactive systems where users select approval workflows from available options","Teams managing evolving approval processes with new forms added over time"],"limitations":["Returns all forms in the account; no filtering by category, team, or permission level","No pagination support; assumes form count is manageable in a single response","Form metadata is read-only; agents cannot create or modify forms via this tool","No caching; each call queries the gotoHuman API, adding latency"],"requires":["Valid GOTOHUMAN_API_KEY environment variable","At least one form configured in the gotoHuman account","Network connectivity to gotoHuman API endpoint"],"input_types":[],"output_types":["Array of form objects (each containing formId, name, description, metadata)"],"categories":["search-retrieval","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-gotohuman__cap_3","uri":"capability://automation.workflow.asynchronous.human.approval.workflow.orchestration.with.webhook.callbacks","name":"asynchronous human approval workflow orchestration with webhook callbacks","description":"Implements an asynchronous human-in-the-loop pattern where approval requests are submitted to gotoHuman and processed independently, with results returned via webhook callbacks rather than blocking the agent. The architecture decouples request submission from approval decision, allowing agents to continue executing other tasks while humans review content. Webhook responses include metadata for workflow correlation (review ID, form ID, approval status), enabling agents to match responses to original requests and trigger downstream actions.","intents":["I want my agent to submit an approval request and continue working without waiting for human response","I need to correlate webhook approval responses back to the original requests my agent submitted","I want to trigger different downstream actions based on approval or rejection decisions","I need my agent to handle approval workflows that may take hours or days to complete"],"best_for":["Long-running agent workflows where blocking on human approval is inefficient","Systems processing high volumes of approval requests with variable response times","Teams where approval decisions are made asynchronously by different people"],"limitations":["Requires client-side webhook infrastructure to receive approval responses; MCP server does not provide webhook endpoint","No built-in webhook retry logic; failed deliveries require manual recovery","No webhook signature verification built into MCP server; clients must implement their own validation","Webhook delivery is not guaranteed; no persistence of failed deliveries in MCP server","Agents must implement their own state management to correlate requests with responses"],"requires":["Valid GOTOHUMAN_API_KEY environment variable","Webhook endpoint configured in gotoHuman account settings","Network connectivity from gotoHuman platform to agent's webhook receiver","Client-side webhook handler implementation to process approval responses"],"input_types":["formId, fieldData, metadata, assignToUsers (for initial request submission)"],"output_types":["Review link (immediate response)","Webhook callback with approval/rejection status (asynchronous)"],"categories":["automation-workflow","planning-reasoning"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-gotohuman__cap_4","uri":"capability://tool.use.integration.mcp.protocol.stdio.transport.integration.for.ide.native.agent.communication","name":"mcp protocol stdio transport integration for ide-native agent communication","description":"Implements the Model Context Protocol (MCP) using stdio transport, enabling the gotoHuman server to communicate with AI agents running in IDE environments (Cursor, Claude, Windsurf) via standard input/output streams. The implementation uses MCP's standardized message format for tool discovery, invocation, and response handling, allowing IDEs to automatically expose gotoHuman tools to agents without custom integration code. Stdio transport provides a lightweight, process-based communication channel that works within IDE sandboxes and doesn't require network ports.","intents":["I want to use gotoHuman approval tools directly in my IDE without external API calls","I need my IDE's AI agent to discover and call gotoHuman tools automatically","I want to integrate gotoHuman into my IDE workflow without custom server setup","I need approval workflows to work seamlessly within Cursor, Claude, or Windsurf"],"best_for":["Developers using MCP-compatible IDEs (Cursor, Claude, Windsurf) for agent development","Teams wanting zero-configuration gotoHuman integration via npx","Workflows where approval requests are initiated from within IDE editing sessions"],"limitations":["Stdio transport is process-based; each IDE session spawns a separate MCP server instance","No inter-process state sharing; multiple IDE windows cannot share approval request history","Stdio communication is synchronous at the transport layer; long-running operations block the stream","IDE-specific MCP client implementations may have different tool discovery or invocation semantics","No built-in logging or debugging output on stdio; errors must be captured via IDE's MCP debugging tools"],"requires":["Node.js runtime installed on developer machine","MCP-compatible IDE (Cursor, Claude, or Windsurf) with stdio transport support","IDE configured with MCP client settings pointing to @gotohuman/mcp-server","GOTOHUMAN_API_KEY environment variable accessible to IDE process"],"input_types":["MCP tool invocation messages (JSON-RPC format)"],"output_types":["MCP tool response messages (JSON-RPC format with results or errors)"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-gotohuman__cap_5","uri":"capability://automation.workflow.zero.installation.npx.based.server.deployment.for.immediate.ide.integration","name":"zero-installation npx-based server deployment for immediate ide integration","description":"Provides a zero-installation deployment model where developers can run the gotoHuman MCP server directly via npx without local installation, automatically downloading and executing version 0.1.2 from the NPM registry. The implementation packages the TypeScript-compiled server as an npm executable, allowing IDEs to invoke the server on-demand via npx command in MCP client configuration. This approach eliminates dependency management, version conflicts, and local setup complexity, enabling developers to integrate gotoHuman into their IDE workflow in seconds.","intents":["I want to use gotoHuman in my IDE without installing dependencies locally","I need to quickly test gotoHuman approval workflows without project setup","I want my team to use the same gotoHuman version without version management","I need to update gotoHuman automatically when new versions are released"],"best_for":["Individual developers wanting quick gotoHuman integration without setup overhead","Teams using multiple IDEs or machines where local installation is impractical","Rapid prototyping scenarios where setup time should be minimal"],"limitations":["First invocation downloads the npm package, adding ~5-10 second startup latency","Requires internet connectivity to NPM registry; offline use is not supported","npx caches packages locally; cache invalidation may cause unexpected version mismatches","No local source code access for debugging; developers must rely on IDE's MCP debugging tools","Updates to @gotohuman/mcp-server require clearing npx cache or waiting for cache expiration"],"requires":["Node.js and npm installed on developer machine","Internet connectivity to NPM registry (npmjs.com)","MCP-compatible IDE with npx command support in MCP client configuration","GOTOHUMAN_API_KEY environment variable accessible to IDE process"],"input_types":[],"output_types":["Running MCP server process with stdio transport"],"categories":["automation-workflow","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-gotohuman__cap_6","uri":"capability://safety.moderation.environment.based.api.authentication.with.gotohuman.api.key","name":"environment-based api authentication with gotohuman_api_key","description":"Implements API authentication by reading the GOTOHUMAN_API_KEY from the environment at server startup, using it to authorize all subsequent requests to the gotoHuman platform API. The implementation stores the API key in memory for the lifetime of the MCP server process, eliminating the need to pass credentials with each tool invocation. This approach follows the twelve-factor app pattern for credential management, allowing developers to configure authentication via environment variables without modifying code or configuration files.","intents":["I want to authenticate my agent with gotoHuman without hardcoding API keys","I need to use different API keys for different environments (dev, staging, prod)","I want my IDE to automatically use my gotoHuman credentials without manual configuration","I need to rotate API keys without redeploying or reconfiguring the MCP server"],"best_for":["Developers using environment-based configuration management","Teams managing multiple gotoHuman accounts or API keys per environment","Workflows where API keys are injected by CI/CD or container orchestration"],"limitations":["API key is stored in memory; no encryption at rest in the MCP server process","No key rotation support; changing GOTOHUMAN_API_KEY requires restarting the MCP server","No audit logging of API key usage; requests are authenticated but not logged","Invalid API keys are only detected on first API call; no validation at server startup","API key is accessible to any code running in the MCP server process; no isolation"],"requires":["GOTOHUMAN_API_KEY environment variable set before MCP server startup","Valid API key generated from gotoHuman account dashboard","Environment variable accessible to the IDE process spawning the MCP server"],"input_types":["GOTOHUMAN_API_KEY environment variable (string)"],"output_types":["Authenticated API requests to gotoHuman platform"],"categories":["safety-moderation","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-gotohuman__cap_7","uri":"capability://tool.use.integration.multi.ide.compatibility.via.standardized.mcp.protocol.implementation","name":"multi-ide compatibility via standardized mcp protocol implementation","description":"Implements the Model Context Protocol (MCP) specification in a way that enables the gotoHuman server to work across multiple IDE environments (Cursor, Claude, Windsurf) without IDE-specific code. The implementation uses MCP's standardized tool definition format, message schema, and stdio transport, allowing any MCP-compatible IDE to discover and invoke gotoHuman tools. This approach decouples the server from IDE-specific APIs, enabling a single server binary to serve multiple IDE clients with different tool invocation patterns.","intents":["I want to use gotoHuman approval tools in Cursor, Claude, and Windsurf without different integrations","I need my team to use gotoHuman regardless of which IDE they prefer","I want to switch IDEs without losing access to gotoHuman approval workflows","I need a single gotoHuman integration that works across our team's diverse IDE choices"],"best_for":["Teams using multiple MCP-compatible IDEs with different preferences","Organizations standardizing on MCP protocol for tool integrations","Developers wanting IDE-agnostic approval workflow automation"],"limitations":["IDE-specific MCP client implementations may have different tool discovery semantics","Some IDEs may not support all MCP features (e.g., resource subscriptions, sampling)","Tool invocation latency varies by IDE's MCP client implementation","Error handling and timeout behavior differs across IDE MCP implementations","No IDE-specific optimizations; server treats all MCP clients identically"],"requires":["MCP-compatible IDE (Cursor, Claude, Windsurf, or other MCP client)","IDE configured with MCP server settings pointing to gotoHuman server","Node.js runtime for executing the MCP server","GOTOHUMAN_API_KEY environment variable"],"input_types":["MCP tool invocation messages (standardized JSON-RPC format)"],"output_types":["MCP tool response messages (standardized JSON-RPC format)"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":33,"verified":false,"data_access_risk":"high","permissions":["Node.js runtime (any version supporting TypeScript transpilation)","Valid GOTOHUMAN_API_KEY environment variable from gotoHuman account","MCP-compatible IDE with stdio transport support (Cursor, Claude, Windsurf)","Pre-configured approval forms in gotoHuman platform dashboard","Valid GOTOHUMAN_API_KEY environment variable","formId that exists in the gotoHuman account","Network connectivity to gotoHuman API endpoint","At least one form configured in the gotoHuman account","Webhook endpoint configured in gotoHuman account settings","Network connectivity from gotoHuman platform to agent's webhook receiver"],"failure_modes":["Asynchronous pattern requires webhook infrastructure on client side to receive approval responses","Form schema must be pre-configured in gotoHuman platform; no runtime schema definition from agent","Field validation happens client-side; server-side validation errors only returned after submission","No built-in retry logic for failed submissions or webhook delivery failures","Schema is fetched per-request; no caching mechanism built into the MCP server","Schema changes on gotoHuman platform are immediately reflected but agents may cache old schemas in memory","No schema versioning support; agents cannot request specific schema versions","Complex nested field types or conditional field logic not documented in schema response format","Returns all forms in the account; no filtering by category, team, or permission level","No pagination support; assumes form count is manageable in a single response","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.05,"quality":0.41,"ecosystem":0.3,"match_graph":0.25,"freshness":0.9,"weights":{"adoption":0.25,"quality":0.25,"ecosystem":0.15,"match_graph":0.23,"freshness":0.12}},"observed_outcomes":{"matches":0,"success_rate":0,"avg_confidence":0,"top_intents":[],"last_matched_at":null},"maintenance":{"status":"active","updated_at":"2026-05-24T12:16:20.440Z","last_scraped_at":"2026-05-03T14:00:15.503Z","last_commit":null},"community":{"stars":null,"forks":null,"weekly_downloads":null,"model_downloads":null,"model_likes":null}},"distribution":{"claim_url":"https://unfragile.ai/submit?claim=gotohuman","compare_url":"https://unfragile.ai/compare?artifact=gotohuman"}},"signature":"qqAIwTQZX2PKOpF8j8U2DGhvHzjSXUCZQQiIvZyjg/gBmLhKjUMtbqGV78pLeuI8UHzyz/gr3sruhK/fyIx6CQ==","signedAt":"2026-06-15T22:07:10.477Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/gotohuman","artifact":"https://unfragile.ai/gotohuman","verify":"https://unfragile.ai/api/v1/verify?slug=gotohuman","publicKey":"https://unfragile.ai/api/v1/trust-passport-public-key","spec":"https://unfragile.ai/trust","schema":"https://unfragile.ai/schema.json","docs":"https://unfragile.ai/docs"}}