Skip to main content
Glama
Goose App Maker MCP

Goose App Maker MCP

by michaelneale

Goose App Maker

This MCP (Model Context Protocol) sever allows users to create, manage, and serve web applications through Goose, that make use of Goose for api calls, data access, and more.

Install

click here to install in goose πŸͺΏ πŸͺΏπŸͺΏπŸͺΏπŸͺΏπŸͺΏπŸͺΏπŸͺΏπŸͺΏπŸͺΏ

Features

  • Create new web applications from basic instructions

  • Store apps in ~/.config/goose/app-maker-apps directory (each app in its own subdirectory)

  • Serve web applications locally on demand

  • Open web applications in the default browser (and chromeless if possible)

  • Lists all available web applications

  • make apps that can themselves use goose as a generic backend

Related MCP server: mcp-toolkit

Examples

Load data via goose (re-using its extensions)

Screenshot 2025-04-28 at 7 38 24β€―pm

Screenshot 2025-04-28 at 7 38 53β€―pm

goose keeps track of your apps:

Make apps on demand

Show rich tabular or list data as well

Usage from source

eg in goose:

# Run directly from source
uv --directory $PWD run python main.py

IMPORTANT: this MCP is required to be run in the goose desktop app at the moment (as it accesses goose-server/goosed)

Building and publishing

Optional: Build in a clean environment using uv

uv venv .venv
source .venv/bin/activate
uv pip install build
python -m build

Publishing

  1. Update version in pyproject.toml:

[project]
version = "x.y.z"  # Update this
  1. Build the package:

# Clean previous builds
rm -rf dist/*
python -m build
  1. Publish to PyPI:

# Install twine if needed
uv pip install twine

# Upload to PyPI
python -m twine upload dist/*

How it works

This MCP serves up apps, but also allows them to talk to goose via goosed and their own session:

Overview

The system implements a non-blocking, asynchronous request-response pattern that allows web applications to send requests to Goose and receive responses without blocking the main thread. This is achieved through a combination of:

  1. A blocking endpoint on the server side

  2. Asynchronous JavaScript on the client side

  3. A response storage mechanism with thread synchronization

Web App Structure

Web apps are made (or downloaded) on request, based on resources/templates. Each web app is stored in its own directory under ~/.config/goose/app-maker-apps with the following structure:

app-name/
β”œβ”€β”€ goose-app-manifest.json     # App metadata
β”œβ”€β”€ index.html        # Main HTML file
β”œβ”€β”€ style.css         # CSS styles
β”œβ”€β”€ script.js         # JavaScript code
└── goose_api.js      # allows the apps to access goose(d) for deeper backend functionality
└── ...               # Other app files

The goose-app-manifest.json file contains metadata about the app, including:

  • name: Display name of the app

  • type: Type of app (e.g., "static", "react", etc.)

  • description: Brief description of the app

  • created: Timestamp when the app was created

  • files: List of files in the app

1. Client-Side Request Flow

When a client wants to get a response from Goose:

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”     β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”     β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”     β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ User    │────▢│ gooseRequestX() │────▢│ Goose API     │────▢│ waitForResp- β”‚
β”‚ Request β”‚     β”‚ (text/list/     β”‚     β”‚ (/reply)      β”‚     β”‚ onse endpoint β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜     β”‚  table)         β”‚     β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜     β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
                β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜                                   β”‚
                         β–²                                            β”‚
                         β”‚                                            β”‚
                         β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
                                          Response
  1. The user initiates a request (e.g., clicking "Get List Response")

  2. The client calls one of the request functions (gooseRequestText, gooseRequestList, or gooseRequestTable)

  3. The function generates a unique responseId and sends a request to Goose with instructions to call app_response with this ID

  4. The function then calls waitForResponse(responseId) which polls the /wait_for_response/{responseId} endpoint

  5. This endpoint blocks until the response is available or a timeout occurs

  6. When the response is available, it's returned to the client and displayed

2. Server-Side Processing

On the server side:

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”     β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”     β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ HTTP Server │────▢│ app_response│────▢│ response_locksβ”‚
β”‚ (blocking   β”‚     β”‚ (stores     β”‚     β”‚ (notifies     β”‚
β”‚  endpoint)  │◀────│  response)  │◀────│  waiters)     β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜     β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜     β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
  1. The /wait_for_response/{responseId} endpoint uses condition variables to block until a response is available

  2. When Goose processes the request, it calls the app_response function with the response data and the responseId

  3. The app_response function stores the response in the app_responses dictionary and notifies any waiting threads using the condition variable

  4. The blocked HTTP request is then unblocked and returns the response to the client

3. Thread Synchronization

The system uses Python's threading.Condition for thread synchronization:

  1. When a client requests a response that isn't available yet, a condition variable is created for that responseId

  2. The HTTP handler thread waits on this condition with a timeout (30 seconds)

  3. When the response becomes available, the condition is notified

  4. If the timeout expires before the response is available, an error is returned

Key Components

Client-Side Functions

  • gooseRequestText(query): Requests a text response

  • gooseRequestList(query): Requests a list response

  • gooseRequestTable(query, columns): Requests a table response with specified columns

  • waitForResponse(responseId): Waits for a response with the given ID

Server-Side Functions

  • app_response(response_id, string_data, list_data, table_data): Stores a response and notifies waiters

  • HTTP handler with /wait_for_response/{responseId} endpoint: Blocks until response is available

Available Tools

9 tools
app_createB
Create a new web application directory and copy starter files.
The starter files are for you to replace with actual content, you don't have to use them as is.
the goose_api.js file is a utility you will want to keep in case you need to do api calls as part of your app via goose.

Args:
    app_name: Name of the application (will be used as directory name)
    description: Brief description of the application (default: "")

Returns:
    A dictionary containing the result of the operation

After this, consider how you want to change the app to meet the functionality, look at the examples in resources dir if you like.
Or, you can replace the content with existing html/css/js files you have (just make sure to leave the goose_api.js file in the app dir)

Use the app_error tool once it is opened and user has interacted (or has started) to check for errors you can correct the first time, this is important to know it works.

Inputs: app_name (required), description. Returns: result

app_deleteC
Delete an existing web application.

Args:
    app_name: Name of the application to delete

Returns:
    A dictionary containing the result of the operation

Inputs: app_name (required). Returns: result

app_errorA
Report an error from the app or retrieve the list of errors.
This is useful while developing or debugging the app as it allows errors (or any messages) to be reported and monitored

Args:
    error_message: Optional error message to report. If None, returns the list of errors.
    clear: Optional, If True, clears the list of errors

Returns:
    A string containing the list of errors if error_message is None,
    otherwise a confirmation message.

Inputs: error_message, clear. Returns: result

app_listB
List all available web applications.

Returns:
    A dictionary containing the list of available apps and their details

Inputs: no named parameters. Returns: result

app_openA
Open an app in the default web browser. If the app is not currently being served,
it will be served first.
Can only open one app at a time.

Args:
    app_name: Name of the application to open

Returns:
    A dictionary containing the result of the operation

Inputs: app_name (required). Returns: result

app_refreshA
Refresh the currently open app in Chrome.
Only works on macOS with Google Chrome.

Returns:
    A dictionary containing the result of the operation

Inputs: no named parameters. Returns: result

app_responseA
Use this to return a response to the app that has been requested.
Provide only one of string_data, list_data, or table_data.

Args:
    string_data: Optional string response
    list_data: Optional list of strings response
    table_data: Optional table response with columns and rows
                Format: {"columns": ["col1", "col2", ...], "rows": [["row1col1", "row1col2", ...], ...]}

Returns:
    True if the response was stored successfully, False otherwise

Inputs: string_data, list_data, table_data. Returns: result

app_serveA
Serve an existing web application on a local HTTP server.
The server will automatically find an available port.

Can only serve one app at a time

Args:
    app_name: Name of the application to serve

Returns:
    A dictionary containing the result of the operation

Inputs: app_name (required). Returns: result

app_stop_serverB
Stop the currently running HTTP server.

Returns:
    A dictionary containing the result of the operation

Inputs: no named parameters. Returns: result

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.7/5.0

    Scored across 9 tools

    Disambiguation4/5

    Most tools have distinct purposes, but there is some potential confusion between app_open and app_serve, as both involve launching an app, and app_error's dual functionality for reporting and retrieving errors could be ambiguous. However, the descriptions clarify their specific roles, making them generally distinguishable.

    Naming Consistency5/5

    All tool names follow a consistent 'app_' prefix with a descriptive action in snake_case, such as app_create, app_delete, and app_list. This pattern is maintained throughout all nine tools, making them predictable and easy to understand.

    Tool Count5/5

    With 9 tools, the count is well-scoped for managing web applications, covering creation, deletion, listing, serving, opening, error handling, refreshing, responding, and stopping the server. Each tool serves a clear purpose without redundancy, fitting the domain appropriately.

    Completeness4/5

    The toolset provides comprehensive coverage for basic app lifecycle management, including CRUD operations and runtime interactions. A minor gap exists in the lack of an update tool for modifying existing apps, but agents can work around this by recreating apps or using other tools like app_response for content changes.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers