Tools
Import from getMCP Manifest
Round-trip a manifest produced by the export endpoint into a server.
POST
Counterpart to
POST /tools/export. Takes a manifest object (with the getmcp/tools-v1 envelope, or a bare tools[] array) and creates the listed tools on the target server in a single round-trip — no two-phase confirmation step.
Slug collisions default to skip (the existing tool is left alone and the candidate appears in
skipped[]). Pass on_conflict: "duplicate" to let ToolManager auto-suffix the new slug instead.Hard cap of 1000 tools per import. Larger manifests return
413 Payload Too Large — split the upload into multiple smaller manifests if you hit this.Path Parameters
string
required
The UUID of the server to import into (e.g.
836995ae-1cff-41ec-823e-a4f07ccca3a0). Numeric IDs are also accepted for backwards compatibility.Body Parameters
string
Manifest format identifier. Must start with
getmcp/tools-v (e.g. getmcp/tools-v1). Optional — bare arrays without an envelope are also accepted.string
Optional ISO 8601 timestamp from the source manifest. Carried through for traceability; not validated.
object
Optional
{ name, slug } block from the source server. Carried through for traceability; not used to override the target.array
required
Array of tool objects produced by the export endpoint. Each entry uses the same shape as the export manifest:
name, slug, description, endpoint_url, http_method, input_schema, parameter_mapping, response_mapping, headers, timeout, cache_ttl, retry_count, retry_backoff, rate_limit_per_min, status, tags, sort_order. The name field is required per row.string
default:"skip"
How to handle slug collisions. One of:
skip (default — record goes into skipped[]), duplicate (auto-suffix the slug).
