Productivity
letsclarify.ai
Manage forms, recipients, and submissions with paginated results.
ENDPOINT 1
https://letsclarify.ai/mcp
MCP server metadata
- Name
- letsclarify
- Version
- 1.0.0
LetsClarify: Human-in-the-Loop API for AI Agents. Create forms, share URLs with humans, get structured JSON responses back. Use 'register' first to get an API key, then authenticate all other calls with it.
Known tools 6
get_summaryGet a quick summary of form status: total, submitted, and pending recipient counts.
Inferred read-onlydelete_formPermanently delete a form, all its recipients, submissions, and uploaded files.
Potential side effectsCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.letsclarify]
url = "https://letsclarify.ai/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"letsclarify": {
"type": "http",
"url": "https://letsclarify.ai/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: letsclarify
Remote MCP URL: https://letsclarify.ai/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"letsclarify": {
"url": "https://letsclarify.ai/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"letsclarify": {
"type": "http",
"url": "https://letsclarify.ai/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "letsclarify",
"transport": "streamable-http",
"url": "https://letsclarify.ai/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Trust Data Available
BuiltWith Trust API v2 evidence for letsclarify.ai was fetched 2026-08-03T22:43:36.795Z and is being refreshed.
letsclarify.ai is assessed as Neutral: No suspicious signals found, but no strong positive signal either
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.