Verify the MCP Endpoint

You can reach the Essbase MCP Server at <base_URL>/essbase/rest/v1/ess-mcp.

Verifying the MCP endpoint checks whether:

• the Essbase MCP URL is correct
• the MCP server is reachable over the network
• authentication is successful
• the MCP server returns its discovery information

If you run a GET on that URL, it should return a discovery document with the server info, sub-endpoints, and capabilities:

{ 
  "server": { 
    "name": "Essbase MCP", 
    "version": "0.2.3" 
 }, 
"endpoints": { 
  "tools": "https://<essbase-server>/essbase/rest/v1/ess-mcp/tools", 
  "call": "https://<essbase-server>/essbase/rest/v1/ess-mcp/call"
 }, 
"capabilities": { 
  "tools": { 
    "listChanged": false 
  } 
 } 
}

You can also list the tool catalog directly using GET <base_URL>/essbase/rest/v1/ess-mcp/tools.

You can invoke Essbase tools using POST <base>/essbase/rest/v1/ess-mcp/call.

Optional: List the available Tools

After initialization, the AI client can use the tools/list method to discover which Essbase tools are available.

The visible tools depend on the access profile used in the endpoint, such as viewer, analyst, or admin.

Optional: Call an Essbase Tool

After discovering the available tools, the AI client can invoke one with the tools/call method.

The following example runs an Essbase calculation:

{ 
  "jsonrpc": "2.0", 
  "id": 2, 
  "method": "tools/call", 
  "params": { 
    "name": "essbase_run_calculation", 
    "arguments": { 
      "app_name": "Sample", 
      "db_name": "Basic", 
      "calc_script": "CALC ALL;", 
      "wait_for_completion": true 
    } 
  } 
}

The above example is optional, for testing. In normal use, the AI client creates and sends this request for you. You request the task in natural language, and the client selects and calls the appropriate Essbase MCP tool.