project_assign_team · Loftlancer Docs

MCP tool: project_assign_team
Canonical action: project.assign_team
Description: Assign team to project
OAuth scopes: mcp:toolsprojects:read
Org roles: owner, manager
Project grant: May require grant

Input (JSON)

Validated with Zod in @loftlancer/api/mcp. Organization context uses organizationId or organizationSlug (MCP tokens do not carry an active-org cookie).

{
  "$ref": "#/definitions/project_assign_team",
  "definitions": {
    "project_assign_team": {
      "type": "object",
      "properties": {
        "organizationId": {
          "type": "string",
          "minLength": 1
        },
        "organizationSlug": {
          "type": "string",
          "minLength": 1
        },
        "projectId": {
          "type": "string",
          "format": "uuid"
        },
        "teamId": {
          "type": "string",
          "minLength": 1
        }
      },
      "required": [
        "projectId",
        "teamId"
      ],
      "additionalProperties": false
    }
  },
  "$schema": "http://json-schema.org/draft-07/schema#"
}

Example request

{
  "name": "project_assign_team",
  "arguments": {}
}

Output

The MCP server returns a single text content block whose body is pretty-printed JSON from the underlying studio tRPC caller (runMcpTool in @loftlancer/api/mcp). Errors surface as tool errors (for example insufficient_scope, organization_required, or validation messages).