P3DF/MCP

Digital-twin interactions through MCP

ClaudeChatGPT

P3DF is an evolving open standard for AI agent digital twins. Proposed MCP tools will support spatial, asset and telemetry queries from Claude and ChatGPT.

Proposed integration · Public MCP server not yet available

Purpose and scope

P3DF defines structured digital-twin context. Model Context Protocol (MCP) provides an interface through which AI applications can request data and invoke tools. The proposed P3DF integration connects these layers so agents can query a building’s spaces, assets, observations and recorded state.

The intended clients include Claude, ChatGPT and other MCP-compatible applications. Client support, account settings and permissions must be verified when the integration is released.

Proposed integration architecture

Claude / ChatGPT / other MCP client
                ↓ authenticated requests
        P3DF MCP server (in development)
                ↓ scoped queries
   P3DF engine / cloud twin database
                ↓
 Spaces · Assets · Observations · Telemetry

The server would return source references, timestamps and available spatial context. An exported package represents recorded state at export; cloud results must identify when an observation was recorded.

Proposed operations

OperationPurpose
List spaces and assetsIdentify rooms, equipment and object relationships.
Retrieve observationsLocate the most recent recorded evidence for an object.
Query telemetryRetrieve asset data for a specified time window.
Inspect navigation constraintsProvide routes, clearances and access conditions to a planner.

Example: locating a book

An agent could query the book’s last recorded location, identify nearby surfaces and rooms, and retrieve navigation constraints. A robot would use that evidence to plan a search and verify the book’s current location. This is a proposed workflow; P3DF does not currently provide a public book-finding integration.

Access and implementation requirements

The proposed initial interface prioritizes scoped, read-only queries. Camera access, personal observations and device actions require separate authorization. Published tool schemas, authentication guidance, validation results and tested client configurations are release requirements. This website does not operate an MCP endpoint.

Protocol and client documentation

Receive project updates

Get release updates or register your interest in shaping the specification.

Newsletter

Subscribe to P3DF updates

Enter your email for updates on P3DF releases, research and community progress.