Maturity: Scaffold / Planned — no supported MCP server package or tool manifest exists yet.
CoreLink MCP Server is the planned Model Context Protocol boundary for AI-assisted, tenant-safe CoreLink workflows. It must consume versioned public CoreLink contracts and preserve the same authorization/tenant boundaries as other clients.
This repository currently contains documentation only. There is no server implementation, distributable package, authentication flow, or supported tool surface.
Subject to accepted MCP security and contract gates:
- discover public CoreLink contract/documentation revisions;
- read authorized tenant-scoped devices and lifecycle state;
- read supported telemetry/location summaries only when those public contracts are accepted;
- return canonical CoreLink IDs and maturity/version metadata.
State-changing tools are a separate Post-Beta/security-gated capability. They require a named product use case, explicit consent/confirmation semantics, least-privilege authorization, idempotency/recovery where applicable, and audit evidence. They are not required for the read-only MCP release candidate.
Every supported tool must:
- resolve actor, tenant and authorization server-side;
- fail closed on insufficient scope and cross-tenant access;
- never turn provider/internal credentials into a public bypass;
- avoid exposing secrets or provider-specific IDs/payloads;
- use explicit consent for sensitive/mutating actions;
- emit audit evidence without leaking credentials;
- map inputs/outputs to version-identifiable CoreLink public contracts.
Prompt/tool instructions cannot grant privileges the caller does not already have.
- MCP-01 — tenant/authorization/consent/audit threat model.
- MCP-02 — read-only contract/docs/device/telemetry tools.
- MCP-03 — separately gated state-changing tools.
- MCP-04 — package/version/sandbox compatibility.
Installation/configuration examples will be published only after a real package and supported authentication/tool boundary exist.