Get Project Details via MCP: Metadata, Members, and Settings

Developer reference for the get_project MCP tool. Learn how to retrieve complete details of a specific project including metadata, members, settings, and statistics. Includes example tool calls, natural language prompts, edge cases, and troubleshooting.

Tool Overview

Purpose

The get_project tool retrieves complete details of a specific project by its ID. Use this tool when you need full context about a project including members, settings, task counts, and metadata before generating reports or planning workflows.

Read-only operation: This tool only reads data - it never modifies projects.

Input Parameters

The tool requires a project ID to retrieve the project details.

Output Format

The tool returns a complete project object with all available fields:

{
  "id": 456,
  "name": "Q1 Product Launch",
  "description": "Launch new product features for Q1 2026",
  "created_at": "2026-01-01T10:00:00Z",
  "updated_at": "2026-03-10T14:30:00Z",
  "created_by_id": 99,
  "members": [
    {
      "id": 101,
      "name": "John Doe",
      "email": "[email protected]",
      "role": "owner"
    }
  ],
  "settings": {
    "default_board_id": 789,
    "notifications_enabled": true
  },
  "task_count": 42,
  "board_count": 3,
  "member_count": 5
}

Response Fields

• id: Unique project identifier
• name: Project name
• description: Full project description (may be null)
• created_at: Timestamp when project was created
• updated_at: Timestamp when project was last updated
• created_by_id: ID of the user who created the project
• members: Array of member objects with id, name, email, and role
• settings: Project settings object (default_board_id, notifications_enabled, etc.)
• task_count: Total number of tasks in the project
• board_count: Number of boards in the project
• member_count: Number of members in the project

Example Tool Calls

Example 1: Get Project by ID

Tool Call (JSON):

{
  "tool": "get_project",
  "arguments": {
    "project_id": 456
  }
}

Returns: Complete project object with all fields

Natural Language Prompt Examples

Claude Desktop / General AI

User Prompt:

"Show me details for the Q1 Product Launch project"

AI Behavior:

1. AI calls list_projects with search: "Q1 Product Launch"
2. AI finds project ID (456)
3. AI calls get_project with project_id: 456
4. AI receives complete project object
5. AI formats and presents project details to user

Checking Project Members

User Prompt:

"Who is on the Q1 launch project?"

AI Behavior:

1. AI finds project using list_projects
2. AI calls get_project to get members list
3. AI extracts and presents member names and roles

Preparing Status Reports

User Prompt:

"Give me an overview of the Q1 project for a status report"

AI Behavior:

1. AI calls get_project to get project metadata
2. AI uses project details (name, description, task_count) to build report context
3. AI may also call list_tasks filtered by project_id for task details
4. AI generates status report using project context

Common Use Cases

• Project Kickoff - Review project details and members before starting work
• Status Reports - Get project metadata for generating status updates
• Client Progress Reports - Include project details and member information in reports
• Find Project First - Use list_projects to find ID before calling get_project

Edge Cases

Project Not Found (404)

Situation: Project ID doesn't exist or was deleted

Response:

{
  "error": "not_found",
  "message": "Project with ID 456 not found"
}

Handling: Verify the project ID is correct, or check if the project was deleted

Permission Denied (403)

Situation: Project exists but you don't have access

Response:

{
  "error": "forbidden",
  "message": "You don't have permission to access this project"
}

Handling: Check if you're in the correct workspace or if the project is private

Read 403 troubleshooting guide →

Invalid Project ID

Situation: Project ID is not a valid integer

Response:

{
  "error": "validation_error",
  "message": "Invalid project_id format",
  "field": "project_id"
}

Handling: Ensure project_id is a valid integer

Troubleshooting

Invalid Project ID

Symptom: 400 validation error or 404 not found

Causes:

• Project ID is not a number
• Project ID doesn't exist
• Project was deleted

Fix:

• Verify project ID is a valid integer
• Use list_projects to find the correct project ID
• Check if project still exists in Corcava

Access Denied (403)

Symptom: 403 Forbidden error

Causes:

• Project belongs to a different workspace
• Project is private and you're not a member
• API key doesn't have access to the workspace

Fix:

• Verify you're accessing the correct workspace
• Check project permissions in Corcava
• Verify API key has access to the workspace

Read 403 troubleshooting guide →

Best Practices

Using get_project Effectively

• ✅ Always call list_projects first to find project ID if you only know the name
• ✅ Use project details to understand context before generating reports
• ✅ Check member list to understand project team composition
• ✅ Use task_count and board_count for project health metrics
• ✅ Review project settings to understand default configurations

Related Tools

Often used together with:

• list_projects - Find project IDs before calling get_project
• list_tasks - Get tasks within a project using project_id
• list_boards - Find boards within a project