# Layers Growth (retired) (/docs/growth)



Layers Growth, the hosted MCP server at `growth.layers.com`, was retired on
2026-08-30. The service, its database, and its OAuth authorization server are
gone. `gi_` keys and `gat_` tokens are revoked, no `growth_`-prefixed tool
exists anywhere, and the hostname serves no MCP protocol. It now serves the
landing site for the converged server; the endpoint itself is
`https://mcp.layers.com/mcp`.

The [converged Layers Growth MCP](/docs/mcp) replaces it. It is one server, and moving
to it is one paste into the coding agent working in your repository:

```text
Set up Layers Growth for me so you can plan, render and deliver content for this product from here.
1. Install the CLI: run `npm install -g @layers/cli`.
2. Set it up: run `layers setup` from this repository. It opens my browser once for sign-in and waits for me; it writes the `.mcp.json` entry and the Layers skill into the repo and stores the session in my OS credential store, so nothing secret lands in the repo.
3. Read the skill at `.agents/skills/layers/SKILL.md`, then tell me what to post first.
Let me know when it is ready.
```

Paste that into Claude Code, Codex, Cursor, or any coding agent working in your
repository: the agent runs both commands, and the browser sign-in is the only
step that needs a person.

`layers setup` signs you in, binds the repository to the Layers Growth MCP, and removes
a `growth` entry an older setup wrote when that entry is exactly the one Layers
owned. The credential stays in the operating system keyring.

Manual setup, if you would rather run the commands in a shell:
`npm install -g @layers/cli`, then `layers setup`.

The product contract for the converged server, including what happened to each
of the 26 growth tools, is `docs/specs/layers-mcp-product.md` in the Layers
repository. Section 15.2 names every tool and says where its outcome went. The credit prices
this section used to publish are superseded by section 13.3 of that spec.
