Documentation
Back to CaptainMCP Overview

Setup & Installation

Learn how to install, configure, and securely connect CaptainMCP to your AI clients and Oracle EPM environments.

1. Installation Prerequisites

CaptainMCP runs locally on your machine or on a centralized server. Before installing, ensure you have the following:

  • Windows 10/11 (64-bit): CaptainMCP ships as a standalone executable — no Node.js or developer tools required.
  • Oracle EPM Connection: The URL endpoint for your Oracle EPM Planning or FCC environment.
  • AI Client: An MCP-compatible client such as Claude Desktop or Cursor.

2. Authentication Configuration

CaptainMCP supports Basic Authentication and OAuth 2.0. Credentials can be stored in the Windows Credential Manager vault (recommended, via the setup wizard) or in a local .env file next to the executable:

EPM_URL=https://epm-tenant.pbcs.us1.oraclecloud.com
EPM_USERNAME=admin@company.com
EPM_PASSWORD=your_secure_password
READ_ONLY_MODE=true
SERVICE_TYPE=planning  # planning | fcc | both

Note: Use a dedicated service account rather than a personal admin account for production workflows. Start with READ_ONLY_MODE=true until you have validated the connection; the server logs a security warning whenever a password is read from a plaintext file instead of the vault.

3. Connecting to the AI Client

Once CaptainMCP is configured, you need to expose it to your AI client. Depending on your tool of choice, the configuration will vary:

  • Claude Desktop: Add CaptainMCP to the `mcpServers` block in `claude_desktop_config.json`, pointing at the installed `start.cmd` (via `cmd /c`). Fully restart the client afterwards.
  • Cursor / other MCP clients: Register the same `start.cmd` path as a stdio MCP server in your client's MCP settings.
  • Interactive approvals: On clients that support MCP elicitation (Claude Desktop), write operations show a native approval dialog. On other clients, CaptainMCP automatically uses a preview + confirmation-token flow instead.