# JoinLayer

Wires your agent to the hosted JoinLayer gateway so it can read workspaces, connections and pipelines after a browser OAuth sign-in.

- MCP server · `type=mcp` · Claude Code, Codex, Cursor, GitHub Copilot, Windsurf (Devin Desktop), Cline, Zed, Gemini CLI
- Author: joinlayer
- License: Apache-2.0 · policy=link-only · description only; the file stays with the author
- Source: https://github.com/joinlayer/agent-toolkit
- Updated: 2026-10-19
- HTML: https://affpapa.org/en/nevibecode/mcp/joinlayer

## What it does

JoinLayer ships as a remote MCP server at `https://mcp.joinlayer.app/mcp`, plus the `joinlayer-pipelines` skill, plugin metadata and starter prompts. The server is listed in the official MCP Registry as `app.joinlayer/mcp`.

Sign-in runs through browser OAuth Authorization Code with PKCE. Do not mint or paste a bearer token by hand; connection credentials belong in JoinLayer browser setup sessions and never in tool arguments. Tokens are short-lived and audience-bound.

You need an MCP client that can do OAuth. The skill installs on its own, but it carries no credentials and does not replace the MCP connection — point your client at the same hosted endpoint first. The repo includes a gateway snapshot for security review, though it is not a self-hosted distribution: it leans on a private control-plane contract that is not published.

## Requirements
- Remote server: `https://mcp.joinlayer.app/mcp`

## Install

### Claude Code (native platform)

**Platform CLI: remote server**
```bash
claude mcp add --transport http mcp https://mcp.joinlayer.app/mcp
```

### Codex

**Platform CLI: remote server**
```bash
codex mcp add joinlayer --url https://mcp.joinlayer.app/mcp
```

### Cursor

**Config file**
File `.cursor/mcp.json`:
```json
{
    "mcpServers": {
        "joinlayer": {
            "url": "https://mcp.joinlayer.app/mcp"
        }
    }
}
```

### GitHub Copilot

**Config file**
File `.vscode/mcp.json`:
```json
{
    "servers": {
        "joinlayer": {
            "type": "http",
            "url": "https://mcp.joinlayer.app/mcp"
        }
    }
}
```

### Gemini CLI

**Platform CLI: remote server**
```bash
gemini mcp add -t http joinlayer https://mcp.joinlayer.app/mcp
```

## When to use it
- see which pipelines already exist in a workspace
- check granted OAuth scopes and capacity
- review source connections without editing configs
- plan a replication or realtime backfill run
- trace why a pipeline stalled and find a recovery point

## Example prompts
- Use $joinlayer-pipelines. Inspect my workspace, scopes, capacity, connections and pipelines. Change nothing.
- List the pipelines that are running now and explain what each one does.
- Show my source connections and their status, read-only.

## Similar
- [turbo-pipelines](https://affpapa.org/en/nevibecode/skills/turbo-pipelines.md) — skill · 3600 installs
- [secrets](https://affpapa.org/en/nevibecode/skills/secrets.md) — skill · 3600 installs
- [Elasticsearch](https://affpapa.org/en/nevibecode/mcp/elasticsearch.md) — MCP server · ★ 8
- [data-feeds](https://affpapa.org/en/nevibecode/skills/brightdata-data-feeds.md) — skill · 415 installs
- [data-engineer](https://affpapa.org/en/nevibecode/agents/voltagent-community-data-engineer.md) — subagent · 3194 installs
- [parallel-findall](https://affpapa.org/en/nevibecode/skills/parallel-findall.md) — skill · 12300 installs

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md