Cyera DataPort

Connect AI assistants to Cyera DataPort data via Snowflake.

Type: Community

Source Type: Repository

Description: Cyera DataPort MCP server provides AI assistants with read-only access to Cyera DataPort data in your Snowflake account. It enables querying data classifications, sensitivity labels, and lineage to support data-governance workflows.

Configuration Parameters:

  • Snowflake Account * - Snowflake account identifier (e.g. xy12345.us-east-1).

  • Snowflake User * - Snowflake service user (e.g. DATAPORT_MCP_USER).

  • Snowflake RSA Private Key * (sensitive) - PEM-encoded private key contents for key-pair auth.

  • Snowflake RSA Key Passphrase (sensitive) (optional) - Passphrase for the RSA key (optional).

  • Snowflake Role (optional) - Snowflake role. Default: DATAPORT_MCP_READONLY.

  • Snowflake Database (optional) - Snowflake database. Default: CYERA_DATAPORT.

  • Snowflake Warehouse (optional) - Snowflake warehouse. Default: WH_LARGE.

  • Snowflake Schema (optional) - Snowflake schema. Default: product.

  • AWS Access Key ID * (sensitive) - AWS access key for the DataPort context S3 bucket.

  • AWS Secret Access Key * (sensitive) - AWS secret access key paired with the access key ID.

  • S3 Bucket Name (optional) - DataPort context bucket. Default: edp-mcp.

Setup Steps:

  1. In Snowflake, create or identify a service user (e.g. DATAPORT_MCP_USER) and grant it the DATAPORT_MCP_READONLY role (or a custom read-only role over the DataPort schema).

  2. Generate an RSA key pair, assign the public key to the user, and have the PEM-encoded private key ready (with passphrase if encrypted).

  3. In AWS IAM, create or use a service user with s3:GetObject and s3:ListBucket on the DataPort context bucket. Generate an Access Key ID and Secret Access Key.

  4. When creating the connection in Natoma, enter the Snowflake account/user/key fields and AWS access key fields, then save.

Last updated