Doc. TMF-006 · Rev 2026.08 Service Specification Classification: Open Sheet 6 of 6

Service Spec · Agent Tooling & MCP

Give agents safe hands on your systems of record

An agent that can only talk is a demo. An agent that can act on SAP, MAXIMO, or a historian is an operational system, and needs to be engineered like one.

Section 01 · Definition

The bottleneck is the tool layer, not the model

Teams reach for a better model when the real constraint is that their agent has no safe way to touch anything that matters. The work is in the layer beneath: typed tools with honest schemas, authorization that mirrors the permissions of the source system rather than a shared service account, rate limits, dry-run and approval on write paths, audit trails that satisfy a reviewer, and rollback for the moment an agent gets it wrong. Build that once, properly, and every agent you write afterwards inherits it.

Fig. 01 One governed tool layer, many agents.

The Equation

Typed tools
+
Authorization
+
Audit
=
Agents that can write

Section 02 · Benefits

What you get

Agents that act, not just answer

Read a historian, raise a work order, update a record: the difference between an assistant and a colleague.

Permissions that mirror the source

Every call carries the acting user's identity, so an agent can never see or change more than the person behind it could.

Every action accounted for

Who asked, what was called, with what arguments, and what changed: a trail a reviewer will accept.

Reversible by design

Dry-run, human approval on destructive paths, and rollback, because the interesting failures are the ones that wrote something.

Integrate once, reuse everywhere

MCP servers are not tied to one agent or vendor. The integration outlives whichever framework is fashionable.

Legacy systems included

SAP, MAXIMO, Kepware, OSI PI, and the in-house service nobody has touched in a decade.

Section 03 · Scope

Our comprehensive offering

Tool layer and MCP servers

  • MCP servers over your systems of record and data platform
  • Typed, documented tool schemas that models actually use correctly
  • Idempotency, retries, and timeouts around every side effect
  • Versioning, so a tool change never silently breaks an agent

Governance and safety

  • Authorization on the acting user's identity, not a shared account
  • Rate limits, quotas, and spend caps per agent and per tenant
  • Dry-run, human approval, and rollback on write paths
  • Sandboxed execution with egress control for agent-run code

Systems of record integration

  • ERP and asset management: SAP, MAXIMO and equivalents
  • Industrial historians and OT gateways, including Kepware and OSI PI
  • Ticketing, ITSM, and document repositories
  • Warehouses, lakehouses, and vector stores

Section 04 · Engagement Model

Two ways to fly

Build and Transfer

We build the capability and then hand it over to your team, documented and running.

Build and Operate

We build it and keep running it, on a fixed-price subscription.

Pricing

Scalable without sacrificing affordability

Tiered on the number of tools, connected systems, and environments under management, on the same fixed-price subscription model as our DevSecOps offering.

Fig. 02 Pricing tracks the estate under management.

Section 05 · Technology

The stack we reach for

Protocol & interfaces
MCPOpenAPIgRPCGraphQL
Identity & policy
OAuth 2.1OIDCOPAToken exchange
Execution & durability
TemporalKafkaPostgresRedis
Isolation & telemetry
gVisorFirecrackerOpenTelemetryAudit logging

Section 06 · Why Us

Why choose The Moonshot Factory

The hard part of this work is not the protocol, it is the systems underneath it. We have already integrated SAP for synchronised work orders and inventory, MAXIMO-enabled maintenance workflows, and Kepware and OSI PI connectors across a fleet of 1,500 sites. We have built the secure networking and confidential compute those integrations run over. We know where the sharp edges are because we have been cut by them.

Get Started Today →

Fig. 03 Same practices we preach, on every project we run.

Section 07 · Contact

Want to build a rocketship?

Contact Us →