Plugins

The Plugins section includes plugin management and a separate MCP Servers page. Plugins have Installed and Explore views and can bundle multiple capabilities. Filters include Reads, Writes, Fact stores, Transforms, and Secret providers.

Official plugins come from the shared registry; workspace plugins can be authored and published through the plugin authoring workflow. Inspect sandbox test results before approving publication. Configuring a remote MCP server is a separate flow for discovering and calling external tools.

Connector manifest

A complete minimal manifest:

{
  "kind": "connector",
  "name": "example-orders",
  "version": "1.0.0",
  "supportedModes": ["full_refresh", "incremental"],
  "features": { "exactlyOnce": false, "discover": { "deep": true } },
  "configSchema": {
    "type": "object",
    "required": ["host"],
    "properties": {
      "host": { "type": "string", "description": "Warehouse host" },
      "port": { "type": "integer", "default": 5432 },
      "password": { "type": "string", "secret": true }
    }
  },
  "selectorSchema": { "type": "object", "properties": {} }
}

A manifest declares capabilities; it does not implement a connector. Supported modes, discovery depth, and exactly-once behavior must match its actual runtime. An OAuth feature flag does not by itself create an authorization flow.

Configuration schemas

Types include string, number, integer, boolean, array, and object. Object schemas use properties and an object-level required field list. Other settings include defaults, enums, descriptions, secret, and multiline hints. Selectors narrow a particular use (table, object, path, filters) separately from installation configuration.

Keep credentials in configuration or supported secret references. The secret hint is not proof that every export or shared view is redacted. Avoid copying secrets into plans, prompts, or evidence.

Transforms and tools

Transforms declare operation, runtime tool, execution mode, parameter schema, input/output bindings, and lineage mode. They must be installed and executable; runtimeSupported: false blocks preflight. Lineage can be row-preserving, explicit, or dropped; inspect this before relying on evidence.

External MCP servers have their own transport and authentication configuration. They differ from connecting an assistant to Semogram. Installation or a connection check does not start automatic ingestion or prove write permissions. See Connect data.