Skip to content
Monomer

Supported clients and warehouses

The agent clients with a setup guide and the warehouses you can connect, with their settings and sign-in methods. Both tables are built from the same sources the app uses.

Monomer works with MCP clients that support remote servers and OAuth client metadata. Monomer sign-in says whether the client has been confirmed to complete Monomer sign-in; the others accept the same server address, but their sign-in has not been confirmed yet. Current tools says whether Monomer has confirmed the client with today’s tools, including monomer_describe; earlier sign-in and tool-discovery checks don’t confirm it. Your own program can connect over REST; see Connect a REST client.

ClientMonomer sign-inCurrent toolsGuide
ClaudeVerifiedNot yet verifiedConnect Claude
Claude CodeVerifiedNot yet verifiedConnect Claude Code
CodexVerifiedNot yet verifiedConnect Codex
CursorNot yet verifiedNot yet verifiedConnect Cursor
VS CodeNot yet verifiedNot yet verifiedConnect VS Code

Each warehouse type needs the required settings and one of its sign-in methods. Names in code are the fields of the connector schema; the app shows them as form labels. Add a warehouse connection explains each field and the read-only account to use.

WarehouseconnectorTypeRequired settingsOptional settingsSign-in methods
PostgreSQLPOSTGRESQLhost, port, databaseschema, sslModeUsername and password (USERNAME_PASSWORD)
BigQueryBIGQUERYprojectId, locationNoneService account JSON (SERVICE_ACCOUNT_JSON)
SnowflakeSNOWFLAKEaccount, warehouse, databaseschema, roleUsername and password (USERNAME_PASSWORD); Username and private key (USERNAME_PRIVATE_KEY)
TrinoTRINOhost, port, catalogschema, ssl, sslVerificationUsername and password (USERNAME_PASSWORD)
RedshiftREDSHIFThost, port, databaseschema, sslModeUsername and password (USERNAME_PASSWORD); AWS IAM (AWS_IAM)
DatabricksDATABRICKShost, warehouseIdcatalog, schemaAccess token (ACCESS_TOKEN); OAuth client ID and secret (OAUTH_CLIENT)