Integrations
How the ATP MCP server relates to Sinera App and the Developer Portal, and what each side still has to build.
Not deployed
The ATP MCP server is designed to serve two applications: Sinera App and the Developer Portal (at atp.sinera.io), plus explicitly authorized external agent clients. Neither application can answer the server's backend calls yet. Both integrations are blocked until their owners build and approve the Application Adapter API.
How an app is selected
A client never picks its application. The operator maps each OAuth client id to sinera or dashboard in the server's client registry (ATP_MCP_CLIENTS), and the server uses that mapping to choose the backend and the gates. Credentials, Root associations, job ledgers and audit identities stay separate per application, even when both point at the same chain. See Authorization.
What works today
| Tool | Sinera App | Developer Portal |
|---|---|---|
atp_get_atom | Works (chain read, no backend) | Works |
| The other five tools | BLOCKED_INTEGRATION | BLOCKED_INTEGRATION |
With no backend configured, the blocked tools answer with zero outbound calls. The server never returns made-up application data.
Sinera App
Sinera App owns the commercial jobs and runs its own isolated signer. Its documented action routes are PAY (create and escrow an Atom) and ACCEPT (accept the original terms with a delegated session). The MCP server never calls the signer, never holds the signer's credential, and never sees a lease token. A model never receives one either.
To connect, Sinera needs a new, reviewed backend contract rather than a shortcut to the signer. The proposed binding is the adapter API. The Sinera side still has to provide:
| Item | Status |
|---|---|
| A service credential and a machine scope for ATP, issued per MCP deployment | Not present |
A mapping from the MCP token's { issuer, subject, clientId } to a Sinera account | Not present |
| The five adapter operations with their obligations | Not implemented |
Confirmation of how ledger states map to the job kind values | Open |
| Approval to start the existing job workflow from the new route without weakening the signer's own checks | Not given |
| Release evidence for the signer, kill switch and reconciliation | Not verified |
The proposed mapping from the application's ledger to the job kind is:
| Application ledger evidence | kind |
|---|---|
| Job claimed, no attempt yet | QUEUED |
| Job held, no open or confirmed attempt | HELD |
| Attempt recorded or submitted | SUBMITTED |
| Attempt ambiguous | RECONCILIATION_REQUIRED |
| Attempt failed but not yet shown to have no effect | RECONCILIATION_REQUIRED |
| Attempt confirmed, with a transaction hash | CONFIRMED |
| Attempt has no effect | NO_EFFECT |
| Job refused without any attempt | REJECTED |
When evidence conflicts, the order of precedence is RECONCILIATION_REQUIRED, CONFIRMED, SUBMITTED, NO_EFFECT, HELD, QUEUED. A failed attempt alone never proves that nothing happened.
For how Sinera App itself works, see the Developer quickstart and Delegation sessions.
Developer Portal
The Developer Portal at atp.sinera.io helps developers prepare ATP actions. It is blocked for a precise reason: there is no backend contract to bind to.
| Observation | Consequence |
|---|---|
| The Portal's server never signs or broadcasts. | There is no execution path for MCP to request. |
| Its API routes are same-origin and unauthenticated, and they prepare drafts. | They are not a service API. They have no service credential, caller identity or scopes. |
| It has no job ledger, signer or service API. | Nothing matches the adapter's attempt, execute or result operations. |
| It has no MCP reference. | There is no integration point on either side. |
Do not assume that a developer login is an ATP Root, that an API key is a Root authorization, or that the Portal can use another application's signer. Using the same chain does not mean sharing an order, account or agreement.
To integrate, the Portal owners would need to build an authenticated service API, an identity model, cryptographic Root wallet binding, a job and terms model with idempotent claims, an executor, and isolation tests. The adapter API is a proposal and is not a commitment from the Portal team.