@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 ~/.hasna/connectors/
• CLI, MCP, REST, and the dashboard all use the same connector registry

CLI

connectors --help

Typical flow:

connectors install github stripe
connectors auth github
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 ~/.hasna/connectors/
• connectors run executes connector commands from the one-product runtime
• connectors status and connectors doctor verify setup and auth state

MCP Server

connectors-mcp

HTTP mode

connectors-mcp --http            # http://127.0.0.1:8854/mcp
MCP_HTTP=1 connectors-mcp

Health: GET http://127.0.0.1:8854/health. MCP is also mounted on connectors-serve at /mcp.

REST API

connectors-serve

The local REST API is served by the one-product runtime at http://localhost:9876. Use @hasna/connectors-sdk with ConnectorsClient or LocalConnectorsClient for this local connectors-serve API.

Hosted SaaS products should use HostedConnectorsClient from @hasna/connectors-sdk. The hosted client talks to a platform /api/v1 endpoint with bearer API keys and does not require local connector installs or individual connector packages.

OpenActions And OpenAutomations Boundary

Connector operations may be exposed to OpenAutomations as @hasna/actions manifests, but Connectors remains the owner of connector discovery, enablement, consent, and credential health. An automation action should name the connector operation and pass only scoped inputs plus references to credentials that Connectors can resolve.

Recommended action shape:

{
  "schemaVersion": "1.0",
  "id": "connectors.github.issue.create",
  "name": "Create GitHub issue",
  "version": "1.0.0",
  "bindings": [
    {
      "kind": "sdk",
      "package": "@hasna/connectors",
      "export": "runConnectorOperation",
      "metadata": {
        "connector": "github",
        "operation": "issues.create"
      }
    }
  ],
  "secrets": [
    {
      "name": "github",
      "ref": "hasna/xyz/opensource/connectors/prod/github",
      "required": true,
      "redaction": "full"
    }
  ],
  "approval": {
    "mode": "manual",
    "requiresApproval": true,
    "reason": "Creates or mutates data in an external account"
  },
  "audit": {
    "eventSource": "hasna.connectors",
    "redactPaths": ["secrets", "input.token", "input.authorization"],
    "evidenceRefs": ["connector:github", "operation:issues.create", "credentialScope:repo"]
  }
}

OpenAutomations owns the durable run/action queue and DLQ. Connectors owns runtime auth checks, connector-specific consent, credential refresh, and provider response normalization. Raw OAuth tokens, API keys, refresh tokens, and session cookies must not be placed in automation specs, action queues, task comments, or run evidence; use secret references and redacted audit metadata.

Project Layout

Project-local enablement is lightweight:

.connectors/
├── manifest.json
└── index.ts

The package no longer copies full connector source trees into each project.

Remote Storage Sync

This package supports repo-owned remote PostgreSQL sync without the retired shared cloud runtime:

export HASNA_CONNECTORS_DATABASE_URL="postgres://..."
connectors storage status
connectors storage sync push
connectors storage sync pull

Data Directory

Data is stored in ~/.hasna/connectors/.

Contributor Notes

Contributor guidance for the one-repo / one-product model lives in docs/one-repo-one-product.md.

License

Apache-2.0 -- see LICENSE