# Local installation and MCP registration

Extract the package, open a terminal in its root, run npm ci --ignore-scripts, npm test, npm run smoke and npm run doctor. Node22+ and installed Microsoft Edge are required. Edge is selected with browserChannel msedge. Dependency versions and transitive hashes are locked by package-lock.json. No post-install script or remote bootstrap script runs.

Run npm run login, complete Siemens ID in the dedicated window, press Enter to check authentication and close it. Browser interaction is needed initially and on MFA/session renewal. Headless use begins after that; it is not a client-credentials OAuth flow. Stop the MCP before login, discovery or another kit instance uses the same profile.

Run npm run discover -- catalog <authorized-UUID> (or project) after login. Populate config.local.json with the returned context object. Delete unused synthetic example entries by editing your new local config, not by deleting remote objects. defaultCatalogId must refer to one configured catalog. Configured identity includes name, templateId, snapshotId and primary author; native checks reject unexpected changes. The business adapter also rejects read-only contexts. Catalog import additionally checks ownership and editing mode.

## Generic MCP host JSON

Replace every path below with the absolute path on the recipient's machine. This is a local stdio command, not an HTTP MCP URL.

```json
{"mcpServers":{"solutionlink":{"command":"node","args":["C:/AgentTools/solutionlink-mcp/src/server.mjs"],"env":{"SOLUTIONLINK_CONFIG":"C:/AgentTools/solutionlink-mcp/config.local.json"}}}}
```

## Codex TOML equivalent

```toml
[mcp_servers.solutionlink]
command = "node"
args = ["C:/AgentTools/solutionlink-mcp/src/server.mjs"]
[mcp_servers.solutionlink.env]
SOLUTIONLINK_CONFIG = "C:/AgentTools/solutionlink-mcp/config.local.json"
```

Merge the entry into your existing MCP configuration without overwriting other servers. These examples describe file formats; your agent host may offer a registration UI. Reload the entry, list the 16 tools, call solutionlink_list_contexts, solutionlink_auth_status and an authorized native read. Never enable a public HTTP listener around this local authenticated adapter without a separately designed authentication/authorization layer.

## Skills

Read skills/solutionlink-authoring/SKILL.md and skills/solutionlink-business-planning/SKILL.md directly, or copy those two folders into your agent's user-owned skill directory. Do not overwrite an existing skill without reviewing differences. They are portable recipes and use only tools exposed here. Both reference package docs using relative paths; if installing them separately, retain a copy of the package docs at the same relative location or update the links.

## First controlled mutation

Use an editable non-production context and a request the user has authorized. Read business state/options, prepare one small explicit change and examine its baseline/preview. Set enableWrites true locally and reload MCP only for authorized work. Apply the prepared plan and read native state again. Keep evidence local. For imports, export before changing, validate the matching owned target and inspect independent after-export content. Import is an overwrite operation, not an additive merge guarantee.