TokenOS dApp Builder
Idea to buildable dApp spec
Should I use this
Quality & Safety
Based on automated analysis of tool definitions and protocol compliance.
Context Cost
This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.
Install
One-Click Install
Add this to your `claude_desktop_config.json` file:
{
"mcpServers": {
"dapp-builder": {
"url": "https://tokenos.ai/api/mcp/apps/dapp-builder"
}
}
}Remote endpoints
https://tokenos.ai/api/mcp/apps/dapp-builderstreamable-httpWhat it can do
Tool inventory
Tools (3)
🟢plan_dapp(idea, name, chain, features, style)
Turn the user's app idea into a spec (features, pages, components, data model, Web3 integrations, stack, steps, credit estimate) with a pre-filled TokenOS IDE link. Only call with the user's own description — if the request is vague (e.g. “build an app”), ask the user what the app should do and for whom first; never invent an idea.
Input Schema
{
"type": "object",
"properties": {
"idea": {
"type": "string",
"description": "The user's own words: what the app should do and for whom (never invented by the assistant)"
},
"name": {
"type": "string"
},
"chain": {
"type": "string",
"enum": [
"solana",
"base",
"robinhood",
"ethereum",
"arbitrum"
]
},
"features": {
"type": "array",
"items": {
"type": "string"
}
},
"style": {
"type": "string",
"description": "Visual direction, e.g. dark neon, minimal light"
}
},
"required": [
"idea"
]
}🟢recommend_models(task)
Pick the best, balanced and cheapest frontier models from the live TokenOS roster for a build task, with price multipliers.
Input Schema
{
"type": "object",
"properties": {
"task": {
"type": "string"
}
}
}🟢tokenos_capabilities
Reference: supported chains, deployment targets, hosting, token launch, agents, payments and credits.
Input Schema
{
"type": "object",
"properties": {}
}Community
Evidence