Connecting to QPR ProcessAnalyzer MCP Server - Revision history

MarHink: /* Step 3: Add MCP Connector to Agent */

2026-06-10T08:38:49Z

Step 3: Add MCP Connector to Agent

← Older revision		Revision as of 08:38, 10 June 2026
Line 374:		Line 374:
	# Sign in to Snowsight.		# Sign in to Snowsight.
	# In the navigation menu, select '''AI & ML''' → '''Agents'''.		# In the navigation menu, select '''AI & ML''' → '''Agents'''.
	# ~~Select~~ your agent from the list.		# Create a new agent, or select your agent that you want to be able to connect to the QPR ProcessAnalyzer from the list, if you have an agent already created.
	# Select '''MCP Connectors'''.		# Select '''MCP Connectors'''.
	# From the list of '''Available Connectors''', select '''QPR ProcessAnalyzer'''.		# From the list of '''Available Connectors''', select '''QPR ProcessAnalyzer'''.

Ollvihe: /* Snowflake Cortex Agents and Snowflake CoWork */

2026-06-09T20:54:50Z

Snowflake Cortex Agents and Snowflake CoWork

← Older revision		Revision as of 20:54, 9 June 2026
Line 341:		Line 341:
	</syntaxhighlight>		</syntaxhighlight>

	== Snowflake Cortex Agents ~~and Snowflake CoWork~~ ==		== Snowflake CoWork and Snowflake Cortex Agents ==
	Snowflake [https://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-agents Cortex Agents] and [https://docs.snowflake.com/en/user-guide/snowflake-cortex/snowflake-cowork Snowflake CoWork] can connect to QPR ProcessAnalyzer as an external MCP server using Snowflake's MCP Connectors feature. To setup the connection, you can follow the instruction below or check out the Snowflake documentation (https://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-agents-mcp-connectors#custom-mcp-connectors).		Snowflake [https://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-agents Cortex Agents] and [https://docs.snowflake.com/en/user-guide/snowflake-cortex/snowflake-cowork Snowflake CoWork] can connect to QPR ProcessAnalyzer as an external MCP server using Snowflake's MCP Connectors feature. To setup the connection, you can follow the instruction below or check out the Snowflake documentation (https://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-agents-mcp-connectors#custom-mcp-connectors).

Ollvihe: /* Snowflake Cortex Agents and Snowflake CoWork (Intelligence) */

2026-06-09T20:54:24Z

Snowflake Cortex Agents and Snowflake CoWork (Intelligence)

← Older revision		Revision as of 20:54, 9 June 2026
Line 341:		Line 341:
	</syntaxhighlight>		</syntaxhighlight>

	== Snowflake Cortex Agents and Snowflake CoWork ~~(Intelligence)~~==		== Snowflake Cortex Agents and Snowflake CoWork ==
	Snowflake [https://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-agents Cortex Agents] and [https://docs.snowflake.com/en/user-guide/snowflake-cortex/snowflake-cowork Snowflake CoWork] can connect to QPR ProcessAnalyzer as an external MCP server using Snowflake's MCP Connectors feature. To setup the connection, you can follow the instruction below or check out the Snowflake documentation (https://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-agents-mcp-connectors#custom-mcp-connectors).		Snowflake [https://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-agents Cortex Agents] and [https://docs.snowflake.com/en/user-guide/snowflake-cortex/snowflake-cowork Snowflake CoWork] can connect to QPR ProcessAnalyzer as an external MCP server using Snowflake's MCP Connectors feature. To setup the connection, you can follow the instruction below or check out the Snowflake documentation (https://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-agents-mcp-connectors#custom-mcp-connectors).

Ollvihe: /* Snowflake Cortex Agents and Snowflake Intelligence */

2026-06-09T20:54:12Z

Snowflake Cortex Agents and Snowflake Intelligence

Ollvihe: /* Step 1: Create API Integration */

2026-05-26T14:13:41Z

Step 1: Create API Integration

← Older revision		Revision as of 14:13, 26 May 2026
Line 349:		Line 349:

	==== Step 1: Create API Integration ====		==== Step 1: Create API Integration ====
	Run the following SQL in Snowflake to create an API integration ~~with~~ full OAuth configuration:		Run the following SQL in Snowflake to create an API integration (using full OAuth configuration):

	<syntaxhighlight lang="sql">		<syntaxhighlight lang="sql">

Ollvihe: /* Setup with OAuth Dynamic Client Registration (DCR) */

2026-05-26T14:07:14Z

Setup with OAuth Dynamic Client Registration (DCR)

← Older revision		Revision as of 14:07, 26 May 2026
Line 346:		Line 346:
	=== Setup with OAuth Dynamic Client Registration (DCR) ===		=== Setup with OAuth Dynamic Client Registration (DCR) ===

	Before running the following commands, change to the intended owner role for the API integration and MCP server.		Before running the following commands, change to the intended owner role for the API integration and the external MCP server.

	==== Step 1: Create API Integration ====		==== Step 1: Create API Integration ====

Ollvihe: /* Setup with OAuth Dynamic Client Registration (DCR) */

2026-05-26T14:06:47Z

Setup with OAuth Dynamic Client Registration (DCR)

← Older revision		Revision as of 14:06, 26 May 2026
Line 345:		Line 345:

	=== Setup with OAuth Dynamic Client Registration (DCR) ===		=== Setup with OAuth Dynamic Client Registration (DCR) ===

			Before running the following commands, change to the intended owner role for the API integration and MCP server.

	==== Step 1: Create API Integration ====		==== Step 1: Create API Integration ====

Ollvihe: /* Method 2: JSON Configuration with API Key */

2026-05-25T13:15:49Z

Method 2: JSON Configuration with API Key

← Older revision		Revision as of 13:15, 25 May 2026
Line 58:		Line 58:

	After saving, completely quit Claude Desktop (not just close the window) and restart it. Look for the MCP server indicator in the bottom toolbar of the conversation area to confirm the connection.		After saving, completely quit Claude Desktop (not just close the window) and restart it. Look for the MCP server indicator in the bottom toolbar of the conversation area to confirm the connection.

			Note that the locally installed Claude Desktop application is needed to use the API key authentication - the browser based claude.ai doesn't support API keys.

	=== Verification ===		=== Verification ===

Ollvihe: /* Setup with OAuth Dynamic Client Registration (DCR) */

2026-05-25T11:17:37Z

Setup with OAuth Dynamic Client Registration (DCR)

← Older revision		Revision as of 11:17, 25 May 2026
Line 350:		Line 350:
	CREATE API INTEGRATION qpr_processanalyzer_mcp_api		CREATE API INTEGRATION qpr_processanalyzer_mcp_api
	API_PROVIDER = external_mcp		API_PROVIDER = external_mcp
	API_ALLOWED_PREFIXES = ( 'https://your-pa-server.com/' )		API_ALLOWED_PREFIXES = ('https://your-pa-server.com/')
	API_USER_AUTHENTICATION = (		API_USER_AUTHENTICATION = (
	TYPE = OAUTH_DYNAMIC_CLIENT		TYPE = OAUTH_DYNAMIC_CLIENT

Ollvihe: /* Claude Desktop */

2026-05-22T08:43:08Z

Claude Desktop

← Older revision		Revision as of 08:43, 22 May 2026
Line 6:		Line 6:

	=== Method 1: Custom Connectors / OAuth ===		=== Method 1: Custom Connectors / OAuth ===

	For a remote QPR ProcessAnalyzer MCP server with OAuth, use the Custom Connectors feature:		For a remote QPR ProcessAnalyzer MCP server with OAuth, use the Custom Connectors feature:

	# Open Claude Desktop.		# Open Claude Desktop.
	# Click the '''+''' button at the bottom of the chat area.		# Click the '''+''' button at the bottom of the chat area.
Line 17:		Line 15:
	# Once connected, the QPR ProcessAnalyzer tools will be available in your conversations.		# Once connected, the QPR ProcessAnalyzer tools will be available in your conversations.

	~~Note~~: ~~Custom Connectors are available on '''Pro'''~~, ~~'''Max'''~~, ~~'''Team''', and '''Enterprise''' plans. Remote servers use Streamable HTTP transport with OAuth~~.		It's also possible to configure the MCP connection to the claude_desktop_config.json file as follows:
			<syntaxhighlight lang="json">
			{
			"mcpServers": {
			"QPR ProcessAnalyzer": {
			"command": "npx",
			"args": [
			"mcp-remote",
			"https://your-pa-server.com/qprpa/api/mcp"
			]
			}
			}
			}
			</syntaxhighlight>

	=== Method 2: JSON Configuration with API Key ===		=== Method 2: JSON Configuration with API Key ===

	For API key authentication, edit the <code>claude_desktop_config.json</code> file directly.		For API key authentication, edit the <code>claude_desktop_config.json</code> file directly.

Line 47:		Line 57:
	</syntaxhighlight>		</syntaxhighlight>

	After saving, ~~'''~~completely quit~~'''~~ Claude Desktop (not just close the window) and restart it. Look for the MCP server indicator in the bottom toolbar of the conversation area to confirm the connection.		After saving, completely quit Claude Desktop (not just close the window) and restart it. Look for the MCP server indicator in the bottom toolbar of the conversation area to confirm the connection.

	=== Verification ===		=== Verification ===