PacSpace MCP
previewPacSpace MCP is not released. What an agent's harness uses today to record what the agent does, check a record, and share it.
Preview.
PacSpace MCP is not released. This page describes no interface and makes no promise about one: no tools, no transport, no date.
MCP is the Model Context Protocol. There is nothing named PacSpace MCP to build against today. An agent's actions are recorded today through the Records API, from the process that runs the agent, with the key kept out of the model's context.
What an agent's harness uses today
| Need | Use |
|---|---|
| Write an entry, read a history or a receipt, run the check | The Records API through the SDKs |
| Keep the key away from the model | Where the write goes |
| Learn when an entry committed or failed | Webhooks |
| Hand another party something they can check without you | Share a record |
| Lay out a run's record | Integration patterns |
| See it end to end | An agent in an evaluation |
Failure modes
- Building against a guess at an interface that is not released.
- Holding back a production agent for something with no date. The Records API records an agent's actions today.
- Putting the key in the model's context so the model can make the call itself. The write belongs in the harness.