> ## Documentation Index
> Fetch the complete documentation index at: https://docs.metabind.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Context Overview

> Set and manage project context for MCP operations

Context management tools set the project context for all subsequent operations, reducing the need to specify project IDs repeatedly.

## Available Tools

<CardGroup cols={2}>
  <Card title="set_project" icon="folder-open" href="/mcp/context/set-project">
    Set the default project context
  </Card>

  <Card title="get_current_project" icon="circle-info" href="/mcp/context/get-current-project">
    Get current project context
  </Card>

  <Card title="list_projects" icon="list" href="/mcp/context/list-projects">
    List available projects
  </Card>

  <Card title="Prompts" icon="message" href="/mcp/context/prompts">
    Server prompts for context guidance
  </Card>
</CardGroup>

## How Context Works

All MCP tools accept an optional `projectId` parameter. If not provided, tools use the session's default project set via `set_project`.

```javascript theme={null}
// Set project context once
await mcp.call("set_project", { projectId: "proj_123" });

// Subsequent calls use the default project automatically
await mcp.call("search_content", { query: "tutorials" });
await mcp.call("search_assets", { type: "image/*" });
```

## Context Persistence

* Context persists within a session
* Context requires re-establishment on reconnection
* Override the default by passing `projectId` explicitly to any tool

## Implementation Behavior

The MCP server manages context based on these rules:

1. **Single Project Access**: If the user has access to only one project, it's automatically set as the default
2. **Multiple Projects**: The `project_context` prompt displays available projects, requiring explicit selection
3. **Error Guidance**: When tools are called without proper context, error messages reference the prompt guidance