eSpace Facilities FAQs

Question 1

Why is a personal eSpace API key required for each user?

Accepted Answer

Each user needs their own eSpace API key to ensure strict audit attribution and accountability. Your key acts as your identity, logging all actions performed via Claude Code directly under your personal eSpace profile.

Question 2

How does eSpace Facilities ensure data safety for write operations?

Accepted Answer

All write operations (create, update, delete) in eSpace Facilities require explicit user confirmation within Claude Code before execution. This mandatory step prevents unauthorized changes to critical facilities data.

Question 3

Is eSpace Facilities an open-source project?

Accepted Answer

No, eSpace Facilities is privately licensed. While it's publicly available for authorized staff to clone and use, the code itself is not open-source, and no license is granted for copying, modification, or redistribution.

Question 4

What eSpace features can I manage using Claude Code?

Accepted Answer

You can manage an extensive range of eSpace functions, including creating/updating work orders, listing events, scheduling maintenance, managing equipment, and accessing organizational/ministry data, all through Claude Code conversations.

Question 5

What is eSpace Facilities?

Accepted Answer

eSpace Facilities is an MCP server that integrates the eSpace facilities management API with Claude Code, enabling AI-driven access and control over work orders, events, maintenance, and equipment.

eSpace Facilities

eSpace Facilities

Key Features

Use Cases

Key Features

Use Cases