mcpField
C
connection-manager

connection-manager

github.com/lyticsData & databases456 installsUpdated 3w ago
Repository

About connection-manager

Connection Manager is a skill for browsing and managing Lytics connections to external systems and their auth providers. It uses the Lytics API to inspect integrations and requires confirmation for write operations while protecting credential values.

Key features

  1. 01List and inspect connections
  2. 02List and inspect auth providers
  3. 03Find available integration types
  4. 04Discover connection data and schema
  5. 05Confirm writes and protect credentials

Use cases

  1. 01Review existing external system connections
  2. 02Find a provider and configure its authentication
  3. 03Scan a connection to inspect available data and schema

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/lytics/agent-skills --skill connection-manager

After installing, type/connection-managerin Claude Code to confirm it loaded.

Details

From the project README

Connection Manager

Purpose

Browse and manage connections (external system configurations) and auth providers (credentials/tokens). Connections define how Lytics communicates with external platforms.

Environment

Requires authenticated API access. See ../references/auth.md for credential resolution.

API Endpoints

Connections
# List all connections
curl -s "${LYTICS_API_URL:-https://api.lytics.io}/v2/connection" \
  -H "Authorization: ${LYTICS_API_TOKEN}"

# Get connection
curl -s "${LYTICS_API_URL:-https://api.lytics.io}/v2/connection/${CONNECTION_ID}" \
  -H "Authorization: ${LYTICS_API_TOKEN}"

# Create connection
curl -s -X POST "${LYTICS_API_URL:-https://api.lytics.io}/v2/connection" \
  -H "Authorization: ${LYTICS_API_TOKEN}" \
  -H "Content-Type: application/json" \
  -d '{ ... connection config ... }'

# Update connection
curl -s -X PUT "${LYTICS_API_URL:-https://api.lytics.io}/v2/connection/${CONNECTION_ID}" \
  -H "Authorization: ${LYTICS_API_TOKEN}" \
  -H "Content-Type: application/json" \
  -d '{ ... updated config ... }'

# Delete connection
curl -s -X DELETE "${LYTICS_API_URL:-https://api.lytics.io}/v2/connection/${CONNECTION_ID}" \
  -H "Authorization: ${LYTICS_API_TOKEN}"

# Scan connection (discover available data)
curl -s -X POST "${LYTICS_API_URL:-https://api.lytics.io}/v2/connection/${CONNECTION_ID}/scan" \
  -H "Authorization: ${LYTICS_API_TOKEN}"

# Get connection schema
curl -s "${LYTICS_API_URL:-https://api.lytics.io}/v2/connection/${CONNECTION_ID}/schema" \
  -H "Authorization: ${LYTICS_API_TOKEN}"

# Get connection table schema
curl -s "${LYTICS_API_URL:-https://api.lytics.io}/v2/connection/${CONNECTION_ID}/schema/${TABLE}" \
  -H "Authorization: ${LYTICS_API_TOKEN}"
Auth Providers
# List all auth providers
curl -s "${LYTICS_API_URL:-https://api.lytics.io}/v2/auth" \
  -H "Authorization: ${LYTICS_API_TOKEN}"

# Get auth by ID
curl -s "${LYTICS_API_URL:-https://api.lytics.io}/v2/auth/${AUTH_ID}" \
  -H "Authorization: ${LYTICS_API_TOKEN}"

# Get auth by type and ID
curl -s "${LYTICS_API_URL:-https://api.lytics.io}/v2/auth/${TYPE}/${AUTH_ID}" \
  -H "Authorization: ${LYTICS_API_TOKEN}"

# Create auth
curl -s -X POST "${LYTICS_API_URL:-https://api.lytics.io}/v2/auth/${TYPE}" \
  -H "Authorization: ${LYTICS_API_TOKEN}" \
  -H "Content-Type: application/json" \
  -d '{ ... auth credentials ... }'

# Update auth
curl -s -X PUT "${LYTICS_API_URL:-https://api.lytics.io}/v2/auth/${TYPE}/${AUTH_ID}" \
  -H "Authorization: ${LYTICS_API_TOKEN}" \
  -H "Content-Type: application/json" \
  -d '{ ... updated credentials ... }'

# Delete auth
curl -s -X DELETE "${LYTICS_API_URL:-https://api.lytics.io}/v2/auth/${AUTH_ID}" \
  -H "Authorization: ${LYTICS_API_TOKEN}"
Providers (available integration types)
curl -s "${LYTICS_API_URL:-https://api.lytics.io}/v2/provider" \
  -H "Authorization: ${LYTICS_API_TOKEN}"

Behavior

For Read Operations (list, get, scan)

Execute immediately. Display connections in a table format showing:

  • Connection ID, name, type, status, last used
For Write Operations (create, update, delete)

Use the confirmation-gate pattern. Auth credentials are sensitive -- never log or display full credential values.

Connection Discovery Flow

When setting up a new integration:

  1. List available providers (GET /v2/provider)
  2. Create auth for the chosen provider
  3. Create connection using the auth
  4. Scan connection to discover available data
  5. Review connection schema

Error Handling

  • Auth expired: Suggest re-creating the auth provider
  • Connection test failure: Check auth credentials, network access
  • Provider not found: List available providers

Dependencies

  • Uses: ../references/auth.md, ../references/api-client.md, ../references/confirmation-gate.md

Comments

Markdown supported