Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Operate secure JoinLayer data pipelines through delegated OAuth.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://mcp.joinlayer.app/mcpRun this in your terminal
claude mcp add --transport http joinlayer https://mcp.joinlayer.app/mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"joinlayer": {
"url": "https://mcp.joinlayer.app/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"joinlayer": {
"type": "http",
"url": "https://mcp.joinlayer.app/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
https://mcp.joinlayer.app/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified against the domain joinlayer.app (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (0.1.2) reached the registry 2 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Spec Driven Development, Remote Desktop Commander, AI Deprecations
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
AI model shutdown dates, replacements, change feed and webhook alerts for 8 providers.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Official agent integration for JoinLayer: a hosted MCP gateway, the joinlayer-pipelines skill, client plugin metadata, safe starter prompts, and public protocol tests.
The supported service is the JoinLayer-hosted endpoint:
https://mcp.joinlayer.app/mcp
It is published as app.joinlayer/mcp in the official MCP Registry. The operating skill is available from skills.sh, and this repository is the canonical source for the JoinLayer Codex and Claude Code marketplaces.
Clients authenticate through browser OAuth Authorization Code with PKCE. Never create, paste, or configure a JoinLayer bearer token manually.
You do not need to read the full documentation first. Open START_HERE.md, connect JoinLayer, and copy the read-only inspection prompt. From there, choose a ready-to-run prompt for your goal.
skills/joinlayer-pipelines: agent operating guidance and task references;.codex-plugin/plugin.json, .claude-plugin/, and .mcp.json: installable Codex and Claude Code plugin metadata;prompts: safe starting points for common JoinLayer tasks;use-cases: complete customer outcomes with evidence and stop boundaries;mcp-gateway: a reviewable snapshot of the hosted MCP security boundary;server.json: MCP Registry metadata for the hosted remote server.The gateway source is published for transparency and compatibility review. It is not a self-hosted JoinLayer distribution: it depends on a private, authenticated JoinLayer control-plane contract that is not included here. JoinLayer production builds and deployment remain in a private release system, but the mcp-gateway/ tree used by a hosted release must match a tagged public snapshot exactly. The private release gate rejects gateway drift. Skills, prompts, and plugin packaging use their own versioned content checks rather than this byte-equality gate. A public contribution never deploys directly to JoinLayer infrastructure.
Install the JoinLayer plugin from its public repository marketplace:
codex plugin marketplace add joinlayer/agent-toolkit
codex plugin add joinlayer@joinlayer
The plugin bundles the operating skill and configures the hosted MCP companion. Complete browser OAuth when prompted. To configure only the MCP server instead:
codex mcp add joinlayer --url https://mcp.joinlayer.app/mcp
codex mcp login joinlayer --scopes workspace:read,usage:read,connections:read,pipelines:read
Then start a fresh session and ask:
Use $joinlayer-pipelines. Inspect my authenticated workspace, scopes,
capacity, connections, and pipelines. Do not change anything.
More copyable starting points are indexed in START_HERE.md. Complete workflows for replication, realtime backfill, scheduling, enrichment, capacity, approvals, and recovery are in use-cases/.
claude plugin marketplace add joinlayer/agent-toolkit
claude plugin install joinlayer@joinlayer --scope user claude mcp login joinlayer
Complete browser OAuth through claude mcp login joinlayer when that command is available, or through Authenticate in /mcp on earlier OAuth-capable releases. Do not add an Authorization header or client secret.
Agents supported by skills.sh can install only the operating skill:
npx skills add https://github.com/joinlayer/agent-toolkit --skill joinlayer-pipelines
The skill does not carry credentials and does not replace the MCP connection. Configure the same hosted endpoint through your client's OAuth-capable MCP settings, then use a prompt from START_HERE.md.
Report vulnerabilities privately as described in SECURITY.md.
python3.12 -m venv .venv
. .venv/bin/activate pip install --requirement mcp-gateway/requirements.lock PYTHONPATH=mcp-gateway python -m unittest mcp-gateway.tests.test_gateway python scripts/validate_public_snapshot.py
Build the review image with docker build .. That image is for reproducibility and review; it is not automatically promoted to JoinLayer production.
See SOURCE_SYNC.md for the exact public/private release invariant. Maintainers can use DISTRIBUTION.md for the verified catalog and marketplace publication contracts. OpenAI review material is recorded in OPENAI_SUBMISSION.md.
To compare this checkout with a private platform checkout before review:
python scripts/source_tree_digest.py --compare-root /path/to/private-platform
Apache-2.0. See LICENSE.
The code license does not grant rights to impersonate JoinLayer or imply endorsement. See TRADEMARKS.md.