npm.io
0.4.0 • Published 4d ago

cesium-mcp-contracts

Licence
MIT
Version
0.4.0
Deps
0
Size
182 kB
Vulns
0
Weekly
0
Stars
119

cesium-mcp-contracts

Transport-neutral Cesium tool contracts shared by browser agents, WebMCP adapters, and model function-calling integrations.

The package contains names, titles, English and Chinese descriptions, localized parameter hints, JSON input schemas, JSON output schemas, and behavioral annotations. It does not depend on CesiumJS, Zod, MCP SDKs, browser APIs, or any transport.

Install

npm install cesium-mcp-contracts

Usage

import {
  cesiumBrowserToolsets,
  selectCesiumToolContracts,
} from 'cesium-mcp-contracts'

const tools = selectCesiumToolContracts(['view', 'entity', 'layer'])
for (const tool of tools) {
  console.log(tool.title, tool.annotations)
  console.log(tool.localizations['zh-CN'].description)
  console.log(tool.inputSchema, tool.outputSchema)
}

console.log(cesiumBrowserToolsets.animation.description)

cesiumBrowserToolsetDefinitions, cesiumSharedToolNames, and each contract's metadata and JSON Schema are canonical for protocol adapters. The MCP runtime converts the same input schemas to Zod at registration time; WebMCP publishes them directly. Runtime-only credential tools and MCP discovery meta-tools remain outside this shared browser-safe inventory. normalizeCesiumToolLocale() maps an environment or application locale to the supported en or zh-CN catalogs.

Selections can be core (15 lightweight contracts), all (61 browser-safe contracts), one toolset name, or an array of toolset names. The 12 domain toolsets mirror the runtime capability groups. Sixty contracts execute directly through the Bridge; geocode is an application-provided browser service. setIonToken is intentionally excluded because page agents must not receive application credentials.

Consumers are responsible for adapting these contracts to their protocol or model provider. Execution remains outside this package.

CesiumJS compatibility

This package is transport-neutral and does not depend on CesiumJS directly. Executable compatibility is defined by cesium-mcp-bridge, currently tested with the peer dependency cesium@~1.143.0. A newer official CesiumJS release is reviewed before the Bridge baseline and affected contracts are updated; contracts do not automatically claim compatibility with every latest release.

Keywords