List available built-in source connector types: pulsar-admin sources available-sources — this shows connectors packaged with your Pulsar distribution (e.g., kafka, rabbitmq, mqtt, debezium-postgres).
Create a source connector: pulsar-admin sources create --name {source-name} --source-type {type} --destination-topic-name persistent://{tenant}/{namespace}/{topic} --source-config-file {config.yaml} where config.yaml contains connector-specific settings.
For a Debezium Postgres source, the config file must include database.hostname, database.port, database.user, database.password, database.dbname, and plugin.name (e.g., pgoutput); check current Pulsar IO Debezium docs for the full required field list.
Check source status: pulsar-admin sources status --name {source-name} --namespace {tenant}/{namespace}
Pulsar IO connectors run as Pulsar Functions internally; resource limits (CPU, RAM) for the connector are configured via --cpu and --ram flags on create/update — not in the connector config file.
Some source connectors require additional JARs not bundled with the default Pulsar distribution; download the NAR file from the Pulsar connector catalog and deploy with --archive rather than --source-type for custom connectors.
Pulsar IO Debezium connectors require a dedicated replication slot in Postgres and will retain it even if the connector is paused — monitor for replication slot bloat on the Postgres side.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp