mcp-scripting

Write ordinary JavaScript using loops and Promise utilities, then pass the source as the code argument to mcpScript. Inside the script, use tools.search to find tools, tools.describe to inspect schemas, and tools.call to invoke them with error handling on each result.

Use mcpScript for multi-call work involving loops, filtering, chaining, or fan-out between calls. Use the plain mcp tool for a single search, describe, status check, auth action, or one tool call.

Each tools.call resolves to either { ok: true, data } or { ok: false, error }, so check the ok flag and return or branch on failures. Failed calls do not stop the script, so explicit handling is required.

The tools object is a non-enumerable proxy, so enumeration methods like Object.keys throw by design. Always use tools.search for discovery instead of inspecting the proxy directly.

The default script timeout is 30 seconds, after which the worker is terminated, including for infinite loops. Design scripts to complete within this window and avoid unbounded iteration.

Use bracket syntax such as tools["server_tool-name"](args) for hyphenated flat paths. If a path collides with reserved names like search, call, describe, or then, invoke it via tools.call("exact-path", args).