Integration

Spydra Asset Tokenization integration

Spydra is a blockchain platform (Hyperledger Fabric networks) whose Asset Tokenization app records business assets on a ledger. Create, upsert, update and delete assets of the asset types configured in the app, read one asset, page all assets, read an asset's full change history and asset statistics, replace asset owners, run ownership-transfer requests (request, approve, reject, list) and generic approval workflows (create, accept, reject, cancel, queues, history), and check the receipt of an asynchronous transaction. Not exposed: the app's status check, and the token routes the same app documents (fungible and non-fungible tokens with mint, burn, accounts and transactions, ERC1155 and fractionalisation vaults). GraphQL queries, custom chaincode apps and the public-chain Token Store are separate Spydra APIs. Authentication is a network API key sent in the X-API-KEY header, plus the organization's membership id and the app id that make up the app's base URL.

Connect Spydra Asset Tokenization How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Spydra Asset Tokenization.Built from the 26 Spydra Asset Tokenization tools below, on the connection you add once.

What you can do with Spydra Asset Tokenization

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Asset, 5 operations

create_assetsCreate assetsPOSTRecords one or more new assets of an asset type on the ledger; data is a list of asset objects keyed by the type's fields. A duplicate id fails (409). Waits for the ledger commit unless async=true.
delete_assetsDelete assetsDELETEDeletes one or more assets of an asset type from the ledger state (the change history stays readable with get_asset_history). Waits for the commit unless async=true.
get_assetGet assetGETReturns one asset of an asset type by its id (the app's primary key value): its data, owners and creation and update entities. depth resolves referenced assets.
update_assetsUpdate assetsPATCHUpdates one or more existing assets of an asset type on the ledger; each object in data carries the asset id. Waits for the ledger commit unless async=true, which returns a receiptId.
upsert_assetsUpsert assetsPUTCreates one or more assets of an asset type, or updates those whose id already exists on the ledger. Waits for the ledger commit unless async=true, which returns a receiptId.

Approval, 3 operations

create_approval_requestsCreate approval requestsPOSTCreates one or more approval requests of an approval type you name (for example a loan approval), sent to the given approvers with optional data and timeout. Waits for the commit unless async=true.
get_approval_requestGet approval requestGETReturns one approval request by id and approval type: approvers with their status, approvals required, timeout, overall status and data.
list_ownership_transfer_approval_queueList ownership transfer approval queueGETLists the ownership transfer requests waiting for your approval (or the actAs entity's); only pending ones unless onlyPending=false. Pass the bookmark for more.

History, 3 operations

get_approval_request_historyGet approval request historyGETReturns the recorded changes of one approval request on the ledger, each with its transaction id, time, approvers and status.
get_asset_historyGet asset historyGETReturns an asset with every recorded change on the ledger (CREATED, UPDATED, DELETED), each with its transaction id, time, data and owners.
get_ownership_transfer_request_historyGet ownership transfer request historyGETReturns the recorded changes of one ownership transfer request on the ledger, each with its transaction id, time, approvers and status.

My, 2 operations

list_my_approval_requestsList my approval requestsGETLists the approval requests of an approval type submitted by you (or the actAs entity) with their status, 25 per page by default; pass the bookmark for more.
list_my_ownership_transfer_requestsList my ownership transfer requestsGETLists the ownership transfer requests submitted by you (or the actAs entity) with their status, 25 per page by default; pass the bookmark for more.

Reject, 2 operations

reject_approval_requestsReject approval requestsPOSTRejects one or more approval requests of an approval type addressed to you (or the actAs entity), each with an optional comment. Waits for the commit unless async=true.
reject_ownership_transfersReject ownership transfersPOSTRejects one or more pending ownership transfer requests addressed to you (or the actAs entity). Waits for the commit unless async=true.

Request, 2 operations

create_ownership_transfer_requestsCreate ownership transfer requestsPOSTAsks the given approvers to approve transferring one or more assets to you (or to the actAs entity). Ownership changes only after the required approvals.
get_ownership_transfer_requestGet ownership transfer requestGETReturns one ownership transfer request by id: approvers with their status, number of approvals required, overall status (PENDING, APPROVED, REJECTED, CANCELLED) and data.

Accept, 1 operation

accept_approval_requestsAccept approval requestsPOSTApproves one or more approval requests of an approval type addressed to you (or the actAs entity), each with an optional comment. Waits for the commit unless async=true.

All, 1 operation

list_assetsList assetsGETLists the assets of one asset type on the ledger, 25 per page by default. Pass the returned bookmark to read the next page.

Approve, 1 operation

approve_ownership_transfersApprove ownership transfersPOSTApproves one or more pending ownership transfer requests addressed to you (or the actAs entity); once enough approvers agree the asset owners change. Waits for the commit unless async=true.

By asset, 1 operation

list_asset_ownership_transfer_requestsList asset ownership transfer requestsGETLists the ownership transfer requests of one asset (by asset id); only pending ones unless onlyPending=false. Pass the bookmark for more.

Cancel, 1 operation

cancel_approval_requestsCancel approval requestsPOSTCancels one or more approval requests of an approval type that you (or the actAs entity) submitted, each with an optional comment. Waits for the commit unless async=true.

Owner, 1 operation

replace_asset_ownersReplace asset ownersPATCHReplaces the owners of one or more assets with the owner lists given (organization membership ids, optionally a user or sub-entity). Waits for the commit unless async=true.

Queue, 1 operation

list_approval_queueList approval queueGETLists the approval requests of an approval type waiting for your approval (or the actAs entity's); only pending ones unless onlyPending=false. Pass the bookmark for more.

Receipt, 1 operation

get_transaction_receiptGet transaction receiptGETReturns the status of a transaction submitted earlier (by any write tool) from its receiptId, with the ledger transactionId once committed.

Stats, 1 operation

get_asset_statsGet asset statsGETReturns asset usage statistics for the app: the total number of assets on the ledger and the count per asset type.

Use Spydra Asset Tokenization from Claude Code, Cursor or Codex

Connect Spydra Asset Tokenization in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Spydra Asset Tokenization operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Spydra Asset Tokenization

Create your workspace
Sign up free. Nothing to install.
Connect Spydra Asset Tokenization once
Add your Spydra Asset Tokenization connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.