Tealfabric MCP Server for Cursor
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TEALFABRIC_API_KEY | Yes | Tealfabric API key (X-API-Key / Bearer) | |
| TEALFABRIC_API_URL | No | Tealfabric base URL | https://tealfabric.io |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| tealfabric_list_connectorsA | List Tealfabric connectors, get a specific connector, or fetch connector parameters. |
| tealfabric_test_connectorB | Test a connector configuration payload against the Tealfabric connectors test endpoint. |
| tealfabric_get_connector_oauth2_requiredB | Check whether a connector requires OAuth2 authentication. |
| tealfabric_list_integrationsC | List integrations or query integration details/status/statistics/execution history via action filters. |
| tealfabric_create_integrationC | Create a new integration. |
| tealfabric_update_integrationC | Update an existing integration. |
| tealfabric_list_webappsA | List Tealfabric webapps for the authenticated tenant. Optionally filter by search or limit. |
| tealfabric_get_webappA | Get a single Tealfabric webapp by ID. Optionally request a specific version. |
| tealfabric_create_webappA | Create a new Tealfabric webapp. Returns the new webapp_id. |
| tealfabric_update_webappC | Update an existing Tealfabric webapp (e.g. page_content, name). |
| tealfabric_publish_webappB | Publish a Tealfabric webapp (make the current version live). |
| tealfabric_list_processesA | List Tealfabric ProcessFlow processes for the authenticated tenant. |
| tealfabric_get_processA | Get a single Tealfabric process by ID. |
| tealfabric_list_process_stepsC | List process steps for a given process. |
| tealfabric_get_process_stepA | Get a single process step by step_id. |
| tealfabric_execute_processB | Execute a Tealfabric process with optional input. |
| tealfabric_create_processC | Create a new Tealfabric process (process flow). Returns the new process_id. |
| tealfabric_update_processC | Update an existing Tealfabric process (process flow). |
| tealfabric_create_process_stepB | Create a new process step in a process flow. Returns the new step_id. |
| tealfabric_update_process_stepC | Update an existing process step in a process flow. |
| tealfabric_list_documentsA | List documents/files in a Tealfabric documents directory. Use for browsing package files. |
| tealfabric_get_document_metadataC | Get metadata for a document/file in Tealfabric documents storage. |
| tealfabric_download_documentA | Download a document/file from Tealfabric documents storage. Returns file content as base64 for binary-safe transfer. |
| tealfabric_upload_documentA | Upload a file to Tealfabric documents storage. Use to publish built package files for delivery. The file is stored in destination_path using the uploaded file's name. |
| tealfabric_move_documentA | Move or rename a file/directory in Tealfabric documents storage. Use to update package paths or reorganize. |
| tealfabric_delete_documentA | Delete a file or directory from Tealfabric documents storage. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 26 tools
Each tool maps to a clear resource-and-action pair: connectors, integrations, webapps, processes, process steps, and documents are kept separate. Even the list tools that can fetch specific details remain clearly distinct from the other get/test/execute operations.
All tools share the tealfabric_ prefix and follow a consistent snake_case verb_noun pattern (list_*, get_*, create_*, update_*, test_*, delete_*). The longer get_connector_oauth2_required name still fits the overall convention.
At 26 tools, the surface is on the heavy side and above the typical comfortable MCP range. However, the count reflects five distinct resource domains with focused operations rather than duplicate or random tools, so it feels large but not bloated.
There are significant lifecycle gaps: integrations, webapps, processes, and process steps have create/update but no delete, and webapps have publish but no unpublish/delete. Agents managing these resources will hit dead ends for teardown or cleanup workflows.