The rise of AI has seen a rapid growth in automation, as “agents” take over more and more mundane tasks. Despite this surge in automation, one constant has remained: Making payments is a chore.
Let’s say you owe a friend for lunch. Paying them back means opening an app, copying their address, checking the details twice and hoping you got it right. With crypto payments, you have the added complexity of keys and networks and other headaches. With Sliyd MCP connected, you tell your assistant “send Bob 5 USDC”, check the transfer it prepares and confirm it. You never leave the window you were working in. What’s better is that with Sliyd it doesn’t matter if Bob doesn’t even have an existing wallet, the Sliyd MCP can create a URL-based wallet for Bob and give him one-click access to his pizza money.
The bigger shift is what your agent can do with a wallet behind it. Mid-task, it can pay for what it needs: a paywalled API or a dataset that charges per call over x402. You set the caps in advance and it comes back with the result instead of the sign-up page.
Sliyd MCP is the connector that does both: a Model Context Protocol server that plugs a Sliyd wallet into any MCP-compatible LLM client. It is available now. Setup is one line in a config file, with no account to create and no subscription to add.
One connector, a full wallet toolkit
Sliyd MCP exposes your wallet to your LLM as a set of purpose-built tools:
- Natural language transfers. Send native ETH or any registered ERC-20 on Base with a plain English request. Your agent prepares the transaction and you approve it.
- x402 payments. Your agent can browse a registry of x402-enabled APIs, then pay for and fetch a resource the moment it hits a paywall, within limits you set.
- Contacts and a token registry. Save wallets, contacts and custom tokens by name once, then reference them in every conversation that follows.
- Live balances and prices. Ask for either and get an answer straight from the chain.
- Vault gating. Route larger payments through a vault that holds them for a human signature.
- Room to extend. Pair Sliyd MCP with other tools in your agent to schedule recurring transfers or chain payments into longer workflows.
We’ve shipped this as an MCP server rather than a chat feature in our own app, because the assistant you use is the one you already have. The Model Context Protocol is an open standard for handing tools to an agent, so Sliyd MCP works in any client that speaks it, with no bespoke integration on either side.
Things to try in your first hour
While there are countless ways you can use Sliyd’s MCP support in your agent here are some things to try:
- Pay people by name. Save Bob’s wallet once and “send Bob 5 USDC” works in every conversation after that. The transfer waits for your approval.
- Send your agent through paywalls. Ask for research and let it pay for the sources it finds over x402, inside your caps. You get the answer, not the checkout.
- Check the numbers as you go. Ask for balances and token prices without switching apps, in the middle of whatever you were doing.
- Register the tokens you hold. Add any ERC-20 on Base by name once and use it by name from then on, in transfers, balances and price checks.
- Keep payouts behind sign-off. Route contractor payments through the vault: your agent drafts them in chat and a person signs them.
A transfer, step by step
Say “send Bob 5 USDC”. Your agent looks Bob up in your contact registry, checks your balance and builds the transaction. Then it stops. The transfer sits in front of you with the recipient, the amount and the token spelled out, and nothing touches the chain until you confirm it. If Bob doesn’t have a wallet, the agent can create a Sliyd URL wallet which can then, depending on your agent set-up, be automatically emailed, DM’d or even (shudder the thought) manually sent to Bob.
The split is deliberate. Your agent does the reading and the preparing; you do the authorising.
Agents that pay their own way
x402 is an open payment standard built on the HTTP 402 “Payment Required” status code. A server quotes a price in response to a request, the agent pays in stablecoins and retries, and the server returns the resource. The whole cycle takes seconds and needs no login. We covered the standard, and why it fits agents, in our agentic payments explainer.
Sliyd MCP gives your agent the paying half. Point it at a registry of x402-enabled services and it can discover a paid API mid-task, settle the fee and use the result. You cap what it can spend before it starts, and research that hits a paywall no longer ends with you filling in a card form.
The security model
A Sliyd wallet lives at a URL: hold the link, control the funds. Sliyd MCP works with that grain. You connect a wallet you already hold, or your agent creates a fresh one, and the server acts through that wallet’s URL. A wallet your agent creates is a wallet your agent can see, so the design does not pretend the model is blind. It puts the controls where the money moves.
Transfers to people wait for your confirmation before anything touches the chain. x402 payments run inside caps you set in advance. Anything larger belongs in the vault, a separate address where transactions queue until a human signs them. The practical rule: fund the connected wallet like spending money and keep the rest vaulted.
If you want the whole loop on your own hardware, Sliyd MCP runs over local stdio and pairs well with locally hosted models.
Getting started
Sliyd MCP works with any MCP client that supports locally hosted, stdio-based servers. Add this to your mcp.json:
{
"mcpServers": {
"sliyd-mcp": {
"command": "npx",
"args": [
"-y",
"https://sliyd.com/mcp/latest"
]
}
}
}
Restart your client, then connect a wallet you already hold or have your agent create a new one. Your first transfer is a sentence away. Full documentation: [PLACEHOLDER: docs URL].
Agents are beginning to spend real money on real services. We think you should stay in charge of the money while your agent does the legwork. Sliyd MCP is built on that split: you set the limits and sign what matters; your agent handles the rest. Try it and tell us what breaks: [PLACEHOLDER: feedback channel or GitHub link].
About Sliyd Sliyd is PayFi infrastructure for agentic commerce, built on Base. Brands use Sliyd to distribute digital rewards through claim links that create a wallet in one click. Sliyd is a Memetiq Labs product.
FAQ
What is Sliyd MCP?
A Model Context Protocol server that connects a Sliyd wallet to any MCP-compatible LLM client. It gives the model a set of wallet tools: transfers, balances, prices, contacts, x402 payments and vault approvals. Every transfer waits for the owner’s confirmation.
Can the model see my wallet?
Treat it as if it can. A Sliyd wallet is controlled by its URL, and a wallet your agent creates is one it knows. Fund the connected wallet like spending money and keep larger sums in the vault, where a human signs every transaction. Transfers to people wait for your confirmation either way.
Which clients does Sliyd MCP work with?
Any MCP-compatible client that supports locally hosted, stdio-based servers. Add it to the client’s MCP configuration with the npx one-liner and the wallet tools appear in the conversation. There is no account and no subscription.
What is x402 and how does Sliyd MCP use it?
x402 is an open payment standard built on the HTTP 402 status code: a server quotes a price, the client pays in stablecoins and retries, and the server returns the resource. Sliyd MCP lets your agent make these payments from your wallet, within limits you set in advance.





