MCP Uplink
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
MCP Uplink
General-purpose local MCP manager with a loopback aggregate MCP endpoint and optional WebSocket uplink.
Install and run
Requires Node.js 22 or newer.
Install the published CLI:
npm install -g @myriadcodelabs/mcp-uplink
mcp-uplinkOr run from source:
npm ci
npm run build
npm startOpen http://127.0.0.1:8787. Add a STDIO command or a Streamable HTTP MCP endpoint, then start it. HTTP MCPs can include custom request headers such as Authorization or X-API-Key for authenticated endpoints. MCP clients connect to http://127.0.0.1:8787/mcp. The UI and endpoint bind only to 127.0.0.1; the local endpoint has no authentication. /mcp accepts loopback and Chrome/Firefox extension origins. Ordinary website origins remain blocked because they could otherwise invoke local tools.
To install as a local CLI package, run npm pack here, then npm install -g ./myriadcodelabs-mcp-uplink-1.0.0.tgz and mcp-uplink.
Configuration, including MCP environment variables, HTTP headers, and the uplink credential, is stored in ~/.config/mcp-uplink/config.json with owner-only permissions. Set MCP_UPLINK_CONFIG to use another path and MCP_UPLINK_PORT to change the loopback port. Legacy MYRIAD_ADAPTER_CONFIG and MYRIAD_ADAPTER_PORT values remain supported for compatibility. Keep your user account and config file protected.
Remote uplink is optional. On the Remote page, enter a WebSocket URL and credential. The current registry backend accepts an Authorization: Bearer header, sends call frames, and receives register, result, and error frames. Other remotes must support this protocol. Tool names are preserved when unique; duplicate names are prefixed with the source ID.
MCP Uplink manages processes and transport only. It has no local permissions, filtering, or quotas.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
MCP federation gateway: route, govern and observe agent tools across clouds and MCP servers.
Streamable HTTP MCP gateway for NV oOS fleets — one API key, namespaced tools, quotas and policy.
Remote MCP server exposing SMI Aware tools, resources, and skills over Streamable HTTP.
Toolstile is a managed MCP gateway that connects remote MCP servers behind one endpoint, with per-agent permissions, shared accounts and activity logs. Connect at https://mcp.toolstile.com/mcp over Streamable HTTP with OAuth; sign in at https://toolstile.com, select a workspace and connect your upstream servers. Available tools, resources and prompts depend on that workspace and the agent's granted access.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceEnables connecting multiple remote HTTP MCP servers through a single local stdio endpoint, handling OAuth authentication, token refresh, and namespace-scoped tools.16 npmMIT
- AlicenseNot gradedqualityBmaintenanceAggregates multiple MCP sub-servers into a single unified entry point, supporting stdio and Streamable HTTP protocols, with a web-based management interface for configuration, routing, and tool management.17 npm1MIT
- AlicenseNot gradedqualityAmaintenanceEnables connecting to and managing multiple backend MCP servers (Stdio, SSE, Streamable HTTP), aggregating their tools/resources, and exposing them through unified SSE, Streamable HTTP, or Stdio endpoints with routing, authentication, and optional web-based administration.120 npmMIT
- AlicenseNot gradedqualityAmaintenanceAggregates multiple backend MCP resource servers (Stdio, SSE, and Streamable HTTP) into one unified hub, exposing their combined tools and resources through single SSE, Streamable HTTP, or Stdio endpoints with routing, authentication, and optional web-based management.120 npmMIT