The official MCP Server for the Influship API
At MCP runtime, the enabled execute tool sends submitted code, intent, the Influship API key, and supplied upstream client environment values to a Stainless-hosted endpoint. It also offers a local mode that dynamically evaluates submitted TypeScript in a Deno worker.
Package source references dynamic require/import behavior.
instructions.jsView on unpkg · L7Source sends credentials or rich application records to a package-controlled external receiver enabled by default.
code-tool.mjsView on unpkg · L98Tarball package.json differs from the npm registry version manifest for scripts or dependency sets.
package.jsonView on unpkgPackage manifest contains a dependency pinned to a remote tarball URL.
package.jsonView on unpkgDefault MCP execute tool runs submitted code in a Stainless-hosted sandbox.
options.jsView on unpkg · L30Package source references dynamic require/import behavior.
instructions.jsView on unpkg · L7Source sends credentials or rich application records to a package-controlled external receiver enabled by default.
code-tool.mjsView on unpkg · L98Tarball package.json differs from the npm registry version manifest for scripts or dependency sets.
package.jsonView on unpkg · L227Package manifest contains a dependency pinned to a remote tarball URL.
package.jsonView on unpkg · L227Default MCP execute tool runs submitted code in a Stainless-hosted sandbox.
options.jsView on unpkg · L30