Initializing Operalta...

MCP Setup

Connect Operalta to Claude Code, Cursor, Windsurf, or another MCP client

Connect Operalta to Claude Code, Cursor, or Windsurf.

01

Configure

  • -Add Operalta as an MCP server. Package: @operalta/cli.
  • -Auth via OPERALTA_API_KEY, or reuse your operalta login session.
  • -OPERALTA_COMPANY_ID pins a company in multi-company setups.
{
  "mcpServers": {
    "operalta": {
      "command": "npx",
      "args": ["@operalta/cli"],
      "env": { "OPERALTA_API_KEY": "op_..." }
    }
  }
}
02

Tool families

  • -Read: get_company_context, get_metrics, get_decisions, search_knowledge, get_structure.
  • -Artifacts: sync_artifact, get_artifact, archive_artifact.
  • -Office: generate_excel_workbook creates a local .xlsx file directly from MCP/CLI without calling the Operalta API.
  • -Innovation templates: generate_innovation_excel_template and operalta excel template create <template-id> produce ready workbooks for portfolio, scoring, experiments, roadmap, funding, partners, impact metrics, and venture BP.
  • -Agents: council, panel, research_panel, deep_research, orchestrate.
  • -Workflow: pipeline, room sync, data room.
  • -Financial planning: read company context and metrics, then create artifacts or room outputs that reference the same company-scoped source data as FounderFin.
03

Company context

  • -OPERALTA_COMPANY_ID pins MCP calls to one company when your key can access multiple workspaces.
  • -Financial tools are company-aware: a founder workspace, investor workspace, and portfolio workspace can expose different metrics, labels, and workflows.
  • -Use the same company context when moving between CLI, MCP, and REST API calls so forecasts, artifacts, and rooms stay attached to the intended workspace.
04

Spreadsheet automation boundary

  • -For local MCP/CLI work, use generate_excel_workbook, generate_innovation_excel_template, operalta excel create, or operalta excel template create to produce the workbook on disk. This path does not require OPERALTA_API_KEY and does not create a server-side generated export.
  • -Pick the template by company type and job: startup experiments/BP, fund or accelerator portfolio, corporate roadmap/capacity, public sector or nonprofit impact/funding, and partner ecosystem tracking.
  • -Template IDs include innovation_portfolio, opportunity_scorecard, experiment_tracker, roadmap_capacity, funding_plan, partner_ecosystem, impact_metrics, and venture_bp.
  • -Use the API sandbox run path only when the workbook must be generated server-side, promoted into Operalta storage, reviewed, or linked to Rooms from the web app.
  • -Keep OPERALTA_COMPANY_ID pinned when API-backed follow-up is needed so workbook assumptions, labels, room access, and generated exports stay tied to the intended company type.