Skip to main content
Glama
michaelneale

Goose App Maker MCP

by michaelneale
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
app_listB
List all available web applications.

Returns:
    A dictionary containing the list of available apps and their details
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
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.
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
app_stop_serverB
Stop the currently running HTTP server.

Returns:
    A dictionary containing the result of the operation
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
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
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
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.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

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.

Resources