tealfabric-team-marketplace

Keep Tealfabric API credentials out of source control and logs.

- Never commit real values for `TEALFABRIC_API_KEY`.
- Prefer local prompts or local environment variables for secrets.
- Do not paste API keys into code examples, docs, issues, or commits.
- When sharing config, replace keys with placeholders like `tf_live_...`.

MCP server: tealfabric

{
  "command": "node",
  "args": [
    "${workspaceFolder}/dist/index.js"
  ],
  "env": {
    "TEALFABRIC_API_KEY": "${input:tealfabric_api_key}",
    "TEALFABRIC_API_URL": "https://tealfabric.io"
  }
}

Verify build, docs, and plugin metadata before publishing.

# Release Readiness Agent

Before marketplace publication:

1. Run `npm run build`.
2. Run `npm run validate:marketplace`.
3. Confirm `CHANGELOG.md` has the target version section.
4. Confirm plugin `version` matches release version in `plugins/tealfabric-mcp/.cursor-plugin/plugin.json`.
5. Confirm no secrets are committed.

Minimal-call pattern for creating and updating a Tealfabric integration.

# Integration Create Update Quick

Use this when the task is only integration create/update.

1. Check existing first:

```json
{"tool":"tealfabric_list_integrations","args":{"search":"<name-fragment>"}}
```

2. Create with required fields only:

```json
{"tool":"tealfabric_create_integration","args":{"name":"<integration-name>","type":"<integration-type>"}}
```

3. Update optional metadata after ID is known:

```json
{"tool":"tealfabric_update_integration","args":{"integration_id":"<id>","description":"<text>","is_active":true}}
```

Rules:
- Do not send optional fields during create unless explicitly required.
- If update fails, verify `integration_id` via `tealfabric_list_integrations` with `action:"get"`.

Use MCP tools to list, create, and update Tealfabric integrations and connectors.

# Tealfabric Integration Workflows

Use these MCP tools in order:

1. `tealfabric_list_connectors` to discover connectors.
2. `tealfabric_get_connector_oauth2_required` to verify auth expectations.
3. `tealfabric_test_connector` to validate connector config payloads.
4. `tealfabric_create_integration` to create an integration.
5. `tealfabric_update_integration` to patch integration metadata/status.
6. `tealfabric_list_integrations` for operational checks and filtering.

Reduce iterations and token use by following strict, known-good tool call patterns.

# Tealfabric MCP Tool Call Efficiency

Use this skill when you need reliable MCP calls with minimal retries.

## Objective

- Minimize trial-and-error with tool schemas.
- Use short call sequences that return actionable data quickly.
- Prefer deterministic payloads and avoid over-supplying fields.

## Core Rules

1. Start with a list tool before create/update unless the user already gave exact IDs.
2. Send only required fields first; add optional fields in follow-up updates.
3. Keep payload keys exactly aligned to tool schema names.
4. For enum-like fields, reuse known values from docs/examples.
5. If a call fails, fix one parameter at a time (do not rewrite whole payload blindly).

## Fast Paths

### Connectors: find and validate

1. `tealfabric_list_connectors` with empty input.
2. If connector identified, call `tealfabric_get_connector_oauth2_required`.
3. Call `tealfabric_test_connector` with minimal connector config payload.

Example minimal envelopes:

```json
{
  "tool": "tealfabric_list_connectors",
  "args": {}
}
```

```json
{
  "tool": "tealfabric_get_connector_oauth2_required",
  "args": {
    "connector_id": "YOUR_CONNECTOR_ID"
  }
}
```

```json
{
  "tool": "tealfabric_test_connector",
  "args": {
    "payload": {
      "connector_id": "YOUR_CONNECTOR_ID"
    }
  }
}
```

### Integrations: create with minimum risk

1. `tealfabric_list_integrations` to avoid duplicates.
2. `tealfabric_create_integration` with required fields only (`name`, `type`).
3. `tealfabric_update_integration` for optional metadata once ID is confirmed.

```json
{
  "tool": "tealfabric_create_integration",
  "args": {
    "name": "Salesforce Sync",
    "type": "salesforce"
  }
}
```

```json
{
  "tool": "tealfabric_update_integration",
  "args": {
    "integration_id": "YOUR_INTEGRATION_ID",
    "description": "Sync leads nightly",
    "is_active": true
  }
}
```

## Recovery Path (When Calls Fail)

1. Read the error and identify whether it is:
   - missing required key
   - invalid enum/value
   - wrong identifier key name
2. Retry once with only the corrected field(s).
3. If still failing, call relevant list/get tool to refresh IDs/state.

## Anti-Patterns to Avoid

- Passing large speculative payloads to create endpoints.
- Mixing connector and integration IDs in the same field.
- Repeated retries without changing payload semantics.
- Adding undocumented keys.