Invoke Human Tool

com.invokehumantoolPublished by invokehumantool.comOfficial publisherv1.0.0Updated Oct 26, 2026

Ask a person on an Apple device or in a browser, then read their answer.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Remote MCP server that lets an assistant ask a person on an Apple device or in a browser and then read their answer.

What you can do
  • Send a question to a person on an Apple device or in a browser.
  • Read the person's answer back into the assistant's context.
  • The manifest lists no individual tools, so the exact operations are not documented beyond this ask-and-read loop.
When to use it
Useful when an assistant needs a human decision, confirmation or piece of information it cannot obtain on its own, and the person can respond on an Apple device or in a browser.
Requirements
A remote streamable HTTP endpoint at invokehumantool.com; no local package or runtime is needed. OAuth authentication is required. No environment variables or custom headers are declared.
Before you install
Questions and answers pass through a third-party hosted service, so avoid sending sensitive content. OAuth grants the server access tied to your account. The manifest lists no tools, so review what it can do before connecting.

Installation

In SourceWeft

  1. Open Invoke Human Tool in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.invokehumantool%2Finvoke-human/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "invoke-human-tool": {
      "type": "http",
      "url": "https://invokehumantool.com/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 26, 2026

Score

75% 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 daysRequired25 pts
  • Auth declaredRequired10 pts
  • 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
  • License10 pts

    Declare a license in the repository or the registry entry.