← usefulapi.io

INDIVIDUAL MCP TOOL

trigger_get_batch_results

Fetch the outcome of every run in a batch.

usefulapi.ionone authenticationAvailability not checked

LIVE ENDPOINT

https://trigger-dev.usefulapi.io/mcp

No auth detected

Connect to this endpoint to inspect the live schema for trigger_get_batch_results and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Inferred read-only · medium confidence · heuristic, not a guarantee.

  • A tool name or description suggests retrieving external content.

Parent server

usefulapi.io

CONNECT 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.trigger-dev-mcp]
url = "https://trigger-dev.usefulapi.io/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "trigger-dev-mcp": {
      "type": "http",
      "url": "https://trigger-dev.usefulapi.io/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: trigger-dev-mcp
Remote MCP URL: https://trigger-dev.usefulapi.io/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": {
    "trigger-dev-mcp": {
      "url": "https://trigger-dev.usefulapi.io/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "trigger-dev-mcp": {
      "type": "http",
      "url": "https://trigger-dev.usefulapi.io/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "trigger-dev-mcp",
  "transport": "streamable-http",
  "url": "https://trigger-dev.usefulapi.io/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

Related tools

  • trigger_list_runs — List task runs, filtered by status, task, tag, queue, schedule or a time window.
  • trigger_get_run — Fetch a single run's outcome — its status, output, error and attempts.
  • trigger_get_run_trace — Fetch the full execution trace of a run — every span, with timings and nesting.
  • trigger_get_run_span — Fetch a single span from a run's trace, with its own logs and attributes.
  • trigger_list_run_events — List the lifecycle events of one run — queued, dequeued, started, retried, completed.
  • trigger_get_run_metadata — Fetch the mutable metadata a run has written about itself — progress, checkpoints and custom state.
  • trigger_list_schedules — List the cron schedules configured for tasks, with their next run times.
  • trigger_get_schedule — Fetch a single schedule with its cron expression, timezone and active state.