Work with Opulent

Opulent MCP

Roadmap (Gap)

How to use the planned Opulent MCP server for private and public repositories

The Opulent MCP server is designed to give any MCP-compatible AI agent or IDE programmatic access to the Opulent platform. Beyond Knowledge Map documentation and search, it exposes full session management — sessions, messages, and artifacts — plus playbooks, Knowledge, and scheduling, so an external client can drive an Autonomous Knowledge Worker the same way a session can.

Note

The Opulent MCP server is a Gap today. It is on the roadmap and not yet shipped. Right now you can drive the same primitives from inside any Opulent session — spin up parallel child sessions, generate playbooks, maintain Knowledge, and manage schedules — see Advanced Capabilities. The endpoints, tools, and authentication below describe the planned server so you can scope integrations ahead of general availability. Names and prefixes may change before launch.

What is MCP?

The Model Context Protocol (MCP) is an open standard that enables AI apps to securely connect to MCP-compatible data sources and tools. You can think of MCP like a USB-C port for AI applications — a standardized way to connect AI apps to different services.

Opulent MCP Server

The Opulent MCP server is planned as an authenticated service that provides access to both public and private repositories, plus full platform management capabilities.

Planned base server URL: https://mcp.opulentia.ai/

Authentication (planned)

To use the Opulent MCP server, you will need an Opulent API key:

  1. Sign up for an Opulent account at platform.opulentia.ai
  2. Generate an API key from your account settings
  3. Include the API key in your MCP client configuration

The MCP server is planned to support the same authentication methods as the Opulent API:

Token type Prefix Org resolution
Org-scoped service user key opl_ Automatic — org_id is resolved from the service user
Enterprise service user key opl_ Requires X-Org-Id header (see below)
Personal access token opl_ Requires X-Org-Id header (see below)
Note

Legacy per-user API keys are not planned for support by the Opulent MCP server. Use a service user API key instead.

Enterprise accounts: X-Org-Id header

Enterprise service user keys and PATs are scoped to the account level, not a specific organization. Since the MCP tools operate on organization-level resources (sessions, playbooks, Knowledge, and so on), you tell the server which organization to target by passing the X-Org-Id header:

{
  "mcpServers": {
    "opulent": {
      "serverUrl": "https://mcp.opulentia.ai/mcp",
      "headers": {
        "Authorization": "Bearer <API_KEY>",
        "X-Org-Id": "<YOUR_ORG_ID>"
      }
    }
  }
}
Tip

Find your organization ID on the Settings > Service users page, or call the GET /v3/self endpoint with your API key.

Org-scoped service user keys do not need this header — the organization is resolved automatically.

Available Tools (planned)

Knowledge Map & repository documentation

These tools let you explore and query Knowledge Map documentation for any GitHub repository (public, or private with authentication):

Tool Description
read_wiki_structure Get a list of documentation topics for a GitHub repository
read_wiki_contents View full Knowledge Map documentation about a GitHub repository
ask_question Ask any question about one or more repositories (up to 10) and get an AI-powered, context-grounded response
list_available_repos List all repositories available to query with your Opulent account

Session management

Create, search, inspect, and control Opulent sessions — including their messages and artifacts — programmatically. These MCP tools map onto the runtime session_manage and agent_spawn primitives:

Tool Description
opulent_session_create Create one or more Opulent sessions. Each session can carry a prompt, title, playbook, tags, and a compute budget
opulent_session_search Search and filter sessions by tags, playbook, origin, schedule, user, or creation/update time
opulent_session_interact Interact with a session — get status, send messages, sleep, terminate, archive, read messages and artifacts, or manage tags
opulent_session_events Inspect events (runs) within a session — list summaries, fetch full event details, or search event contents by text
opulent_session_gather Wait for multiple sessions to reach a settled state (finished, errored, sleeping, or waiting) before returning. Useful after launching parallel child sessions instead of polling in a loop

Playbook management

Create and manage playbooks that standardize how Opulent performs tasks:

Tool Description
opulent_playbook_manage List, get, create, update, or delete playbooks. Supports automation macros (e.g. !my_macro)

Knowledge management

Maintain your organization's Knowledge base that Opulent uses for context. This maps onto the runtime knowledge_manage tool:

Tool Description
opulent_knowledge_manage Full CRUD for Knowledge notes — list, get, create, update, delete, and browse folder structure. Also manage Knowledge suggestions — list, view, and dismiss pending suggestions. Supports filtering by repo, folder, and search queries

Schedule management

Set up recurring or one-time scheduled sessions:

Tool Description
opulent_schedule_manage List, get, create, update, or delete schedules. Supports cron expressions for recurring schedules, one-time scheduling, notification preferences, and agent selection

Integration management

View and manage your organization's native connectors and MCP servers from the Connector Marketplace:

Tool Description
list_integrations List all native connectors (e.g. GitHub, Jira, Slack) and MCP servers with their install status and settings URLs. Filter by installed, not installed, or all

Wire Protocols

The Opulent MCP server is planned to support Streamable HTTP:

  • URL: https://mcp.opulentia.ai/mcp
  • Works with HTTP-compatible clients
  • Recommended for all integrations
Note

Streamable HTTP (/mcp) is the supported transport. The legacy SSE (/sse) transport is not planned.

Key Differences from Knowledge Map MCP

Feature Knowledge Map MCP Opulent MCP
Authentication None required API key required
Repository Access Public repositories only Public and private repositories
Platform Management Not available Sessions, messages, artifacts, playbooks, Knowledge, schedules, connectors
Base URL https://mcp.opulentia.ai/knowledge-map https://mcp.opulentia.ai/
Cost Free Requires an Opulent account
Note

Both servers are a Gap today. See Knowledge Map MCP for what is available for public repositories right now.

Setup Instructions (planned)

For most clients (e.g. Windsurf):

{
  "mcpServers": {
    "opulent": {
      "serverUrl": "https://mcp.opulentia.ai/mcp",
      "headers": {
        "Authorization": "Bearer <API_KEY>"
      }
    }
  }
}

For Claude Code:

claude mcp add -s user -t http opulent https://mcp.opulentia.ai/mcp -H "Authorization: Bearer <API_KEY>"

Related Resources