Management MCP server

Layer exposes a second, separate MCP server for workspace administration. Where the creative server generates assets, the management server handles the operational side of a workspace: projects, groups, members, and Creative-Units usage.

It runs at a different endpoint (https://mcp.app.layer.ai/mcp-management) and is connected as its own server in your client.

SetupConnect the management server to your client.

Creative serverThe generation server (images, 3D, video, audio).

Why a separate server?

MCP agents choose tools better when the toolset in front of them is small and focused. Every tool loaded into a conversation consumes context and adds another option the model has to reason about — and past a certain point, too many tools pollute the context: the agent gets slower, picks the wrong tool more often, and loses the thread of what the user actually asked for.

Workspace administration and creative generation are genuinely different jobs. Someone generating game assets rarely needs to suspend a member or set a group’s Creative-Units cap in the same breath — and an automation that manages seats has no use for forge parameters. Bundling ~40 tools into one server would make both jobs worse.

So we split them by concern. Each agent connects only to the surface it needs:

• Creators & pipelines connect to the creative server — generation, models, workflows, files.
• Admins & provisioning automation connect to the management server — the tools on this page.

You can connect to both at once if you need to; they’re independent servers with independent tool lists, so neither dilutes the other.

Note

Both servers use the same Layer account and OAuth flow. Every management operation runs as your Layer user and is subject to your workspace role — the server doesn’t grant new permissions.

What it manages

Projects

Create and manage projects and their members within a workspace.

• list_projectsList projects in a workspace with their name, status, and linked object count.
• get_projectGet details for a single project in a workspace.
• create_projectCreate a new project in a workspace.
• update_projectUpdate a project's name, description, instructions, or archive status.
• delete_projectDelete a project (soft-delete: it is removed from listings and can't be used).
• add_project_membersAdd existing workspace members to a project by email.
• remove_project_memberRemove a member from a project by email.

Groups

Manage workspace groups — the role they grant, their members, and their Creative-Units caps.

• list_groupsList a workspace's groups with their name and granted role.
• create_groupCreate a workspace group, optionally granting its members a role.
• update_group_roleSet or clear the workspace role a group grants its members.
• delete_groupDelete a workspace group, revoking its role and cap from members.
• list_group_membersList a group's members with their email and status.
• add_group_memberAdd a workspace member to a group by email (they must already be a workspace member).
• remove_group_memberRemove a member from a group by email.
• set_group_usage_limitSet a group's Creative-Units cap for a period.
• remove_group_usage_limitRemove a group's Creative-Units cap.

Members

Invite, list, and manage the access of workspace members.

• list_workspace_membersList the members of a workspace with their email, role, and status.
• invite_memberInvite a user to a workspace by email, creating the Layer user if needed.
• suspend_memberSuspend a workspace member, revoking their access without deleting them.
• reactivate_memberReactivate a suspended workspace member, restoring their access.

Usage

Inspect a workspace’s Creative-Units balance and consumption.

• get_workspace_usageReport a workspace's Creative Units balance and recent consumption.