Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Conector

by Secra-Solutionsversion 0.1.7i★ –iRuns on your computer
Registry nameio.github.Secra-Solutions/conector

Install

Overview

Description from the maker (original English)

Self-hosted MCP gateway: connect 1,178 apps once and use them from any AI agent.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Other
  • You need to fill in: CONECTOR_URL, CONECTOR_TOKEN

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • You fill in yourself: CONECTOR_URL, CONECTOR_TOKEN

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

  • npmNode.js installed (for the npx command)

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "conector": {
      "command": "npx",
      "args": [
        "-y",
        "conector",
        "stdio"
      ],
      "env": {
        "CONECTOR_URL": "your-value",
        "CONECTOR_TOKEN": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add conector --env CONECTOR_URL=your-value --env CONECTOR_TOKEN=your-value -- npx -y conector stdio

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "conector": {
      "command": "npx",
      "args": [
        "-y",
        "conector",
        "stdio"
      ],
      "env": {
        "CONECTOR_URL": "your-value",
        "CONECTOR_TOKEN": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "conector": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "conector",
        "stdio"
      ],
      "env": {
        "CONECTOR_URL": "your-value",
        "CONECTOR_TOKEN": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

  • CONECTOR_URL required env
    MCP endpoint of your Conector server
  • CONECTOR_TOKEN secret required env
    Access token (cnr_…) created in the Conector panel under Connect agents

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account Secra-Solutions, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

  • More stars than 0% of the other 32558 servers in this category
  • Published to the registry more recently than 74% of the other 32558 servers in this category
  • Basic checks equal to or better than 100% of the other 32558 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Conector safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: CONECTOR_URL, CONECTOR_TOKEN

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.7) reached the registry 13 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, FactLot

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago
Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday
Install

FactLot

by 9mp96ygnbk-alt

Cited CRE facts and deterministic calculators for agents: rent, CAM, debt sizing, IRR, parcel IDs.

Computer or cloudUpdated today
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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:

Agents
CLIsClaude Code, Codex, Gemini CLI, OpenCode, Amp, goose, Qwen Code, Factory Droid, Devin CLI, TRAE CLI, Mistral Vibe, Kimi Code CLI, Grok Build, Hermes Agent, Auggie CLI, CodeBuddy Code, Qoder CLI, MiniMax Code, Cortex Code, Deep Agents, fast-agent, Stakpak, ZCode, Pi, Oh My Pi, Muse Code, Autohand Code, CodeWhale, crow-cli, DimCode, Gajae Code, Minion Code, Nova, Poolside, siGit Code, VT Code, GLM Agent, Corust Agent
EditorsCursor, GitHub Copilot (VS Code), Cline, Kilo Code, Kiro, Junie, Google Antigravity
Desktop and webClaude Desktop, Hoplite
Not supported yetChatGPT (it requires OAuth for MCP servers), Agoragentic and Dirac (they have no way to add MCP servers)

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.

VariableDefault
CONECTOR_PORT8790Port to listen on.
CONECTOR_HOST127.0.0.1Interface to bind. Use 0.0.0.0 only behind a firewall or reverse proxy.
CONECTOR_PUBLIC_URLhttp://localhost: Address that people and agents use. Some OAuth providers require https://.
CONECTOR_ALLOWED_HOSTSExtra Host headers to accept, comma-separated (for example conector.lan:8790).
CONECTOR_DATA_DIR./dataUsers, tokens, encrypted credentials, the master key and the audit log. ~/.conector when installed from npm, /data in Docker.
CONECTOR_TRUST_PROXY1 behind a reverse proxy on the same machine or private network.
CONECTOR_HSTS1With an https:// public URL, send Strict-Transport-Security. Set 0 if the same host name also serves plain-HTTP services on other ports.
CONECTOR_SESSION_HOURS12Idle time before panel sessions expire. Sessions also end when the server restarts.
CONECTOR_ALLOW_PRIVATE_HTTP1 lets self-hosted apps on your local network use http:// (for example http://homeassistant.local:8123 or http://192.168.1.10:8123). See below.

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

Only the beginning is shown; read the rest in the repo

Ask PopNx