Invoke — hire a human from your AI agent (first post free)
by invoke.nanocorp.appapp.nanocorp.invoke/human-tasksv0.1.4
Let your AI agent hire a human for tasks it can't do — first post free.
- Remote endpoint
Uptime
Checked · every day
100%from 5 days of checks
Up without downtime on 5 of 5 days with data.
- No downtime
- Degraded
- Down over 5 minutes
- No data
- Not checked yet
Response time
Median 1901 ms, slowest 5% 2584 ms for the handshake and the tool list, over 30 days.
How far each check got
- Reached the address 100%
- Completed the handshake 100%
- Listed its tools 100%
3 tools at the last answer.
Every day
| Day | Result | Checks | Median |
|---|---|---|---|
| 4 Nov (today) | No downtime | 1 | 1577 ms |
| 3 Nov | No downtime | 1of 1 | 2179 ms |
| 2 Nov | No downtime | 1of 1 | 2160 ms |
| 1 Nov | No downtime | 1of 1 | 1883 ms |
| 31 Oct | No downtime | 2 | 1884 ms |
A failure counts as down time only when a second check five minutes later fails too. How we check
Connect to the publisher's own endpoint
Paste into Settings › Connectors › Add custom connector:
https://invoke.nanocorp.app/mcp Run in a terminal:
claude mcp add --transport http human-tasks https://invoke.nanocorp.app/mcp Add to ~/.cursor/mcp.json:
Add to ~/.config/devin/mcp_config.json:
Add to mcp.json (Program › Install › Edit mcp.json):
Add to config.json in oterm's data folder (~/Library/Application Support/oterm on macOS, ~/.local/share/oterm on Linux, %APPDATA%\oterm on Windows):
Add to ~/.bob/settings/mcp.json (global) or .bob/mcp.json (project):
Add to ~/.config/eca/config.json (global) or .eca/config.json in the project:
Add to ~/.kiro/settings/mcp.json (user) or .kiro/settings/mcp.json (workspace):
Add to ~/.kiro/settings/mcp.json (user) or .kiro/settings/mcp.json (workspace):
{
"mcpServers": {
"human-tasks": {
"url": "https://invoke.nanocorp.app/mcp"
}
}
} Add to .vscode/mcp.json:
{
"servers": {
"human-tasks": {
"type": "http",
"url": "https://invoke.nanocorp.app/mcp"
}
}
} Add to ~/.config/zed/settings.json:
{
"context_servers": {
"human-tasks": {
"url": "https://invoke.nanocorp.app/mcp"
}
}
} Add to cline_mcp_settings.json (MCP Servers › Configure › Configure MCP Servers):
{
"mcpServers": {
"human-tasks": {
"type": "streamableHttp",
"url": "https://invoke.nanocorp.app/mcp"
}
}
} Add to ~/.continue/config.yaml:
mcpServers:
- name: "human-tasks"
type: streamable-http
url: "https://invoke.nanocorp.app/mcp" Add to ~/.config/goose/config.yaml:
extensions:
"human-tasks":
type: streamable_http
name: "human-tasks"
enabled: true
uri: "https://invoke.nanocorp.app/mcp"
headers: {}
env_keys: []
envs: {}
timeout: 300 Add to ~/.gemini/settings.json:
{
"mcpServers": {
"human-tasks": {
"httpUrl": "https://invoke.nanocorp.app/mcp"
}
}
} Run in a terminal:
codex mcp add human-tasks --url https://invoke.nanocorp.app/mcp Add to ~/.llm/config.json:
Add to resources/assets/config/mcp.json in the installed app:
Add to ~/.boltai/mcp.json:
{
"mcpServers": {
"human-tasks": {
"url": "https://invoke.nanocorp.app/mcp"
}
}
} This server's endpoint speaks streamable HTTP, which this client's documentation does not list among its transports; use another client for it.
Add to ~/.config/agenvoy/mcp.json:
{
"servers": {
"human-tasks": {
"url": "https://invoke.nanocorp.app/mcp"
}
}
} Add to ~/.config/amp/settings.json (user) or .amp/settings.json (workspace):
{
"amp.mcpServers": {
"human-tasks": {
"url": "https://invoke.nanocorp.app/mcp"
}
}
} Add to anythingllm_mcp_servers.json in the AnythingLLM storage plugins directory:
{
"mcpServers": {
"human-tasks": {
"type": "streamable",
"url": "https://invoke.nanocorp.app/mcp"
}
}
} Add to Augment Settings Panel – MCP section – Import from JSON (VS Code extension):
{
"mcpServers": {
"human-tasks": {
"type": "http",
"url": "https://invoke.nanocorp.app/mcp"
}
}
} For agents: the install prompt
Every step above as one Markdown text, for an assistant installing it for you.
# Install the MCP server Invoke — hire a human from your AI agent (first post free) (`app.nanocorp.invoke/human-tasks`)
Its page: https://plug.directory/servers/app.nanocorp.invoke/human-tasks
It runs on the publisher's servers; the client connects to its URL.
Use the section for the person's client.
## Claude Desktop
Paste into Settings › Connectors › Add custom connector:
```text
https://invoke.nanocorp.app/mcp
```
## Claude Code
Run in a terminal:
```sh
claude mcp add --transport http human-tasks https://invoke.nanocorp.app/mcp
```
## Cursor, Devin Desktop, LM Studio, oterm, Bob Shell, ECA, Kiro, Kiro CLI
Merge into the place for the person's client:
- Cursor: ~/.cursor/mcp.json
- Devin Desktop: ~/.config/devin/mcp_config.json
- LM Studio: mcp.json (Program › Install › Edit mcp.json)
- oterm: config.json in oterm's data folder (~/Library/Application Support/oterm on macOS, ~/.local/share/oterm on Linux, %APPDATA%\oterm on Windows)
- Bob Shell: ~/.bob/settings/mcp.json (global) or .bob/mcp.json (project)
- ECA: ~/.config/eca/config.json (global) or .eca/config.json in the project
- Kiro: ~/.kiro/settings/mcp.json (user) or .kiro/settings/mcp.json (workspace)
- Kiro CLI: ~/.kiro/settings/mcp.json (user) or .kiro/settings/mcp.json (workspace)
```json
{
"mcpServers": {
"human-tasks": {
"url": "https://invoke.nanocorp.app/mcp"
}
}
}
```
## VS Code
Merge into .vscode/mcp.json:
```json
{
"servers": {
"human-tasks": {
"type": "http",
"url": "https://invoke.nanocorp.app/mcp"
}
}
}
```
## Zed
Merge into ~/.config/zed/settings.json:
```json
{
"context_servers": {
"human-tasks": {
"url": "https://invoke.nanocorp.app/mcp"
}
}
}
```
## Cline
Merge into cline_mcp_settings.json (MCP Servers › Configure › Configure MCP Servers):
```json
{
"mcpServers": {
"human-tasks": {
"type": "streamableHttp",
"url": "https://invoke.nanocorp.app/mcp"
}
}
}
```
## Continue
Merge into ~/.continue/config.yaml:
```yaml
mcpServers:
- name: "human-tasks"
type: streamable-http
url: "https://invoke.nanocorp.app/mcp"
```
## Goose
Merge into ~/.config/goose/config.yaml:
```yaml
extensions:
"human-tasks":
type: streamable_http
name: "human-tasks"
enabled: true
uri: "https://invoke.nanocorp.app/mcp"
headers: {}
env_keys: []
envs: {}
timeout: 300
```
## Gemini CLI
Merge into ~/.gemini/settings.json:
```json
{
"mcpServers": {
"human-tasks": {
"httpUrl": "https://invoke.nanocorp.app/mcp"
}
}
}
```
## Codex
Run in a terminal:
```sh
codex mcp add human-tasks --url https://invoke.nanocorp.app/mcp
```
## mcp-client-cli, TUUI, BoltAI
This server's endpoint speaks streamable HTTP, which this client's documentation does not list among its transports; use another client for it.
## Agenvoy
Merge into ~/.config/agenvoy/mcp.json:
```json
{
"servers": {
"human-tasks": {
"url": "https://invoke.nanocorp.app/mcp"
}
}
}
```
## Amp
Merge into ~/.config/amp/settings.json (user) or .amp/settings.json (workspace):
```json
{
"amp.mcpServers": {
"human-tasks": {
"url": "https://invoke.nanocorp.app/mcp"
}
}
}
```
## AnythingLLM
Merge into anythingllm_mcp_servers.json in the AnythingLLM storage plugins directory:
```json
{
"mcpServers": {
"human-tasks": {
"type": "streamable",
"url": "https://invoke.nanocorp.app/mcp"
}
}
}
```
## Augment Code
Merge into Augment Settings Panel – MCP section – Import from JSON (VS Code extension):
```json
{
"mcpServers": {
"human-tasks": {
"type": "http",
"url": "https://invoke.nanocorp.app/mcp"
}
}
}
```
Then restart the client, or reload its MCP servers, and ask it to list the server's tools to confirm it started.
From the publisher's entry in the Official MCP Registry (the registry entry). Report a problem