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

​
Available Tools

set_project

Set the default project context

get_current_project

Get current project context

list_projects

List available projects

Prompts

Server prompts for context guidance

​
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. 
// 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("list_components", { type: "layout" });

​
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