Model Context Protocol

Kreato MCP API

Connect AI agents to Kreato — search creators, browse and access digital products, send donations, and manage memberships on-chain via the Model Context Protocol.

Base URLhttps://mcp.kreato.space
12 tools3 chainsv1.0.0
Claude integration

Using Kreato MCP with Claude

This section covers the Claude.ai connector flow — how tools map to natural language, how the 2-step payment flow works end-to-end, and how to embed the wallet-bridge packages into your own MCP-compatible app.

1 · Connect to Claude

Add Kreato as a custom MCP connector in Claude.ai. Once connected, Claude gains access to all 12 Kreato tools and can execute on-chain actions on your behalf.

Steps

  1. 1Open Claude.ai → Customize → Connectors
  2. 2Click Add custom connector
  3. 3https://mcp.kreato.space
  4. 4Connect your MetaMask or Phantom wallet

What you can say

ChainsEthereumEthereumBaseBaseSolanaSolanaETH · USDC · SOL
2 · How tools map to language

Each natural language prompt resolves to one or more MCP tools. Claude selects and chains them automatically — you never reference tool names directly.

Discovery
search_creators←"Find Web3 developers on Kreato"
get_creator←"Show me @alexbuilds full profile"
search_products←"Browse PDF tutorials under $20"
get_product←"What's the price of the EVM course?"
Payments
request_payment←"Buy the course for me with USDC"
buy_product←→ called after wallet approval
send_donation←"Tip @alexbuilds 5 USDC"
manage_membership←"Subscribe to the Pro tier"
Account
get_my_purchases←"Show my downloads"
get_analytics←"How much did I earn this month?"
get_pro_info←"What does Pro cost?"
upgrade_to_pro←"Upgrade me to Pro — monthly"
3 · The 2-step payment flow

AI agents can't sign wallet transactions directly. Kreato uses a bridge pattern: the agent creates a signed approval request, the user approves it in their browser wallet, and the agent registers the resulting transaction hash.

1
User prompt

"Buy the EVM Mastery course with USDC on Base"

2
request_payment

Agent calls the tool → bridge creates a signed approval request

tool
3
Wallet approval

User opens kreato.space/wallet/approve/[id] → signs in MetaMask or Phantom

4
buy_product

Bridge returns txHash → agent calls buy_product to register the purchase

tool
5
Download ready

Agent polls statusUrl until CONFIRMED, then returns the download link

⚠request_payment returns an approvalUrl — it does not trigger a wallet popup directly. The user must visit that URL in a browser tab to sign. Claude will surface the link automatically.
4 · Embedding the wallet bridge

Building your own MCP-compatible app on top of Kreato? The wallet-bridge packages handle the approval flow for you — drop them into any Next.js or React project.

Server-side@kreato-mcp/wallet-bridge
npm

Creates and stores signed payment requests. Exposes the approval URL back to the agent.

$npm install @kreato-mcp/wallet-bridge
Client-side@kreato-mcp/wallet-bridge-ui
npm

Drop-in React approval page. Reads the pending request, shows MetaMask / Phantom prompt, emits txHash on sign.

$npm install @kreato-mcp/wallet-bridge-ui
Full source, examples, and changeloggithub.com/kreatospace/mcp-wallet-bridge
API Reference

All endpoints are called by the MCP server on your behalf — you don't call these directly when using Claude. Use this reference when building your own integration or debugging tool behaviour.

🔒All endpoints require the x-mcp-secret header. Requests without a valid secret are rejected by mcpGuard.
⛓Donations, downloads, and memberships follow a 2-step flow: (1) create a PENDING transaction via the relevant endpoint, then (2) poll GET /api/transactions/status?txHash=... until status === "CONFIRMED".
Users
1 endpoint
Creators
2 endpoints
Products
2 endpoints
Downloads
1 endpoint
Donations
1 endpoint
Transactions
1 endpoint
Subscriptions
2 endpoints
Analytics
1 endpoint
Pro
2 endpoints

Parameter locations

querypathbody· * Required
Kreatokreato.spaceKreato MCP API · v1.0.0