Databutton MCP – build your own MCPs

Created By
databuttona year ago
Databutton MCP Server
Overview

what is Databutton MCP Server?

Databutton MCP Server is an AI agent that builds and deploys frontends and backends in React and Python APIs/MCPs, designed for creating complex business applications.

how to use Databutton MCP Server?

To use the Databutton MCP Server, you can install it via Smithery or manually configure it for Claude Desktop. For installation via Smithery, run the command: npx -y @smithery/cli install @databutton/databutton-mcp --client claude. For manual installation, add the server configuration to the appropriate config file based on your operating system.

key features of Databutton MCP Server?

  • AI-driven app planning and deployment
  • Supports building both frontends and backends
  • Integration with React and Python APIs
  • Initial planning mode for app generation

use cases of Databutton MCP Server?

  1. Rapid development of business applications with complex requirements.
  2. Streamlining the app planning process for developers.
  3. Facilitating the deployment of scalable web applications.

FAQ from Databutton MCP Server?

  • What programming languages does Databutton MCP Server support?

It supports React for frontends and Python for backends.

  • Is there a way to debug the server?

Yes, you can use the MCP Inspector for debugging, which provides a URL to access debugging tools in your browser.

  • How can I install Databutton MCP Server?

You can install it automatically via Smithery or manually by configuring the server settings in your Claude Desktop.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
databutton
Star
12
Language
TypeScript
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago