Platform toolset
The Platform toolset exposes core SnapLogic platform operations to MCP-compatible clients. Use these APIs to run and validate pipelines, discover accounts and assets, create projects and project spaces, manage SLDB files, query Snaplex infrastructure, export projects and pipelines, and save user preferences, all through a standard MCP session.
All Platform toolset endpoints share the base path
/api/1/rest/public/platform_mcp/mcp/platform.
| Platform toolset APIs | |
|---|---|
POST
/platform_mcp/mcp/platform
|
sends a JSON-RPC 2.0 request to the Platform MCP Server using the Platform toolset and returns the response as a Server-Sent Events (SSE) stream. |
GET
/platform_mcp/mcp/platform
|
opens a persistent Server-Sent Events (SSE) stream for receiving server-initiated messages from the SnapLogic MCP Server on the Platform toolset. |
DELETE
/platform_mcp/mcp/platform
|
terminates an active Platform toolset MCP session and releases any associated server-side resources. |
Available tools
After initializing a session, call tools/list to retrieve the
live set of tools. The following 37 tools are available in the Platform toolset,
grouped by function:
Session and organization
| Tool name | Description | Inputs |
|---|---|---|
save_user_preferences |
Save default environment/org, project path, and Snaplex for the session so that subsequent tool calls do not require them explicitly. |
|
refresh_organizations_and_assets_cache |
Force a refresh of the server-side cache of organizations, projects, and assets. Useful after creating or moving assets in SnapLogic Manager. |
|
list_organizations |
List all SnapLogic organizations the authenticated user belongs to.
Returns [{name, id, is_admin}]. Call this first when the
environment/org name is unknown. The name values are what
other tools expect as their org argument. |
None. |
list_groups |
List all groups in an environment/org. Returns the group names available.
Use get_group_details to see a group's members. |
|
get_group_details |
Get details of a specific group in an environment/org, including its
members. Use list_groups to find available group names. |
|
get_user_info |
Look up a SnapLogic user by email address. Returns the user's display
name, first and last name, and org memberships. Use this to look up another
user; use list_organizations for the current authenticated
caller's own orgs. |
|
Account and asset discovery
| Tool name | Description | Inputs |
|---|---|---|
list_accounts |
List accounts under an org or project path. Returns metadata only
(label, path, snode_id, class_id, class_label); never credential
values. Filter by class_id to find accounts compatible
with a given Snap type. |
|
list_assets |
List the assets directly under one directory path. Use
asset_type to narrow results (for example,
Pipeline) or pass comma-separated values (for example,
Dir,PSpace,Project) to list project containers only.
Omit asset_type to return everything under the path.
To search the whole org for one type use
find_assets_by_type. |
|
find_assets_by_type |
Find assets of one type across a project path. Pass
project_path for complete results; omitting it searches
from the org root but coverage depends on the backend search index and
is not guaranteed to be exhaustive. To find Tasks, use
asset_type='Job'. |
|
get_asset_details |
Look up an asset by path. Returns its snode_id and
type. Set detail='full' to also retrieve owner,
timestamps, and the full raw asset record. For the reverse lookup
(snode_id → path) use get_asset_path. |
|
get_asset_path |
Reverse lookup: resolve a snode_id back to its
readable asset path. The inverse of get_asset_details
(path → snode_id). |
|
Project management
| Tool name | Description | Inputs |
|---|---|---|
create_project_space |
Create a project space, the top-level container that holds projects. The
platform also creates the space's shared folder. The new space is
owned by the calling user. If a project space with this name already exists, the
tool returns an error. To create a project inside an existing space, use
create_project. |
|
create_project |
Create a project inside an existing project space. The new project
is owned by the calling user. If the specified project space doesn't exist,
the tool returns an error. Use create_project_space
first. |
|
Snaplex management
| Tool name | Description | Inputs |
|---|---|---|
list_snaplexes |
List all Snaplexes available in the specified org. Use the returned
runtime_path_id with pipeline execution tools
(snaplex_path parameter). To look up a Snaplex by name
or get its node status, use
get_snaplex_details. |
|
get_snaplex_details |
Retrieve Snaplex status, including the nodes running at the time of
the call. jcc_count and fm_count are
the running JCC and FeedMaster nodes, and nodes[],
nodes_down[], and node_status list
them. Call with only org to return every Snaplex in
the organization in one response; supply
snaplex_snode_id or snaplex_name for
a single Snaplex and its configuration. |
|
list_platform_versions |
List current and latest Snaplex platform versions across the SnapLogic fleet. | None. |
Tip: To retrieve all Snaplexes in an organization, call
get_snaplex_details with only org — one call
returns every Snaplex. Avoid calling it once per Snaplex in a loop; the
single-org call is significantly faster on organizations with
many Snaplexes.Note: The single-Snaplex response (with
snaplex_snode_id or snaplex_name) includes the
full Snaplex configuration (full_details). The all-Snaplexes
response omits it to keep the payload small. On organizations with many Snaplexes
the call can take several seconds.Note: A Snaplex with zero running nodes is a valid result:
jcc_count and fm_count return 0. Only a
non-existent snaplex_name or
snaplex_snode_id returns an error.Pipeline operations
| Tool name | Description | Inputs |
|---|---|---|
execute_pipeline |
Execute a pipeline and return the run result. Provide one of
pipeline_name or slp_content. |
|
import_pipeline |
Import a pipeline definition into a SnapLogic project without executing it. |
|
validate_pipeline |
Validate a pipeline against a Snaplex without executing it. Returns validation errors and warnings. |
|
delete_pipeline |
Delete a pipeline from a SnapLogic project. Only pipelines are supported. If a scheduled task references the pipeline, the task stays enabled after deletion. |
|
export_pipeline |
Export a pipeline definition (SLP JSON) by name. Returns the complete pipeline
definition including metadata, which can be passed directly to
import_pipeline. Uses the Export individual
assets API. |
|
export_project |
Export a SnapLogic project as a ZIP archive. The ZIP is written to the project (timestamped) and the response returns a short-lived presigned download URL; the archive content does not pass through the model context. Account assets are opt-in only; when included, the response note warns that the presigned link carries an encrypted credential envelope and must be treated as a secret. Uses the Export a project API. |
|
SLDB file operations
| Tool name | Description | Inputs |
|---|---|---|
list_sldb_files |
List files and folders in SLDB cloud storage. |
|
upload_sldb |
Upload a file to SLDB cloud storage inline. For large files, use
lease_sldb_upload instead to upload directly to
storage without routing file content through the server. |
|
lease_sldb_upload |
Get a presigned S3 upload URL for a file in SLDB cloud storage.
Use the returned URL and headers to PUT the file content directly to
storage, without routing file bytes through the server. Preferred
over upload_sldb for large files. |
Returns: |
download_sldb_file |
Download a file from SLDB cloud storage. Returns a presigned URL by
default; set delivery="content" to return inline
content. |
|
move_sldb_file |
Move or rename a file within SLDB cloud storage. |
|
delete_sldb_file |
Delete a file from SLDB cloud storage. |
|
Runtime monitoring
| Tool name | Description | Inputs |
|---|---|---|
get_execution_status |
Inspect one pipeline run by runtime ID. Returns run state, duration,
documents processed, and error summary (detail="status");
raw server passthrough (detail="raw"); or full snap-level
I/O dump (detail="dump"). |
|
get_execution_logs |
Get execution log entries for a pipeline run. |
|
get_execution_snap_stats |
Get per-snap throughput statistics (documents and bytes per snap) for a pipeline run. |
|
list_executions |
List pipeline executions in an org. Use
phase="running" for active runs or
phase="past" (default) for historical runs with
filtering by pipeline name, project, user, state, or time
range. |
|
list_executions_for_pipeline |
Get execution history for one pipeline. Covers the last 7 days by default. |
|
Health and diagnostics
| Tool name | Description | Inputs |
|---|---|---|
get_runtime_health |
Get org runtime health over a time window. Returns historical pipeline success/failure rates, current execution slot usage, or both. |
|
diagnose_pipeline_failure |
Diagnose recent failures for a pipeline in one call. Fetches the
last N failed runs and returns status, snap statistics, and logs for
each. Replaces the manual chain of
list_executions_for_pipeline →
get_execution_status →
get_execution_logs. |
|
get_org_health_report |
Get an org-wide health snapshot in one call: runtime health, Snaplex inventory, outdated Snaplexes, and API usage limits. |
|
Scheduled tasks
| Tool name | Description | Inputs |
|---|---|---|
get_task_details |
Get details of a scheduled task by snode_id, including its configuration, schedule, and target pipeline. Optionally include execution history and upcoming run times. |
|
Note: Tool calls are logged to the Activity logs (operation metadata only). Audit
log entries include the calling user, tool name, environment, and timestamp.