Conector

Connect 1,178 apps once and use them from Claude, Codex, Cursor, Gemini CLI, GitHub Copilot and 42 more AI agents.

Self-hosted and open source. Your credentials stay encrypted on your own server.

Quick start · Agents · Apps · Security · Add an app · About

Why Conector

AI agents can only use the tools they can reach. Wiring every agent to every app means juggling API keys, OAuth apps and config files on each machine, for each agent. Conector puts all of it in one place:

1. Connect an app once in the web panel, by signing in or pasting an API key.
2. Add Conector to your agents with one command or config snippet.
3. Every agent gets tools for every app you connected, over the Model Context Protocol.

Features

1,178 apps

GitHub, Gmail, Google Drive, Notion, Slack, Linear, HubSpot, Salesforce, Stripe, Microsoft 365, Jira and more. 107 connect with one click. The rest take an API key, a username and password, or nothing at all.

1,416 tools

Every app gets an authenticated <app>_request tool for its whole API. Many add specific tools such as outlook_search_mail , jira_search or slack_send_message .

47 agents

The panel shows the exact command or config file for each agent, with a token already filled in. conector install <agent> writes it for you.

Built for teams

Admins and members, invitation links, personal and shared connections, and per-agent tokens limited to the apps you choose.

Private by design

Credentials are encrypted with AES-256-GCM and only sent to the app they belong to. The panel loads no external scripts, fonts or images.

Easy to run

Node.js and three dependencies, or one docker compose up . Every tool call is recorded in an audit log.

Quick start

With Node.js 22 or later, in one command:

npx conector start

Installed from npm, Conector keeps its data in ~/.conector. For a permanent install, run npm install -g conector and then conector start.

With Docker:

docker run -d --name conector -p 127.0.0.1:8790:8790 -v conector-data:/data ghcr.io/secra-solutions/conector

docker logs conector # shows the setup link

Or from source:

git clone https://github.com/Secra-Solutions/Conector.git

cd Conector npm install npm start

The first start prints a one-time setup link:

Conector 0.1.0 listening on http://127.0.0.1:8790 — public URL http://localhost:8790

No users yet. Create the admin account at: http://localhost:8790/setup?code=…

Open it, create the admin account, and then:

1. Apps: pick an app and connect it.
2. Connect agents: pick your agent, click Create a token, and copy the command or snippet.
3. Ask your agent to use the app, for example: "list my open GitHub pull requests".

With Docker Compose

From a clone of the repository:

docker compose up -d

docker compose logs conector # shows the setup link

The data (users, tokens, encrypted credentials and the master key) lives in the conector-data volume. The compose file only exposes the panel on 127.0.0.1:8790. Images for amd64 and arm64 are published at ghcr.io/secra-solutions/conector: latest and X.Y.Z for releases, edge for the main branch.

Connect an agent

Each agent authenticates with its own access token (cnr_…) and talks to http:// /mcp over Streamable HTTP, with an Authorization: Bearer header. Agents that can only start local (stdio) servers use the bundled bridge, bin/stdio-bridge.js (or conector stdio), configured with CONECTOR_URL and CONECTOR_TOKEN. It has no dependencies, so you can copy it to any machine with Node.js. On the machine where Conector stores its data, an agent can also start conector mcp, which serves the same tools over stdio without the web server or a token.

Everything on one machine? Start the panel with npx conector start, connect your apps, and add Conector to your editor in one click. The button adds npx -y conector mcp, which reads the same data in ~/.conector, so there's no token to create:

From the panel, open Connect agents, pick your agent and click Create a token. Or, from a terminal on the server:

npm link                                    # makes the `conector` command available

conector agents # list the supported agents conector install claude-code # runs claude mcp add … with a new token conector install cursor --user you@example.com conector install codex --dry-run # show what it would do

conector install uses the agent's own CLI when it is installed. Otherwise it merges the entry into the agent's JSON or TOML config file and keeps a .conector-backup copy. When a file can't be merged safely (JSONC comments, YAML, an existing table), it prints the snippet for you to paste.

Apps

Each app page offers the simplest way to connect it:

• Continue with …: OAuth sign-in. An admin registers Conector's OAuth app once per provider under OAuth apps. The page shows the redirect URI and scopes to use. One registration covers all of the provider's apps: one Google OAuth app covers Gmail, Drive, Calendar, Sheets and the rest.
• API key, or username and password: step-by-step instructions to find the key, and a connection test when you save.
• Enable: public APIs that need no credentials.
• Microsoft 365: sign-in with a device code, with no app registration needed.

Connections are personal (only you) or shared (everyone in the workspace; only admins can create them). When both exist, your personal connection wins.

Configuration

Set these environment variables, or put them in a .env file next to package.json (see .env.example). When Conector is installed from npm, the .env file is read from the current directory instead.

To reach Conector from other machines or from cloud agents, put an HTTPS reverse proxy or tunnel in front of it (Caddy, nginx, Cloudflare Tunnel…) and set CONECTOR_PUBLIC_URL to its address.

Self-hosted apps must use https://, except on localhost. Many home servers have no certificate, so CONECTOR_ALLOW_PRIVATE_HTTP=1 also accepts http:// for pr