- Home
- MCP servers
- Apps Script
Apps Script
- typescript
0
GitHub Stars
typescript
Language
5 months ago
First Indexed
2 months ago
Catalog Refreshed
Documentation & install
Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.
Installation
Add the following to your MCP client configuration file.
Configuration
View docs{
"mcpServers": {
"sam-ent-appscript-mcp": {
"command": "uv",
"args": [
"run",
"appscript-mcp"
],
"env": {
"MCP_TIMEOUT": "30000",
"MCP_TOOL_TIMEOUT": "90000"
}
}
}
}You can manage Google Apps Script projects from a single MCP server. Create, edit, execute, deploy, and monitor Apps Script projects using natural language through a local or remote MCP client. It streamlines working with Apps Script by exposing project and code actions as commands you can phrase conversationally.
How to use
Start by authenticating with Google to access your Apps Script projects, then use the toolset to list your projects, read and edit files, run functions, and manage deployments. Typical workflows include: asking to list all script projects, creating a new project, adding or updating script files, executing a function with parameters, deploying a new version, and viewing recent executions.
How to install
# Clone the repository
git clone https://github.com/sam-ent/appscript-mcp.git
cd appscript-mcp
# Install with uv (recommended)
uv sync
# Or install with pip
pip install -e .
Configuration and notes
Prerequisites include setting up a Google Cloud project with the Apps Script API and Google Drive API enabled, plus OAuth credentials. You will configure a local or remote MCP client to point at your server. The server supports a local, stdio-style runtime and can also be run via an HTTP endpoint if provided.
To run the server locally, the recommended flow is to start the MCP server process directly. The example uses the UV runtime to launch the server from a local directory named appscript-mcp.
Environment variables exposed by the server influence timeouts and operation limits. You can set them in your client configuration when running the server.
Security and authentication
On first use, authenticate with Google to grant access to your Apps Script projects. The authentication flow includes starting the OAuth process in your client, visiting the authorization URL in a browser, and completing the flow with the redirected URL. Credentials are cached for subsequent sessions to avoid repeated authorizations.
Development and testing
uv run pytest tests/ -v
uv run appscript-mcp
Usage quick reference
-
List projects: "Show me my Apps Script projects"
-
Create a project: "Create a new Apps Script project called 'Email Automation'"
-
Add code to a project: "Add a function to my Email Automation script that sends a daily summary email"
-
Run a function: "Run the sendDailySummary function in my Email Automation script"
-
Deploy: "Create a production deployment for my Email Automation script"
Available tools
start_google_auth
Begin the Google OAuth flow to authenticate the MCP server with Google APIs.
complete_google_auth
Complete OAuth with the provided redirect URL to obtain access tokens.
list_script_projects
List all Apps Script projects accessible to your authenticated account.
get_script_project
Retrieve details for a specific Apps Script project, including all files.
get_script_content
Fetch the content of a specific file within a project.
create_script_project
Create a new Apps Script project.
update_script_content
Update files within an Apps Script project.
run_script_function
Execute a function inside a script with optional parameters.
create_deployment
Create a new deployment for a project.
list_deployments
List all deployments for a project.
update_deployment
Update deployment configuration.
delete_deployment
Delete a deployment.
list_script_processes
View recent script executions and their statuses.