Management MCP setup
The management server is a separate MCP server from the creative one — you add it as its own entry in your client, pointing at:
https://mcp.app.layer.ai/mcp-managementIt uses the same Layer account and OAuth flow as the creative server, and the same transport (Streamable HTTP). If you’ve connected the creative server before, this is the identical process with a different URL and server name.
Connect your client
Section titled “Connect your client”Claude.ai / Claude Desktop
Section titled “Claude.ai / Claude Desktop”Add it as a custom connector: in Settings > Connectors, click + Add custom connector, name it Layer Management, enter https://mcp.app.layer.ai/mcp-management, and click Add. OAuth triggers on first use.
On Team / Enterprise, an Owner adds it org-wide via Organization settings > Connectors; members then authenticate individually.
Claude Code (CLI)
Section titled “Claude Code (CLI)”claude mcp add --transport http "Layer Management" https://mcp.app.layer.ai/mcp-managementRun /mcp, select Layer Management, and choose Authenticate.
Cursor
Section titled “Cursor”In Settings > Features > MCP, click + Add New MCP Server, choose Streamable HTTP, name it Layer Management, and use https://mcp.app.layer.ai/mcp-management.
VS Code
Section titled “VS Code”Add to .vscode/mcp.json:
{ "servers": { "Layer Management": { "type": "http", "url": "https://mcp.app.layer.ai/mcp-management" } }}Other clients
Section titled “Other clients”Every client covered on the creative Setup page works the same way — just substitute the management URL (https://mcp.app.layer.ai/mcp-management) and a distinct server name. For clients without OAuth, authenticate with a Personal Access Token the same way.
The generic mcp-remote bridge (any client that can launch a command):
{ "mcpServers": { "Layer Management": { "command": "npx", "args": ["-y", "mcp-remote", "https://mcp.app.layer.ai/mcp-management"] } }}