Skip to main content
Glama
PocketShell-io

PocketShell MCP

Official

PocketShell MCP

Remote MCP tools for PocketShell and DataOps. Assistant computers need no saved CLI login, SSH key or host pins. A persistent service holds that state and connects through the existing PocketShell gateway.

The server uses standard Streamable HTTP and MCP OAuth: discovery, dynamic client registration, authorization code with S256 PKCE, audience binding, short access tokens and rotating refresh tokens. It has no ChatGPT-specific transport or token exchange. The same endpoint can be connected by ChatGPT/dots, Claude, Grok Bot, Cursor, Codex and other OAuth-capable MCP clients.

Status: protocol tests and Inspector HTTPS tests pass. Production installation and actual ChatGPT/dots, Claude and Grok Bot account tests remain required. Protocol compatibility is not a claim that those account tests have passed.

Tools

Service

Tools

PocketShell

hosts, ls, start, send, capture, stop, status

DataOps

dataops_guide, dataops_read, dataops_write

PocketShell operations invoke the same psc runtime used by the terminal client. Account/device/gateway functions come from @pocketshell/tui-client/core. The public entry point lives in the upstream client package; it re-exports the existing implementations. The lower-level host contract remains in @pocketshell/core. The build pins both upstream source revisions. Generated bundles stay outside Git because upstream defaults can contain deployment details.

DataOps tools access the same portal API as dataops api. They preserve portal permissions, JSON bodies and query parameters. Auth/token-management endpoints and local filesystem access are excluded. Binary uploads/downloads use the portal.

Related MCP server: OpenXNet MCP Server

Development

Requires Node 24, npm, Git and OpenSSL for the HTTPS tests. SSH operations also require OpenSSH.

npm ci
npm test
node scripts/build-client.mjs

The build downloads pinned public client/core sources into a temporary directory, compiles the shared code, and removes the sources. To use an existing checkout, pass its path as the first argument.

Configure a service using the variables in configuration, then run npm start. Run PocketShell and DataOps as separate service users with separate state directories, storage keys and issuer URLs. Infrastructure belongs in the infrastructure repository; this repository does not create AWS resources.

See connection steps for ChatGPT/dots, Claude, Grok Bot, Cursor, Codex and Inspector. Security and limits describes credential storage, host trust and operating limits.

Related MCP Connectors

Related MCP Servers

  • A
    license
    Not graded
    quality
    A
    maintenance
    Exposes a Windows or Linux host terminal to remote MCP clients via Streamable HTTP, enabling command execution, tunnel management, and privileged operations with security features like OAuth and audit logging.
    19 npm
    2
    MIT
  • A
    license
    Not graded
    quality
    B
    maintenance
    Enables MCP clients to securely access authorized computers and VPSs for scoped file operations, Git operations, and administrator-defined quality gates through an outbound-polling gateway.
    1
    Apache 2.0
  • A
    license
    Not graded
    quality
    B
    maintenance
    Enables an agent to search approved MCP integrations and expose only the tools a given task needs, signing the user in once via browser-based OAuth and enforcing scopes, effects and budgets in code. It also acts as a single gateway connection so existing hosts can reach many servers with per-tenant isolation and audit events.
    MIT