Skip to main content
Glama
databutton

Databutton MCP Server

Official
by databutton
README.md
# Databutton MCP – build your own MCPs

We released a game changing way for anyone to build their own MCP servers in Databutton.
Learn more at https://www.databutton.com/mcp

# Databutton MCP Server

Databutton's (<https://www.databutton.com/>) AI agent builds and deploys frontends and backends in React and Python APIs/MCPs, for building beautiful business apps with unbounded complexity.

The agent has a planning mode for generating an initial plan for your app.

This MCP server is for doing doing initial app planning and creating a good starting point for an app.

## Installation

To use with Claude Desktop, add the server config:

On MacOS: `~/Library/Application Support/Claude/claude_desktop_config.json`
On Windows: `%APPDATA%/Claude/claude_desktop_config.json`

```json
{
  "mcpServers": {
    "databutton": {
      "command": "/path/to/databutton/build/index.js"
    }
  }
}
```

## Development

Install dependencies:

```bash
npm install
```

Build the server:

```bash
npm run build
```

For development with auto-rebuild:

```bash
npm run watch
```

### Debugging

Since MCP servers communicate over stdio, debugging can be challenging. We recommend using the [MCP Inspector](https://github.com/modelcontextprotocol/inspector), which is available as a package script:

```bash
npm run inspector
```

The Inspector will provide a URL to access debugging tools in your browser.

TDQS

C2.2/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The tool has a single, clear purpose that cannot be confused with any other tool in the set.

Naming Consistency5/5

Since there is only one tool, naming consistency is inherently perfect. The tool name 'submit_app_requirements' follows a clear verb_noun pattern, and there are no other tools to deviate from this pattern.

Tool Count2/5

A single tool is too few for a server named 'Databutton MCP Server', which suggests a broader scope for app development or management. One tool cannot cover the expected domain comprehensively, making it feel thin and under-scoped.

Completeness2/5

The tool set is severely incomplete for the implied domain of app development or requirements management. With only a submission tool, there are obvious gaps such as retrieving, updating, or deleting requirements, and no coverage of other app-related operations like deployment or testing.

Maintenance

ActivityInactive
ResponsivenessNo issues