Conector

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.

Related MCP server: mcpgate

Features

Quick start

You need Node.js 22 or later.

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

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.

Connect an agent

Each agent authenticates with its own access token (cnr_…) and talks to http://<server>/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. It has no dependencies, so you can copy it to any machine with Node.js.

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):

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.

Users and security

• Roles: admins manage users, OAuth apps and shared connections. Members connect their own apps and use the shared ones. Invitation and password reset links work once, and Conector never sends e-mail.

• Tokens act as their user, can be limited to some apps and are shown only once. Conector stores only their SHA-256 hash.

• Passwords are hashed with scrypt and must be at least 12 characters long. Repeated failed sign-ins are throttled.

• The panel sets a strict Content Security Policy and checks a CSRF token and the origin on every form. It accepts only known Host headers, which blocks DNS rebinding, and binds to 127.0.0.1 by default.

• App URLs built from user input (subdomains, self-hosted instances) are validated, so credentials can't be sent to another server.

• The audit log records every tool call and every change made in the panel. It never stores request payloads or credentials.

Back up CONECTOR_DATA_DIR: without master.key, the stored credentials can't be decrypted. To report a vulnerability, see SECURITY.md.

REST API

The same tokens work for scripts and automations:

curl -H "Authorization: Bearer $CONECTOR_TOKEN" http://localhost:8790/api/v1/apps
curl -H "Authorization: Bearer $CONECTOR_TOKEN" -H "Content-Type: application/json" \
     -d '{"method":"GET","path":"/user"}' http://localhost:8790/api/v1/apps/github/request

Command line

conector start                    Start the server
conector setup-link               Print a link to create the first admin account
conector users | tokens           List users or access tokens
conector invite <email> [--admin] Print an invitation link
conector reset-link <email>       Print a password reset link
conector token <email> [--apps a,b] [--name N]
conector revoke <token id>
conector agents | install <agent> Add Conector to an agent
conector apps [--connected]       List the catalog

Adding an app

Apps are plain data: a base URL, how to authenticate, a connection test and help text. A complete example:

{
  id: "acme", name: "Acme", category: "productivity", description: "Projects and tasks in Acme",
  website: "https://acme.example", docs: "https://developers.acme.example", logo: { favicon: "https://acme.example" },
  baseUrl: "https://api.acme.example/v1",
  fields: [{ id: "token", label: "API key", secret: true }],
  auth: { type: "bearer" },
  help: "1) In Acme open “Settings” → “API”. 2) Click “New key” and paste it here.",
  test: { path: "/me", account: (d) => d.email },
}

docs/ADDING_APPS.md documents every option (OAuth, client credentials, AWS signatures, custom tools…). After editing, run npm run validate.

Development

npm run dev               # restart on changes
npm test                  # unit and end-to-end tests
npm run validate          # check every app definition (offline)
npm run validate:network  # also call each app's API with fake credentials
npm run logos             # regenerate app logos (npm run logos -- --agents for agents)

The code is plain JavaScript (ES modules), with three runtime dependencies: Express, the MCP SDK and Zod. Pages are rendered on the server with an escaping template tag. The browser script is small, plain JavaScript.

bin/        conector CLI and the stdio bridge
src/        server, MCP, auth, encrypted store, OAuth
src/catalog app definitions (apps/*.js) and the engine that turns them into tools
src/ui      pages, layout and icons
public/     CSS, JavaScript, fonts, brand and logos
scripts/    catalog validator and logo generator
test/       node:test suites

Contributing

New apps, agent install guides, fixes and ideas are welcome. See CONTRIBUTING.md to get started.

Powered by Secra Solutions

Secra Solutions builds and maintains Conector, and releases it as open source so anyone can give their AI agents safe access to the tools they use.

Conector is our first open-source initiative for the community. If you find it useful, we'll launch more: star the repo, open an issue or send a pull request, and tell us what you'd like us to build next.

Credits

• Inspired by Composio.

• Geist fonts (SIL Open Font License 1.1), Phosphor icons (MIT) and brand glyphs from Simple Icons (CC0).

• App and agent names and logos are trademarks of their owners. They are shown only to identify each service and don't imply endorsement.

License

MIT