Letsclarify Mcp

io.github.heiseePublished by GitHub account heiseev1.0.4Updated Oct 25, 2026

Human-in-the-Loop API: AI agents create forms, share URLs with humans, get JSON back.

VerifiedSTDIODesktop onlyProductivity & Workflow

Overview

AI-generated overview

A local MCP server that lets an AI agent create human-in-the-loop forms, share their URLs, and receive the answers back as JSON.

What you can do
Create forms for a human to fill in on behalf of the agent, using the LetsClarify human-in-the-loop API. Share a form URL so a person can open and complete it. Retrieve the submitted answers back as structured JSON for the agent to continue with.
When to use it
Useful when an agent needs a person to supply information, confirm a choice, or complete a step it cannot do itself, and the result should come back in a machine-readable form.
Requirements
Runs as a local process via the npm package @heisee/letsclarify-mcp over stdio, on desktop only. Requires a LetsClarify API key supplied in the LETSCLARIFY_API_KEY environment variable; the key starts with lc_. Network access to the LetsClarify service is implied.
Before you install
Requires a LetsClarify API key stored in LETSCLARIFY_API_KEY; treat it as a secret. Form contents and submitted answers pass through the third-party LetsClarify service, so avoid putting sensitive data in forms. The server creates forms and shares URLs, which is a write action outside the local machine.

Installation

In SourceWeft

  1. Open Letsclarify Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.4LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.