Otherlay

com.otherlayPublished by otherlay.comOfficial publisherv1.0.0Updated Oct 24, 2026

Secure access to a dedicated Otherlay Mac for files, terminals, Git, builds and UI inspection.

VerifiedStreamable HTTPWeb executableCloud & InfrastructureDeveloper Tools

Overview

AI-generated overview

Remote MCP endpoint giving an assistant secure access to a dedicated Otherlay Mac for files, terminals, Git, builds and UI inspection.

What you can do
  • Work with files on a dedicated Otherlay Mac
  • Run terminal commands on that machine
  • Handle Git operations and builds
  • Inspect the user interface of running apps
  • No individual tools are listed, so exact capabilities come from the Otherlay console.
When to use it
Useful when an assistant needs to act on a real macOS environment rather than the local machine: editing project files, running builds or Git commands, and checking app UI on a dedicated remote Mac.
Requirements
A remote endpoint at mcp.otherlay.com over streamable HTTP. OAuth authentication is required, plus an Authorization header carrying a Bearer token generated by Connect coding agent in the Otherlay customer console. An Otherlay account and a provisioned Mac are implied.
Before you install
The Authorization Bearer token is a secret granting access to the dedicated Mac; keep it out of logs and shared configs. Terminal, file and Git access means the assistant can change, build or delete things on that machine, so scope and review actions. Data on the Mac is handled by a third-party service.

Installation

In SourceWeft

  1. Open Otherlay in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.otherlay%2Fotherlay/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "otherlay": {
      "type": "http",
      "url": "https://mcp.otherlay.com/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.