get-form-schema
Get the partial schema ('fields' and 'config' (optional) properties) to be used when requesting a human review with the given review template.
LABSCO SUMMARY
An approval request becomes a structured form rather than a message someone has to notice.
Three tools in a fixed order: list the templates, fetch the chosen template's field schema, then submit field data that matches it. The schema call is not optional — the fields are defined on the gotoHuman side, so an agent that guesses at them submits a review nobody can act on. What distinguishes this from a single approve-or-reject callback is the workflow argument: one runId plus prevSteps links several reviews, possibly by different people, into one traceable run. Templates themselves are built in gotoHuman, not here.
What it is
A server for human-in-the-loop review — list the review templates, read the fields one expects, and submit a review request against it.
What you get
- The review templates available on the account, and the exact fields and config a chosen template expects
- A review request carrying field data, a title, assigned users and metadata, so what a reviewer sees is structured rather than a wall of text
- Multi-step chains: the same runId on each step with prevSteps naming the reviews that came before, which ties a sequence of approvals into one run
- A webhook URL per request, for where the decision is delivered
Requirements
GOTOHUMAN_API_KEY, and a gotoHuman account with at least one review template already defined — the field schema comes from the template, so it has to exist before an agent can ask for a review. MIT.
Setup effort
One command plus a key — npx @gotohuman/mcp-server, then supply credentials
USE CASES
01
Getting sign-off before an agent acts
Find the template that matches the decision, read the fields it defines, and submit the agent's output against them addressed to the people who should decide. The webhook carries the answer back.
02
Chaining approvals across a multi-step run
Each step submits its own review against the template it needs, all sharing one runId, with prevSteps naming the reviews already completed — so the second reviewer sees what the first one approved.
3 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
list-forms
List all available review templates. NOTE: You need to fetch the schema for the template fields first using the get-form-schema tool.
request-human-review-with-form
Request a human review with a review template. NOTE: If you don't have a review template ID yet, list all available review templates using the list-forms tool first. To know what to pass for fieldData, you need to fetch the schema for the review template fields using the get-form-schema tool. For multi-step workflows, pass workflow with the same runId on each step and prevSteps listing prior reviewIds; use workflowRunId from the response when gotoHuman assigns a new runId.
BEFORE YOU INSTALL
What to know first
Tools you get
3 tools when we connected.
Requires
- npx on PATH
- GOTOHUMAN_API_KEY in your environment
Where it runs
All 3 documented clients run the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 3 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx @gotohuman/mcp-serverMCP Clients
Cursor, Claude Desktop, Windsurf
JSON
{
"mcpServers": {
"gotoHuman": {
"command": "npx",
"args": [
"-y",
"@gotohuman/mcp-server"
],
"env": {
"GOTOHUMAN_API_KEY": "<YOUR_GOTOHUMAN_API_KEY>"
}
}
}
}
