create_cyberlinkLABSCO 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 — git clone https://github.com/dasein108/mcp-cw-graph.git
USE CASES
01
Recording a relationship between two things on chain
Create the cyberlink with its type, source and target — or create the node and the link in a single call.
02
Pulling everything of one kind, or one owner
Filter by type, by source, by target, or by owner and type, with a cursor and page size.
03
Confirming a write actually landed
Take the transaction hash from the create and poll its status until it settles.
04
Finding entries by meaning rather than by field
Attach an embedding to entries, then use the cosine similarity that gives you for semantic matching.
26 tools
Listed in project docs. Your client may show a different list.
create_cyberlink2create_named_cyberlinkcreate_cyberlinksupdate_cyberlinkdelete_cyberlinkupdate_with_embeddingquery_by_gidquery_by_fidquery_cyberlinksquery_named_cyberlinksquery_by_gidsquery_cyberlinks_by_typequery_cyberlinks_by_fromquery_cyberlinks_by_toquery_cyberlinks_by_owner_and_typequery_cyberlinks_by_owner_timequery_cyberlinks_by_owner_time_anyquery_last_idquery_configquery_debug_stateget_graph_statsquery_transactionget_tx_statusquery_wallet_balancesend_tokensBEFORE YOU INSTALL
What to know first
Tools you get
26 tools named in the project's documentation.
Requires
- Node.js 16 or higher
- A reachable Cosmos node and a deployed CW-Social contract (NODE_URL and CONTRACT_ADDRESS)
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
You clone and build this one yourself.
Server setup
TERMINAL
git clone https://github.com/dasein108/mcp-cw-graph.git
cd mcp-cw-graph
npm install
npm run buildMCP Clients
Cursor
CURSOR · JSON
{
"mcpServers": {
"cw-graph": {
"command": "node",
"args": [
"<YOUR_PATH_TO_PROJECT>/dist/index.js"
],
"env": {
"NODE_URL": "http://localhost:26657",
"WALLET_MNEMONIC": "<YOUR_WALLET_MNEMONIC>",
"CONTRACT_ADDRESS": "<YOUR_CONTRACT_ADDRESS>",
"DENOM": "stake",
"BENCH32_PREFIX": "cyber"
}
}
}
}<YOUR_PATH_TO_PROJECT> is the full path of your mcp-cw-graph clone. dist/index.js is created by npm run build.
