Integrations
Enables creation and management of web application styles through custom CSS files stored in app directories
Supports web application functionality through custom JavaScript code, including integration with Goose API via a helper script
Provides package distribution capabilities, with instructions for building and publishing the MCP server to PyPI
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
Examples
Load data via goose (re-using its extensions)
goose keeps track of your apps:
Make apps on demand
Show rich tabular or list data as well
Usage from source
eg in goose:
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
Publishing
- Update version in
pyproject.toml
:
- Build the package:
- Publish to PyPI:
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:
- A blocking endpoint on the server side
- Asynchronous JavaScript on the client side
- 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:
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:
- The user initiates a request (e.g., clicking "Get List Response")
- The client calls one of the request functions (
gooseRequestText
,gooseRequestList
, orgooseRequestTable
) - The function generates a unique
responseId
and sends a request to Goose with instructions to callapp_response
with this ID - The function then calls
waitForResponse(responseId)
which polls the/wait_for_response/{responseId}
endpoint - This endpoint blocks until the response is available or a timeout occurs
- When the response is available, it's returned to the client and displayed
2. Server-Side Processing
On the server side:
- The
/wait_for_response/{responseId}
endpoint uses condition variables to block until a response is available - When Goose processes the request, it calls the
app_response
function with the response data and theresponseId
- The
app_response
function stores the response in theapp_responses
dictionary and notifies any waiting threads using the condition variable - 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:
- When a client requests a response that isn't available yet, a condition variable is created for that
responseId
- The HTTP handler thread waits on this condition with a timeout (30 seconds)
- When the response becomes available, the condition is notified
- If the timeout expires before the response is available, an error is returned
Key Components
Client-Side Functions
gooseRequestText(query)
: Requests a text responsegooseRequestList(query)
: Requests a list responsegooseRequestTable(query, columns)
: Requests a table response with specified columnswaitForResponse(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
This server cannot be installed
local-only server
The server can only run on the client's local machine because it depends on local resources.
This MCP server allows users to create, manage, and serve web applications through Goose, storing apps in configurable directories and providing web app serving capabilities.
Related MCP Servers
- AsecurityAlicenseAqualityA simple MCP server that facilitates website fetching through a configurable server platform using stdio or SSE transport, allowing integration with tools like Cursor for streamlined access.Last updated -223PythonMIT License
- -securityAlicense-qualityAn MCP server that enables fetching web content using the Node.js undici library, supporting various HTTP methods, content formats, and request configurations.Last updated -668TypeScriptMIT License
- AsecurityFlicenseAqualityAn MCP server implementation that enables interaction with the Unstructured API, providing tools to list, create, update, and manage sources, destinations, and workflows.Last updated -3925
- -securityAlicense-qualityAn MCP server that enables web searches using a SearxNG instance, allowing MCP-compatible applications like Goose to perform internet searches.Last updated -PythonGPL 3.0