Labsco
MCP SERVER

Cyberlink MCP Server

by dasein108

Create and query cyberlinks — typed relationships between things — on a CW-Social contract from the conversation.

Wallets, Signing & Transaction Execution
Summary
Writes go on chain, so the mnemonic in your config is the boundary.

Reads are plain queries, but creates, updates and send_tokens are signed transactions with real cost, which is why the transaction-status tools exist alongside them. Leaving WALLET_MNEMONIC out gives you a read-and-compose setup with no signing key present.

What it is

A server for the CW-Social smart contract on Cosmos chains. It creates, updates, deletes and queries cyberlinks, tracks the resulting transactions, and can attach semantic embeddings to entries.

What you get
  • create_cyberlink, create_cyberlink2 (node plus link in one call), create_named_cyberlink and create_cyberlinks for batches
  • update_cyberlink and delete_cyberlink by global ID
  • update_with_embedding — attach a semantic embedding to an entry
  • query_by_gid, query_by_fid, query_by_gids, query_cyberlinks and query_named_cyberlinks with pagination
  • query_cyberlinks_by_type, _by_from, _by_to and _by_owner_and_type for filtered reads
  • query_cyberlinks_by_owner_time and _by_owner_time_any for ISO 8601 time ranges in UTC
  • query_transaction and get_tx_status for transaction state, query_wallet_balance and send_tokens for the wallet
  • query_last_id, query_config, query_debug_state and get_graph_stats for contract and graph state
Requirements

Node.js 16 or higher, a reachable Cosmos node and a deployed contract: NODE_URL and CONTRACT_ADDRESS are required. WALLET_MNEMONIC is optional — without it transactions go unsigned. DENOM defaults to stake, and BENCH32_PREFIX is optional.

Setup effort

Build from source — clone the repository and build it, then point your client at the binary