Tealfabric MCP Server for Cursor

Official

Overview Schema Source Related Servers Discussions Admin

tealfabric_update_webapp

Update an existing Tealfabric webapp's content, authentication, public URI, and settings. Use it to modify deployed webapps from Cursor without recreating them.

Instructions

Update an existing Tealfabric webapp (content, auth, public URI, etc.).

Input Schema

Name	Required	Description
`name`	No
`version`	No	Pin update to a numeric version when supported
`custom_js`	No
`page_head`	No
`webapp_id`	Yes	Webapp UUID
`custom_css`	No
`process_id`	No
`version_id`	No
`description`	No
`page_footer`	No
`page_header`	No
`public_uris`	No
`auth_require`	No
`code_snippet`	No
`http_headers`	No
`page_content`	No
`auth_transport`	No
`webapp_user_id`	No
`public_uri_host`	No
`public_uri_path`	No
`custom_referrer_policy`	No
`custom_security_policy`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed14 schema fields changedv0.2.0Nov 1, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
- addedInput schema / properties / auth_require
```
Added value: +{
+  "type": "boolean"
+}
```
- addedInput schema / properties / auth_transport
```
Added value: +{
+  "enum": [
+    "cookie",
+    "bearer",
+    "both"
+  ],
+  "type": "string"
+}
```
- addedInput schema / properties / code_snippet
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / custom_referrer_policy
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / custom_security_policy
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / http_headers
```
Added value: +{}
```
- addedInput schema / properties / page_head
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / public_uri_host
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / public_uri_path
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / public_uris
```
Added value: +{}
```
- addedInput schema / properties / version
```
Added value: +{
+  "description": "Pin update to a numeric version when supported",
+  "type": "number"
+}
```
- addedInput schema / properties / version_id
```
Added value: +{
+  "type": [
+    "string",
+    "number"
+  ]
+}
```
- addedInput schema / properties / webapp_user_id
```
Added value: +{
+  "type": "string"
+}
```
First observedv0.1.3Aug 30, 2026

TDQS

C2.5/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. It identifies this as a mutation, but does not state whether updates are partial or full, what happens to omitted fields, whether permissions are required, or what the response contains.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single front-loaded sentence with no wasted filler. However, the trailing 'etc.' is uninformative and the brevity is more under-specification than efficient concision for a 22-parameter mutation tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the high parameter count, no annotations, no output schema, and near-zero schema description coverage, the description is far too sparse. An agent would not know how to safely perform or scope the update.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 9% across 22 parameters, so the description must compensate. It mentions broad categories (content, auth, public URI) but leaves most parameters, including auth_transport, version, custom security settings, and headers, unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: update an existing Tealfabric webapp. The parenthetical gives example update areas, though only vaguely, and the tool is distinguishable from create/delete siblings by 'update an existing'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit guidance on when to use this tool versus alternatives such as create_webapp, publish_webapp, or create_webapp_version. Usage is only implied by the word 'update'.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

tealfabric_update_webapp

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools