Skip to Content
IntegrationMCP reference

MCP reference

The Nebbos MCP surface exposes 85 tools organised into 14 capability categories. The MCP classifier assigns each tool call to the appropriate data tier on the operator’s host. The substrate evaluates every request against operator identity, tier, and policy before executing.

Tool discovery

Integrations should pin against list_available_tools rather than a hard-coded roster. The MCP surface is self-describing: the discovery tool returns each current tool with its input schema, output shape, and required operator tier. Additions to the tool set become available to an integration on its next discovery pass.

Capability categories

CategoryTool countTier requirementPurpose
Pearl query2GuestNatural-language queries against a department-scoped Pearl
Signals and risk2Host (for acknowledgement)Cross-domain risk signals produced by the Orchestrator; acknowledgement requires the human-token attribution tuple
Project and task operations21Guest (read), Host (write)Read and write the operational-work tracker. Writes require justification and verification fields.
Departments and workspace4Guest (read), Architect (create)The organisational structure within which Pearls operate
Audit chain3HostRead the hash-chained audit log; walk a chain segment and receive a signed verification receipt
Context and knowledge6GuestKnowledge graph, memory registers, playbook catalog, predictions
Discovery2GuestSelf-describing entry points: the live tool roster with tier requirements, and the caller's own identity and connection
Billing5Guest (read), Host (write)Read invoice previews, family balances, client invoices, usage snapshots, and AR aging reports
GitHub operations28Guest (read), Host (write)Pull requests, workflow runs, branches, commits, issues, and code search against the connected GitHub account
Google Workspace3GuestWorkspace users, groups, and organisational units from the DWD-owning tenant
Tenant tools registry4HostRegister, update, deactivate, and list tenant-scoped MCP tools alongside the first-party surface
Tenant admin3Host (for admin ops)Provision new tenants and super-admin invitations; register OAuth redirect URIs with the Nebbos AuthKit environment; link named configuration capabilities between services
Deployment status1GuestCheck whether a given commit is live on a hosted service
Workflows1GuestTrigger structured operational-review workflows across all departments

Counts are generated from the platform’s live tool registry and refresh hourly.

Tools by category

  • Pearl query: query_pearl, describe_pearl
  • Signals and risk: get_active_signals, acknowledge_signal
  • Project and task operations: list_projects, get_project, create_project, update_project, assign_project_layers, list_tasks, get_task, create_task, update_task, update_task_status, update_task_department, update_task_project, update_task_recalibration, update_tasks_bulk, assign_task, add_comment, get_task_activity, get_task_assignees, get_task_comments, list_user_activity, list_registered_tags
  • Departments and workspace: list_departments, create_department, list_projects_departments, compare_departments
  • Audit chain: audit_event_list, audit_event_get, audit_event_hash_chain_verify
  • Context and knowledge: get_context, get_knowledge_graph, analyze_gaps, search_insights, get_predictions, search_playbook_catalog
  • Discovery: list_available_tools, whoami
  • Billing: get_invoice_preview, get_family_balance, list_client_invoices, get_billing_usage, get_ar_aging
  • GitHub operations: gh_pr_view, gh_pr_list, gh_pr_check_runs, gh_pr_files, gh_workflow_run_logs, gh_repo_list, gh_repo_tree, gh_repo_get_file, gh_commit_list, gh_commit_view, gh_branch_list, gh_compare, gh_issue_list, gh_issue_view, gh_code_search, gh_pr_create, gh_pr_comment, gh_pr_merge, gh_pr_edit, gh_pr_close, gh_pr_reopen, gh_pr_ready, gh_workflow_rerun, gh_pr_update_branch, gh_issue_create, gh_issue_comment, gh_issue_edit, gh_branch_create
  • Google Workspace: list_workspace_users, list_workspace_groups, list_workspace_org_units
  • Tenant tools registry: register_tenant_tool, unregister_tenant_tool, update_tenant_tool_visibility, list_tenant_tools
  • Tenant admin: invite_tenant_super_admin, workos_add_redirect_uri, capability_link
  • Deployment status: railway_deploy_status_for_commit
  • Workflows: run_ops_review

Authentication requirements

Every MCP request carries a Bearer token. Every write additionally carries a delegation token identifying the human on whose authority the call is made. Bearer tokens expire fifteen minutes after issuance.

See Authentication & tiers for the mapping of Guest, Host, and Architect tiers to integration identity requirements.

Human-in-the-loop authorisation

Tools that accept a human_token input require a signed approval from the verified human delegator on the same request. The substrate refuses the call if the token cannot be verified, has expired, or if the delegator’s scope does not cover the operation. Delegation tokens are issued through the human-approval flow and passed into subsequent tool calls.

Audit-chain recording

Every MCP invocation produces one entry in the hash-chained audit log, with the tool name, the redacted parameters, the outcome, the scopes used, the acting identity and its delegator, the time and the chain hash. The tool’s response is not stored, and inputs and outputs are not hashed separately. See The audit chain.