MCP Server Modal
# mcp-server-modal
https://docs.google.com/document/d/1DcrSKbcsXrzCoyMe0XtAsDcE3IgBV1bLirUG80VxPq8/edit?tab=t.0
An MCP Server that allows users to deploy python scripts to [modal](https://modal.com/).
## Installation
Make sure that modal is setup:
```
pip install modal
python3 -m modal setup
```
Then setup the server with the filesystem server in your Claude desktop app:
```
{
"mcpServers": {
"mcp-server-modal": {
"command": "uv",
"args": [
"--directory",
"/path/to/mcp-server-modal",
"run",
"modal-server"
]
},
"filesystem": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-filesystem",
"/Users/user/Desktop/",
"/path/to/other/dir"
]
}
}
}
```
## Usage
In claude, give a python script and ask it to create a modal application and deploy it for you. After code generation, you will get a link to the modal application which you can try out and share with others.
## Development
```
npx @modelcontextprotocol/inspector uv --directory /path/to/mcp-server-modal run modal-server
```
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools, as there are no other tools to confuse it with. The tool's purpose is inherently distinct by default in this minimal set.
A single tool inherently exhibits perfect naming consistency, as there are no other tool names to compare it against or deviate from. The name 'deploy' follows a clear verb pattern, but consistency is trivially achieved with only one element.
A single tool is generally too few for most server purposes, as it limits functionality and suggests an incomplete or overly narrow scope. For a server named 'MCP Server Modal', which implies modal interactions or deployments, one tool feels insufficient to cover meaningful workflows or operations.
With only a 'deploy' tool, the surface is severely incomplete for any reasonable domain inferred from the server name. There are obvious gaps, such as lacking tools for managing, updating, listing, or deleting deployments, making it impossible for agents to perform basic lifecycle operations without workarounds.