Auto-syncing MCP server for the Spraay x402 Gateway. Auto-creates a wallet on first run — no env vars, just fund and go. Pay-per-call x402, USDC, no
Auto-syncing MCP server for the Spraay x402 Gateway. Auto-creates a wallet on first run — no env vars, just fund and go. Pay-per-call x402, USDC, no API keys. Exposed over MCP by the spraay mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.
Connect Claude, Cursor, or any MCP client to onchain payments, batch payouts, swaps, bridging, payroll, invoicing, escrow, oracle data, analytics, 200+ AI models, GPU/compute, research APIs, search/RAG, and more. Agents pay USDC per request via the x402 protocol — no API keys, no accounts.
Everything the assistant can do here goes through one of these:
Gateway — ** gateway.spraay.appManifest — ** gateway.spraay.app/.well-known/x402.jsonSmithery — ** smithery.ai/servers/Plagtech/Spraay-x402-mcpx402 — ** x402.orgArea — What it coversCompute — Text / image / video / TTS / STT / embeddings across Replicate, Chutes, OpenRouter; batch jobsBittensor — Decentralized inference, image gen, and embeddings via SN64 / SN19Payments — Batch payouts up to 200 recipients (Base, XRP Ledger, Stellar); estimatesPayroll — Stablecoin payroll runs across Base, Ethereum, SolanaAnalytics — Wallet profiles and decoded transaction historyResearch — 250M+ papers (OpenAlex), arXiv, Crossref, PubMed, PubChem, US Census, dictionaryCommunication — Email, SMS, XMTP messaging, webhooksBeing a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
You will need 2 environment variables: EVM_PRIVATE_KEY, SPRAAY_GATEWAY_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Plenty of team communication servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Spraay's toolset — Gateway, Manifest, Smithery and 11 more — is a fair guide to whether it matches your workflow. It is maintained by plagtech; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Gateway | ** [gateway.spraay.app](https://gateway.spraay.app) |
| Manifest | ** [gateway.spraay.app/.well-known/x402.json](https://gateway.spraay.app/.well-known/x402.json) |
| Smithery | ** [smithery.ai/servers/Plagtech/Spraay-x402-mcp](https://smithery.ai/servers/Plagtech/Spraay-x402-mcp) |
| x402 | ** [x402.org](https://x402.org) |
| Area | What it covers |
| Compute | Text / image / video / TTS / STT / embeddings across Replicate, Chutes, OpenRouter; batch jobs |
| Bittensor | Decentralized inference, image gen, and embeddings via SN64 / SN19 |
| Payments | Batch payouts up to 200 recipients (Base, XRP Ledger, Stellar); estimates |
| Payroll | Stablecoin payroll runs across Base, Ethereum, Solana |
| Analytics | Wallet profiles and decoded transaction history |
| Research | 250M+ papers (OpenAlex), arXiv, Crossref, PubMed, PubChem, US Census, dictionary |
| Communication | Email, SMS, XMTP messaging, webhooks |
| Infrastructure | Multi-chain RPC, IPFS/Arweave storage, cron scheduling, structured logs |
| Variable | Required |
{
"mcpServers": {
"spraay-x402": {
"command": "npx",
"args": ["-y", "spraay-x402-mcp"],
"env": {
"EVM_PRIVATE_KEY": "your-value",
"SPRAAY_GATEWAY_URL": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| EVM_PRIVATE_KEY | Credential the server authenticates with. | Yes |
| SPRAAY_GATEWAY_URL | Endpoint or connection string the server talks to. | Yes |
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Inbox intelligence — search, read, draft and send Gmail through your assistant with OAuth auto-setup.
Read and write Jira, Confluence, Bitbucket, JSM and Compass from your AI client — with your own permissions.
Read and send Telegram messages through your assistant — chats, channels and history via the client API.
Enables Discord bot integration with Model Context Protocol (MCP) compatible applications like Claude Desktop.
Exposes REST APIs defined by OpenAPI specifications as Model Context Protocol (MCP) tools, facilitating seamless integration into MCP-based workflows.