Catalog npm
PACKAGE EXPLORERView in registry

1server-mcp-engine

npm

One MCP server to run them all. Install MCP servers from the 1Server marketplace and access all tools through a single connection.

1serveraggregatorai-toolshubmcpmcp-servermodel-context-protocoloneserver
Versions collected8
Direct dependencies16From release 1.4.1
Last observed20 Oct, 18:37 UTC

README

Current package documentation

1server-mcp-engine

One MCP server to run them all.

Stop juggling dozens of MCP server configs. Browse the 1Server marketplace, install the servers you need, and connect your MCP client once. The engine handles everything else — spawning processes, managing connections, OAuth flows, tool aggregation, health monitoring, and hot-reload.

Without mcp-engine:

{
  "mcpServers": {
    "memory": { "command": "npx", "args": ["-y", "@modelcontextprotocol/server-memory"] },
    "github": { "command": "npx", "args": ["-y", "@modelcontextprotocol/server-github"], "env": { "GITHUB_TOKEN": "..." } },
    "filesystem": { "command": "npx", "args": ["-y", "@modelcontextprotocol/server-filesystem", "/path"] },
    "slack": { "command": "npx", "args": ["-y", "@modelcontextprotocol/server-slack"], "env": { "SLACK_TOKEN": "..." } },
    "brave": { "command": "npx", "args": ["-y", "@modelcontextprotocol/server-brave-search"], "env": { "BRAVE_API_KEY": "..." } }
  }
}

With mcp-engine:

{
  "mcpServers": {
    "1server": {
      "command": "npx",
      "args": ["-y", "1server-mcp-engine"],
      "env": {
        "ONESERVER_API_KEY": "your-api-key"
      }
    }
  }
}

One config. All your servers. Managed from a web dashboard.

Features

Hot-Reload — No More Restarts

Install, uninstall, or toggle servers from the marketplace and changes take effect immediately. No MCP client restart needed. The engine detects config changes, spins up new servers, tears down removed ones, and reconnects modified ones — all while your AI assistant stays connected.

Progressive Server Loading

The engine starts accepting client connections instantly. Servers connect in the background with parallel loading (up to 3 at a time). Fast servers are available in seconds while slower ones finish connecting. Your AI assistant doesn't sit waiting for every server to be ready before it can respond.

Health Monitoring & Auto-Recovery

Every server is continuously monitored. If a server crashes, the engine automatically reconnects it with exponential backoff (up to 10 attempts). Use the built-in 1server_health tool to see real-time status of every server — healthy, degraded, reconnecting, or errored — along with uptime, failure counts, and tool counts.

Server Restart on Demand

If a server is misbehaving, use the 1server_restart_server tool to restart it by name. The engine disconnects and reconnects the server, refreshing all its tools and capabilities. Your AI assistant can even detect unhealthy servers from the health report and suggest a restart.

In-Client Server Management

Manage your entire server inventory without leaving your AI conversation:

ToolWhat it does
1server_list_serversSee all your installed servers
1server_search_serversBrowse the marketplace
1server_install_serverInstall or update a server
1server_uninstall_serverPermanently remove a server
1server_toggle_serverEnable/disable without losing config
1server_restart_serverRestart an unhealthy server
1server_healthCheck status of all servers
1server_list_secretsView your saved credentials

Encrypted Secrets

API keys and tokens are stored in an AES-256 encrypted vault on the 1Server backend. Reference secrets by ID when installing servers — values are never exposed in config files or logs.

Setup

  1. Create an account at 1server.ai
  2. Install MCP servers from the marketplace
  3. Generate an API key from your dashboard
  4. Add this to your MCP client config (Claude Desktop, VS Code, Cursor):
{
  "mcpServers": {
    "1server": {
      "command": "npx",
      "args": ["-y", "1server-mcp-engine"],
      "env": {
        "ONESERVER_API_KEY": "your-api-key"
      }
    }
  }
}

The engine fetches your installed servers and starts them automatically.

How it works

MCP Client (Claude, VS Code, Cursor)
    |
    |  stdio
    v
mcp-engine
    |--- stdio ---> memory server
    |--- stdio ---> filesystem server
    |--- http  ---> github (OAuth)
    |--- stdio ---> any MCP server
    |
    All tools namespaced and aggregated
  • Stdio servers are spawned as local processes
  • HTTP servers connect remotely with automatic OAuth
  • Tools are namespaced by server name to avoid conflicts
  • OAuth tokens persist across restarts at ~/.oneserver-mcp/auth/
  • Servers install/uninstall from the 1Server dashboard or directly from your AI assistant — no config files to edit
  • Servers auto-recover from crashes with exponential backoff
  • Config changes apply instantly — no client restart needed

Requirements

  • Node.js >= 18
  • 1Server account + API key

Built by 1Server AI

Downloads & popularity

Awaiting observations

No metric observations yet

Download counts and popularity will appear here as the collector receives them.

Versions 8

Collected releases
VersionPublishedDirect dependenciesOpen version
1.4.1Registry latest2 May 202616
1.4.015 Apr 202616
1.3.114 Apr 202616
1.3.013 Apr 202616
1.2.011 Apr 202616
1.1.011 Apr 202616
1.0.19 Apr 202616
1.0.09 Apr 202616

Package advisories

0
No matching advisories collected

This describes our collected data; it is not a security assessment.

Repository

PENDING
oneserverai/oneserver-mcp-engine

Shared repository data · GitHub

License detected in repository
Not collected

Metadata history

Meaningful changes
Current collected state Current

Observed since 20 Oct, 18:37 UTC

No superseded metadata states collected. Unchanged observations do not create new revisions.

Record identity

package:b12f883562b59eeba2f600f584e683533cbbe4601ab1ba7b8ac6ce49f31863a8