Solutionlink + eXplore
ENGINEERING HANDOFF / v0.4.0
Agent tools · Source included · Local execution

Give your agent a working connection.

A portable MCP and practical authoring knowledge for the Solutionlink and eXplore team. Install locally, sign in with your own Siemens account, and work in explicitly configured catalogs and projects.

v0.4.0 · 16 MCP tools · 34 synthetic tests · Node.js 22+ / Microsoft Edge
SHA-256 checksum   /   Machine-readable release   /   Verification scope
New / Production integration evidence

Saber eXplore embedding: results and support needed.

Three launch routes tested from deployed S2CD. Read the findings and the request for durable, read-only access scoped only to the Saber 2 project.

Read the support handoff ↗

Connect and inspect

Dedicated browser login, native context discovery, catalog inspection, process/scenario reads and owned solution exports.

Explore the tool surface ↗

Plan and apply

Validated solution imports and prepared TIPS, implementation phases and ROI changes, with baseline guards and native readback.

Read the typed schemas ↗

Build with context

Human-style BPMN, Digital Thread hierarchy, meaningful avatars, tabletop domains, subway maps and billboard recipes.

Read the eXplore guide ↗
Start with your agent

One link. A clear handoff.

Give your agent this instruction. It can fetch the manifest, inspect the source and guide the local setup.

Read https://explore.xcelerator.us/AGENTS.md and its linked setup guide. Download the versioned agent kit from agent.json, verify its checksum, inspect it, and install it in a new local directory. Configure the local stdio MCP for my authorized Solutionlink contexts. Let me complete the dedicated Siemens sign-in when required. Verify native read access before making changes.

From download to native read.

No access to another person's session. The kit runs on your workstation and keeps its dedicated profile and evidence there.

01

Inspect, install, verify

Extract the ZIP, review the source, run npm ci --ignore-scripts, tests and the stdio smoke check.

02

Sign in and discover

Use the dedicated login script. Read identity from your authorized catalog/project URLs and create your local configuration.

03

Register the MCP

Use the supplied JSON or TOML example. Verify context and authentication, then read native state. Writes are disabled by default.

Know what is ready.

CapabilityThis release
Local stdio MCP and offline arithmeticIncluded, independently installed and smoke-tested from the ZIP.
Native imports and business changesTyped tools with guards and evidence. Recipient live access and controlled non-production validation required.
BPMN, scene editing and native billboardsAuthoring guidance included; those write operations are not public MCP tools.
Authenticated 3D iframe embeddingOpen integration work. Vendor startup, framing and SSO contract still needed.

Documentation, ready for people and agents.