@hasna/connectors weekly downloads statistics

@hasna/connectors

Open-source connector platform for enabling, authenticating, and running API connectors from one package.

Install

bun install -g @hasna/connectors

What It Is

@hasna/connectors is a single-product runtime:

• connectors stay inside this repo and package
• projects enable the connectors they want through .connectors/manifest.json
• credentials live in the connectors data home (resolved by the in-package resolver; ~/.hasna/connectors/ until the XDG data home is adopted)
• CLI, MCP, REST, and the local API/OAuth server all use the same connector registry

Local or remote

Connectors runs locally by default, with nothing to configure: the CLI, the MCP server and the SDK run the connector engine in-process and keep connections in the local store.

To use a server instead (one you run yourself, or any service that speaks the /v1 API), point the client at it:

# One shell or CI job: environment variables
export CONNECTORS_API_URL=https://connectors.example.com
export CONNECTORS_API_KEY=...            # from your server administrator

# Or save it: the key is read from stdin or a hidden prompt, never from arguments
connectors login --api-url https://connectors.example.com
connectors config show                   # mode, server URL, whether a key is set
connectors logout                        # delete the stored key
connectors config unset api-url          # back to local mode

Settings resolve in this order: the --api-url / --api-key-stdin flags, then CONNECTORS_API_URL / CONNECTORS_API_KEY, then <connectors home>/config.json (mode 0600, written by connectors login), then local mode. A saved key is only sent to the server it was saved for, a server URL without a key is an error rather than a silent fall back to local mode, and plain http:// is refused for anything but loopback unless CONNECTORS_ALLOW_INSECURE_HTTP=1.

Service connectors work the same way in both modes:

connectors service list
connectors service describe openai       # auth methods, operations and their effects
printf '{"adminKey":"%s"}' "$OPENAI_ADMIN_KEY" | \
  connectors connections add openai --auth admin_key --label prod-admin --secrets-stdin
connectors connections add openai --auth admin_key --label ci --secret-env adminKey=OPENAI_ADMIN_KEY
connectors connections list
connectors connections check openai:prod-admin
connectors call openai <operation> --connection prod-admin --input '<json object>'
connectors runs list --limit 20

The shipped service connectors are anthropic, brandsight, cloudflare, cursor, godaddy, openai, opencode, stable and youtrust (Youtrust, formerly Yousign: signature requests, documents, recipients, audit trails and webhooks; see docs/providers/youtrust.md). A Youtrust connection picks its environment with a plain field:

connectors connections add youtrust --auth api_key --label prod \
  --field environment=production --secret-env apiKey=YOUTRUST_API_KEY   # default: sandbox
connectors call youtrust signature_requests.list --connection prod --input '{"limit":10}'

Secret connection fields are never accepted as arguments (--field refuses them); use --secret-env key=ENV_NAME, --secrets-stdin or the hidden prompt. Any operation that is not a read (write, billable, destructive, credential) needs --confirm. A credential result, such as a newly minted key, is shown once and never stored.

CLI

connectors --help

Typical flow:

connectors install github stripe
connectors auth github
printf '%s\n' "$STRIPE_API_KEY" | connectors auth stripe --key-stdin
connectors run github --help
connectors run stripe products list --limit 5

Key commands:

• connectors install writes project enablement to .connectors/manifest.json
• connectors list and connectors search browse the shared catalog
• connectors docs reads connector docs from the internal registry
• connectors auth stores credentials in the connectors data home (resolved by the in-package resolver)
• connectors auth <name> --key-stdin reads an API key or bearer token from stdin, and --key-env <VAR> reads it from the named environment variable. connectors setup and connectors llm set take the same two flags. Do not pass a key as a command-line value: it lands in shell history and the process list.
• connectors run executes connector commands from the one-product runtime
• connectors status and connectors doctor verify setup and auth state

Compact Output Defaults

CLI output is compact by default so agent terminals do not fill with huge catalogs, README sections, credential status tables, or API records.…