FactVerse MCP Integration

FactVerse uses Model Context Protocol to connect AI agents with governed industrial tools, digital twin context, simulation services, operational data, and approved execution paths.

Integration model

An MCP-compatible client sends requests to a FactVerse MCP endpoint with an API key. FactVerse resolves the tenant and allowed scopes from the key, then exposes only the tools that the key is allowed to use.

AI client -> FactVerse MCP endpoint -> scoped tools -> FactVerse services

Authentication

Customer-facing MCP requests use an API key in the request header:

X-API-Key: your-api-key

The key identifies the tenant and the scopes assigned to that customer or integration. Clients should not send tenant identifiers in headers as a substitute for key-based authorization.

Example client configuration

{
  "mcpServers": {
    "factverse": {
      "url": "https://your-factverse-host/mcp/base/",
      "headers": {
        "X-API-Key": "your-api-key"
      }
    }
  }
}

Working with tools

Use the MCP client to list available tools at runtime. Tool availability can change as modules, customer scopes, and deployment configuration evolve.

The generated reference in this site describes the current source-derived tool catalog and should be treated as the public reference snapshot for this build.

Deprecated endpoints

The retired physical MCP endpoint is retained for migration awareness. New integrations should use the base platform and module-specific MCP endpoints described in the scope reference.