Skip to main content

Quick Start

Invoke a Digital Banking tool through the Candescent MCP Server in a few minutes. This guide assumes you have already completed Installation and candescent-digital-banking is connected in your IDE. The examples below use the Stage MCP URL (https://api.stage.candescent.com/mcp); use the Sandbox URL instead if that is the environment you configured.

Beta

The MCP Server is in beta for testing only. Do not use production customer data or production MCP endpoints.

Discover Available Tools​

In your IDE's AI chat (with MCP enabled), ask:

What Candescent Digital Banking tools are available from the MCP server?

The IDE should list tools mapped to REST operations — for example list accounts, list transactions, and get customer profile. See Digital Banking APIs for the complete beta list.

Run Your First Tool Call​

Ask the assistant to call a read-only operation using your test entitlements. See Digital Banking APIs for sample prompts for every MCP tool.

List all accounts for user <hostUserId> using the Candescent MCP server.

The MCP Server forwards the tool invocation to the underlying REST API with your bearer token and returns structured JSON the model can summarize.

important

Replace placeholder IDs with values valid in your Stage or Sandbox environment. The assistant only returns data your app's credentials and scopes are entitled to access.

Example: What Happens Under the Hood​

When you ask to list accounts:

  1. Your IDE sends a tools/call request to https://api.stage.candescent.com/mcp with your Authorization and transactionId headers.
  2. The MCP Server validates your bearer token.
  3. The server invokes the equivalent of List Accounts V1 against the Digital Banking gateway.
  4. The JSON response is returned to your IDE as a tool result.

When your access token expires, obtain a new one per Installation and update the Authorization value in mcp.json.

Next Steps​