SAI MCP Server in WebAssembly Go

Created By
example42a year ago
Sai Mcp Server
Overview

what is SAI MCP?

SAI MCP is a Management Control Protocol server implemented in WebAssembly Go, designed to execute the 'sai' command and manage its output and exit codes.

how to use SAI MCP?

To use SAI MCP, integrate the WebAssembly module into your JavaScript environment and call the executeSai function with the desired command arguments.

key features of SAI MCP?

  • Executes the 'sai' command with specified arguments
  • Captures and returns stdout, stderr, and exit codes
  • Supports output parsing in JSON, YAML, and plain text formats
  • Provides structured results for easy integration

use cases of SAI MCP?

  1. Automating command line tasks in web applications
  2. Integrating command line tools with JavaScript frameworks
  3. Capturing and processing command outputs for further analysis

FAQ from SAI MCP?

  • What is the output format supported by SAI MCP?

SAI MCP supports JSON, YAML, and plain text output formats.

  • How do I build the WebAssembly module?

Use the command GOOS=js GOARCH=wasm go build -o sai_mcp.wasm ./cmd/main to build the module.

  • Can I run tests for SAI MCP?

Yes! You can run tests using the command go test ./cmd/main -v in a native Go environment.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
example42
Star
0
Language
Go
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago