Skip to main content
Glama
awe7893625

Local Workspace MCP

by awe7893625
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Local Workspace MCP

No user-submitted related servers found.

    Related Servers

    • Codex Local Ops

      hattimon
      A
      license
      D
      quality
      B
      maintenance
      Enables controlled local developer operations including file and process management, shell execution, SSH, WSL, Docker, Git, browser and desktop automation, media processing, and asynchronous jobs through MCP.
      146
      MIT

    • VBridge

      sirouk
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables authorized remote MCP clients to securely reach local Mac or Windows tools over OAuth, including shell commands, file read/write, background jobs, screenshots, UI control, and clipboard access. It can also expose configured Desktop MCP servers and optional Claude Code task delegation.
      MIT

    • ownerops-desktop-mcp

      sionchu
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables secure, self-hosted desktop automation through MCP with scoped filesystem access and a restricted, allowlisted shell.
      -

    • GoreeCloud Remote MCP

      GoreeCloud
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables self-hosted remote access to a user-controlled device's approved filesystem roots, allowing clients to list directories, read and search files, inspect metadata, ping the agent, and list devices through an MCP tunnel.
      AGPL 3.0
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    B3.4/5.0

    Scored across 11 tools

    Disambiguation4/5

    Each tool targets a distinct resource/action: identity, device listing/pinging, device tool discovery/execution, agent shutdown, local file listing/reading, workflow guidance, and artifact listing/path. Minor potential confusion among list-style tools and between local vs remote file operations is mostly resolved by descriptions.

    Naming Consistency4/5

    Mostly consistent snake_case with verb_noun patterns such as list_*, get_*, read_text, call_device_tool, and shutdown_device_agent. current_user_info is a noun phrase rather than get_current_user_info, a minor deviation.

    Tool Count5/5

    11 tools is well-scoped for a local workspace/device bridge: enough for device lifecycle, file access, and artifacts without excessive surface. No obvious redundant or bloat tools.

    Completeness3/5

    The set covers reading/listing local files and artifacts plus remote device discovery/execution, but lacks local write/create/update/delete operations and artifact creation/upload/download. These are notable gaps for a workspace server, though remote call_device_tool offers some execution coverage.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources