Tealfabric MCP Server for Cursor
OfficialConnects Cursor to Tealfabric so the model can manage connectors, integrations, webapps, ProcessFlow processes/steps, and document storage.
Connectors: list/get connectors or parameters, test connector configuration payloads, and check whether OAuth2 is required.
Integrations: list/query integrations (details, statistics, status, execution history) and create/update integrations.
Webapps: list/get/create/update/publish webapps.
ProcessFlow: list/get/execute/create/update processes, and list/get/create/update process steps.
Documents: list directory contents, get file metadata, download files as base64, upload local files, move/rename files or directories, and delete files/directories.
Note: the README advertises some tools not present in the schema, such as execute/delete integration, unpublish/delete/create webapp version, delete/retire process, delete process step, read/write document text, and document tree listing.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Tealfabric MCP Server for Cursor upload the built package to the documents folder"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Tealfabric MCP Server for Cursor
MCP (Model Context Protocol) server that connects Cursor IDE to the Tealfabric platform. The model in Cursor can manage connectors, integrations, webapps, ProcessFlow processes/steps, and documents (including text read/write and package delivery).
Prerequisites
Node.js 18+
A Tealfabric API key (create one in Tealfabric: User settings → API Keys, or
POST /api/v1/api-keyswhen logged in)Key scopes as needed:
connectors.read|write,integrations.read|write|execute|delete,webapps.read|write,processflow.read|write,documents.read|write
Related MCP server: Azure DevOps MCP Server
Install
cd cursor-mcp-tealfabric
npm install
npm run buildUpgrading from 0.1.x? Read docs/RELEASE_NOTES_0.2.0.md and docs/MIGRATING.md — publish, create-webapp, list-webapps, and test-connector inputs changed.
Cursor setup
Create an API key in Tealfabric (if you don’t have one).
Add the MCP server in Cursor:
Cursor Settings (Cmd+, / Ctrl+,) → Tools & MCP → Add new MCP server
Or create/edit
.cursor/mcp.jsonin your project (or~/.cursor/mcp.jsonfor global):
{
"mcpServers": {
"tealfabric": {
"command": "node",
"args": ["/ABSOLUTE/PATH/TO/cursor-mcp-tealfabric/dist/index.js"],
"env": {
"TEALFABRIC_API_KEY": "YOUR_API_KEY_HERE",
"TEALFABRIC_API_URL": "https://tealfabric.io"
}
}
}
}Replace:
YOUR_API_KEY_HEREwith your Tealfabric API key (e.g.tf_live_...)./ABSOLUTE/PATH/TO/cursor-mcp-tealfabric/...with the real path to this repo (e.g./Users/username/src/cursor-mcp-tealfabric/dist/index.js).
Restart Cursor so it picks up the new server.
Tools exposed to Cursor
Tool | Description |
| List connectors (optional action: get, parameters) |
| Test connector ( |
| Check whether connector requires OAuth2 |
| List integrations or query by action/filter |
| Create a new integration |
| Update an existing integration |
| Execute an integration (optional async/data) |
| Delete an integration |
| List webapps ( |
| Get one webapp by ID (optional version) |
| Create webapp ( |
| Update webapp (content, auth, public URI, etc.) |
| Publish a webapp version (requires |
| Unpublish a webapp |
| Create a new unpublished webapp version |
| Delete a webapp |
| List ProcessFlow processes |
| Get one process by ID |
| List steps of a process |
| Get one process step by step_id |
| Execute a process (optional input) |
| Create a new process |
| Update an existing process |
| Hard-delete a process |
| Soft-retire a process ( |
| Create a new step ( |
| Update an existing process step |
| Delete a process step |
| List documents in a directory |
| List documents as a tree |
| Get file metadata |
| Read UTF-8 text document |
| Write UTF-8 text document |
| Download a file (returns base64 payload) |
| Upload a file (e.g. built package) |
| Move or rename file/directory |
| Delete file or directory |
Environment variables
Variable | Required | Default | Description |
| Yes | — | Tealfabric API key (X-API-Key / Bearer) |
| No |
| Tealfabric base URL |
Security
Do not commit
.cursor/mcp.jsonif it contains your real API key. Use.cursor/mcp.json.example(without the key) and addmcp.jsonto.gitignore, or use Cursor’s UI so the key stays local.API keys are scoped to your user/tenant in Tealfabric; create keys with minimal required scopes if your platform supports it.
Documentation
Release notes (0.2.0): docs/RELEASE_NOTES_0.2.0.md
Migrating from 0.1.x: docs/MIGRATING.md
Developer guide (setup, tools, API mapping, extending): docs/DEVELOPER.md
Changelog: CHANGELOG.md
Tealfabric platform docs (WebApps, ProcessFlow, APIs): https://tealfabric.io/docs
Related projects
Tealfabric exposes the same MCP capabilities across different host environments. Each repo ships the appropriate packaging and setup for its platform:
Host | Repository |
Cursor (this repository) | |
Claude (Claude Code and compatible MCP clients) | |
Lovable |
Available Tools
37 toolstealfabric_create_integrationD
Create a new integration.
Inputs: name (required), type (required), status, is_active, +5 more.
tealfabric_create_processC
Create a new Tealfabric process (process flow). Returns the new process_id.
Inputs: name (required), type, status, category, +5 more.
tealfabric_create_process_stepC
Create a new process step in a process flow. Returns the new step_id.
Inputs: process_id (required), name, language, sequence, +9 more.
tealfabric_create_webappC
Create a new Tealfabric webapp (unpublished by default). Requires name, type, page_content, and webapp_user_id.
Inputs: name (required), type (required), page_content (required), webapp_user_id (required), +18 more.
tealfabric_create_webapp_versionA
Create a new unpublished version of a webapp (copies latest version).
Inputs: webapp_id (required).
tealfabric_delete_documentC
Delete a file or directory from Tealfabric documents storage.
Inputs: path (required), tenant_id.
tealfabric_delete_integrationC
Delete an integration by ID.
Inputs: integration_id (required).
tealfabric_delete_processA
Hard-delete a Tealfabric process by ID.
Inputs: process_id (required).
tealfabric_delete_process_stepC
Delete a process step by step_id.
Inputs: step_id (required).
tealfabric_delete_webappC
Delete a Tealfabric webapp by ID.
Inputs: webapp_id (required).
tealfabric_download_documentA
Download a document/file from Tealfabric documents storage. Returns file content as base64 for binary-safe transfer.
Inputs: file_path (required), tenant_id.
tealfabric_execute_integrationC
Execute an integration (optionally async) with optional call data.
Inputs: integration_id (required), data, async.
tealfabric_execute_processC
Execute a Tealfabric process with optional input.
Inputs: process_id (required), input.
tealfabric_get_connector_oauth2_requiredA
Check whether a connector requires OAuth2 authentication.
Inputs: connector_id (required).
tealfabric_get_document_metadataC
Get metadata for a document/file in Tealfabric documents storage.
Inputs: file_path (required), tenant_id.
tealfabric_get_processB
Get a single Tealfabric process by ID.
Inputs: process_id (required).
tealfabric_get_process_stepB
Get a single process step by step_id.
Inputs: step_id (required).
tealfabric_get_webappA
Get a single Tealfabric webapp by ID. Optionally request a specific version.
Inputs: webapp_id (required), version.
tealfabric_list_connectorsB
List Tealfabric connectors, get a specific connector, or fetch connector parameters.
Inputs: action, connector_id.
tealfabric_list_documentsB
List documents/files in a Tealfabric documents directory. Use for browsing package files.
Inputs: path, tenant_id.
tealfabric_list_document_treeC
List a Tealfabric documents directory as a tree (action=tree).
Inputs: path, max_depth, tenant_id.
tealfabric_list_integrationsC
List integrations or query integration details/status/statistics/execution history via action filters.
Inputs: page, type, limit, action, +8 more.
tealfabric_list_processesB
List Tealfabric ProcessFlow processes for the authenticated tenant.
Inputs: no named parameters.
tealfabric_list_process_stepsC
List process steps for a given process.
Inputs: process_id (required).
tealfabric_list_webappsC
List Tealfabric webapps for the authenticated tenant.
Inputs: page, type, search, sort_by, +4 more.
tealfabric_move_documentB
Move or rename a file/directory in Tealfabric documents storage. Use to update package paths or reorganize.
Inputs: new_path (required), old_path (required), tenant_id.
tealfabric_publish_webappB
Publish a Tealfabric webapp version (make that version live).
Inputs: version (required), webapp_id (required).
tealfabric_read_document_textB
Read a UTF-8 text document from Tealfabric documents storage (action=read-text).
Inputs: file_path (required), tenant_id.
tealfabric_retire_processA
Soft-retire a process (sets status inactive and prefixes name with ). Prefer this over hard delete when preserving history.
Inputs: process_id (required).
tealfabric_test_connectorC
Test a connector configuration against the Tealfabric connectors test endpoint.
Inputs: connector_id (required), configuration.
tealfabric_unpublish_webappB
Unpublish a Tealfabric webapp (take it offline).
Inputs: webapp_id (required).
tealfabric_update_integrationD
Update an existing integration.
Inputs: integration_id (required), name, type, status, +6 more.
tealfabric_update_processC
Update an existing Tealfabric process (process flow).
Inputs: process_id (required), name, type, status, +6 more.
tealfabric_update_process_stepC
Update an existing process step in a process flow.
Inputs: step_id (required), name, language, sequence, +11 more.
tealfabric_update_webappC
Update an existing Tealfabric webapp (content, auth, public URI, etc.).
Inputs: webapp_id (required), name, version, custom_js, +18 more.
tealfabric_upload_documentB
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.
Inputs: file_path (required), destination_path (required), tenant_id.
tealfabric_write_document_textB
Write UTF-8 text to a Tealfabric documents path (action=write-text; creates a backup).
Inputs: content (required), file_path (required), encoding, tenant_id.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 37 tools
Most tools target a distinct resource+action across five clear domains (connectors, integrations, webapps, processes, documents), and delete vs retire process is explicitly differentiated. However, tealfabric_list_documents vs tealfabric_list_document_tree overlap heavily (the latter is just an action variant), and tealfabric_update_webapp vs tealfabric_create_webapp_version vs tealfabric_publish_webapp have fuzzy boundaries around when to use which.
Every tool follows the same tealfabric_verb_noun snake_case pattern, with a stable verb vocabulary (list, get, create, update, delete, execute, publish, unpublish, move, read/write/download/upload). Compound nouns like process_step and webapp_version are used consistently rather than introducing new conventions.
37 tools is well past the 25+ threshold and is more surface than an agent can reliably route among in one context. While five resource domains partially justify the volume, consolidation is clearly possible (e.g. list_documents/list_document_tree as one tool with an action flag, like list_integrations already does).
Integrations, webapps, processes/steps, and documents each have near-full lifecycle coverage, including versioning, publish/unpublish, soft-retire, and binary-safe upload/download. Minor gaps remain: connectors are read/test only with no create/update, and there is no way to list or fetch individual webapp versions.
Maintenance
Related MCP Connectors
Deploy apps from GitHub, read build/runtime logs, and manage your app's users from your AI agent.
Plan Salesforce deploys, open pull requests and trigger pipelines from your AI client.
Run, debug, and triage tests from your IDE using natural language, no dashboard switching, no manual data transfers. The TestMu AI (formerly LambdaTest) MCP Server is a single remote server exposing four tool suites: HyperExecute — analyze your project, generate YAML configs and test runner commands, then monitor jobs and sessions. Automation — pull a TestID's details plus command, network, and console logs into one chat for instant root-cause analysis. Includes mobile app upload. SmartUI — explain pixel, layout, DOM, and perceptual changes in a visual regression run, with context-aware React/HTML/CSS fixes. Accessibility — audit any public URL or a local React app against WCAG and get ready-to-apply remediation steps. Connects over https://mcp.lambdatest.com/mcp using OAuth 2.1 — no API keys in your config. One-click install in Cursor; works with Claude, GitHub Copilot, Cline, and any MCP client. Tests execute on the TestMu AI cloud: 3,000+ browsers and 10,000+ real devices.
Use your Mac, Windows or Linux computer from ChatGPT, Claude or Codex: files, commands, documents.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceConnects Fledge functionality to Cursor AI, allowing interaction with Fledge instances via natural language commands.MIT
- AlicenseNot gradedqualityFmaintenanceEnables interaction with Azure DevOps through Cursor chat, providing tools to manage builds, pipelines, work items, sprints, and board operations. Supports secure authentication via Personal Access Tokens and allows natural language-driven DevOps task management.1MIT
- FlicenseNot gradedqualityFmaintenanceEnables interaction with Azure DevOps through natural language in Cursor IDE. Supports work item management, pull requests, builds, releases, test management, and guided workflows for development teams, QA testers, and release management.1-
- AlicenseNot gradedqualityDmaintenanceEnables management of TeamCity CI/CD operations through natural language commands, including builds, projects, tests, artifacts, and more.15 npmMIT