MCP
The agent integrates
without a sales conversation.
An agent gets the same door as a person: capture, query, get_event, translate as typed MCP tools, JSON-RPC over POST /mcp, with the same key. One block in your client's configuration, and the door is in the toolchain.
{
"mcpServers": {
"epcis": {
"command": "npx",
"args": [
"epcis.dev",
"mcp"
]
}
}
}The tools.
readOnlyHint is set exactly where it is true, so a client can auto-approve the reads inside already-granted scope.
| tool | what it does | readOnlyHint | state |
|---|---|---|---|
| capture | POST an EPCIS document through the gateway laws: strip validate project-check stamp append | false | shipped |
| query | SimpleEventQuery over whatever was captured | true | shipped |
| get_event | one event, by its CBV §8.9 hash identity | true | shipped |
| translate | EPCIS 1.1 / 1.2 / 2.0 XML 2.0 JSON-LD, with a per-job fidelity report | true | shipped |
| resolve | identity resolution, via id.org.ai (Agent. Human. Thing.) | true | Coming soon |
| subscribe | push subscriptions | false | Coming soon |
Get a capture key.
Translate, validate and hash run here with no key. Capture, query and MCP open with a capture key.