Overview
The Brickken MCP server exposes the Brickken Dapp API and Agentic API as tools for MCP-compatible AI agents.
MCP Open the official Brickken MCP page.
Health check Check hosted server availability.
Connect
Use the hosted endpoint in Claude Code, Codex, or any MCP-compatible client:
{
"mcpServers" : {
"brickken" : {
"url" : "https://mcp.brickken.com/"
}
}
}
Session Configuration
Every MCP session is isolated. Configure credentials at runtime with the configure tool, then use get_config to verify the active environment without exposing secrets.
API-key mode
Use this mode for the Dapp API .
{
"env" : "production" ,
"apiKey" : "YOUR_BRICKKEN_API_KEY"
}
x402 private-key mode
Use this mode for the Agentic API . The private key is used by the MCP server session for local transaction signing and x402 payment signing.
{
"env" : "production" ,
"privateKey" : "0xYOUR_PRIVATE_KEY" ,
"apiKey" : ""
}
For sandbox:
{
"env" : "sandbox" ,
"privateKey" : "0xYOUR_PRIVATE_KEY" ,
"apiKey" : ""
}
Only configure a private key in MCP clients and environments you trust. get_config returns booleans such as hasApiKey and hasPrivateKey, never the secret values.
Tool Purpose configureSet env, baseUrl, apiKey, or privateKey for the current session. get_configInspect env, baseUrl, hasApiKey, and hasPrivateKey.
Tool Purpose prepare_transactionsPrepare unsigned transactions for a backend method. send_transactionsSubmit signed transactions to Brickken. get_transaction_statusPoll a transaction hash.
These tools map to API-key authenticated dapp flows. If a private key is configured, write tools can prepare, sign, and send automatically; otherwise they return prepared transactions for external signing.
Area Tools Tokenization create_tokenizationSTOs create_sto, invest_in_sto, claim_sto, close_stoSecurity-token operations mint_tokens, whitelist_investor, burn_tokens, transfer_tokens, approve_tokens, distribute_dividendReads get_network_info, get_token_info, get_tokenizer_info, get_stos, get_sto_by_id, get_investments_by_sto_id, get_investor_info, get_allowance, get_whitelist_status, get_balance_whitelist, get_sto_balance, get_dividend_info
These tools map to ERC-8004 and agent-token methods. When the session has a private key and no API key, agentic calls are paid through x402.
Area Tools Agent identity agent_register, agent_set_uri, agent_set_metadata, agent_set_walletReputation agent_give_feedback, agent_revoke_feedback, agent_append_feedback_responseAgent-owned tokens agent_create_token, agent_mint_token, agent_burn_token, agent_transfer_token, agent_transfer_from_token, agent_approve_token
Example
Configure x402 mode, then register an agent:
{
"env" : "sandbox" ,
"privateKey" : "0xYOUR_PRIVATE_KEY" ,
"apiKey" : ""
}
{
"chainId" : "11155111" ,
"signerAddress" : "0xYourWallet" ,
"name" : "Research Agent" ,
"description" : "On-chain AI research agent" ,
"image" : "https://example.com/agent.png" ,
"serviceName" : "A2A" ,
"serviceEndpoint" : "https://agent.example/.well-known/agent-card.json" ,
"aiModelProvider" : "OpenAI" ,
"aiModelName" : "Research Model" ,
"x402Support" : true ,
"active" : true
}
The agent_register result includes prepared transaction data and, when auto-executed, the send result. Save prepared.info.agentUuid for later agent updates.