relai-mcp-server
Enables on-chain agent identity via SATI on Solana, including registration of a SATI identity NFT and submission of positive feedback after paid API calls.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@relai-mcp-serverRequest authorization to use the premium translation API"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
relai-mcp-server
MCP (Model Context Protocol) server for RelAI. Lets any MCP-compatible AI agent authorize itself with RelAI and call paid x402 APIs autonomously.
Tools
Tool | Description |
| Request a one-time consent link from RelAI to send to the user |
| Check if the user approved — returns the service key |
| Call any paid API through the RelAI Metered proxy |
| Check the remaining USDC balance in the user's wallet |
Related MCP server: x402-gateway-mcp
Setup
npm install
npm run buildUsage with Claude Desktop
Add to your claude_desktop_config.json:
{
"mcpServers": {
"relai": {
"command": "node",
"args": ["/path/to/relai-mcp-server/dist/index.js"],
"env": {
"RELAI_API_BASE": "https://api.relai.fi"
}
}
}
}Usage with any MCP client
RELAI_API_BASE=https://api.relai.fi node dist/index.jsAuthorization Flow
Agent calls
request_authorization→ gets a linkAgent shows the link to the user
User opens the link and clicks Allow on relai.fi
Agent calls
poll_authorization→ getsserviceKey+agentIdAgent calls
call_apifor any paid API — payments are automatic
Environment Variables
Variable | Default | Description |
|
| RelAI API base URL |
| (optional) | Solana keypair (base58 or JSON byte array) — enables SATI on-chain agent identity |
SATI Integration (optional)
If SATI_PAYER_KEYPAIR is set, the server automatically:
Registers a SATI identity NFT on Solana when the user approves authorization — giving the agent a verifiable on-chain identity with
x402Support: trueSubmits positive feedback on-chain after every successful paid API call — building the agent's reputation over time
If SATI_PAYER_KEYPAIR is not set, SATI is silently disabled and everything works normally.
{
"mcpServers": {
"relai": {
"command": "node",
"args": ["/path/to/relai-mcp-server/dist/index.js"],
"env": {
"RELAI_API_BASE": "https://api.relai.fi",
"SATI_PAYER_KEYPAIR": "<your-solana-wallet-base58>"
}
}
}
}This server cannot be deployed
Maintenance
Related MCP Connectors
Give AI agents identity, permissions, and reusable proof through one MCP.
Paid MCP tools behind one endpoint. Agents pay per call in USDC on Base via x402.
Agent x402 Paywall MCP — Coinbase HTTP 402 protocol + on-chain settlement. Agents pay per-call
Pay-per-action access to APIs and MCP tools over Lightning L402 and Base USDC x402.
Related MCP Servers
- AlicenseAqualityBmaintenanceL402 + x402 client MCP. AI agents discover, pay for, and consume any payment-gated API autonomously. Supports Lightning (NWC), Cashu ecash, stablecoins, and human-in-the-loop payments.1162 npmMIT
- AlicenseAqualityFmaintenanceEnables MCP clients to access all endpoints of an x402 gateway by paying real-time microtransactions (USDC on Base) per API call, with automatic tool discovery and spend guardrails.23214 npmMIT

@hpp-io/x402-mcp-bridgeofficial
AlicenseNot gradedqualityBmaintenanceEnables AI agents to autonomously pay for and discover services using HPP USDC.e over the x402 protocol, without API keys or manual signing.88 npmApache 2.0- AlicenseNot gradedqualityFmaintenanceMCP server for the x402 protocol that lets AI agents discover and call payment-gated HTTP APIs automatically.82 npmApache 2.0