MCP FAQ

Your Promaster A Nintex Process Manager system administrator who administers a Nintex Promapp site and has rights to view and edit all areas of a Nintex Promapp site. must have the capability enabled for your tenant, the MCP URL for your tenant (https://<region-identifier>-pmp.promapp.com/mcp/<tenant name> e.g. https://prd-aue-pmp.promapp.com/mcp/mycompany) and your Nintex Process Manager account with a username and password. If you are using Single Sign-On (SSO) this will also work.

Use the following for your region identifier:

• au -> prd-aue

• ca -> prd-cac

• eu -> prd-neu

• us -> prd-wu3

• demo -> dmo-wu3

No. Process Manager MCP provides a connection between your AI assistant/Agent and your Nintex Process Manager repository. It does not include or run the AI models that are part of your AI Assistant/Agent. Any token usage, model usage, or related costs are managed and billed by your chosen AI provider.

All current Nintex Process Manager regions are supported (Demo, US, CA, EU and AU) except the AE (AEN) region.

Yes.

Not yet, as this is a future improvement we will be introducing.

User based authentication (username/password). SSO can also be used for authentication if it’s enabled for your Process Manager tenant.

Yes. Process and search results are filtered based on the permissions of the authenticated account. If the account you used to authenticate when connecting to Process Manager MCP does not have access to a process or group, it will not appear in results.

Follow the instructions here: Connect your agent to an existing Model Context Protocol (MCP) server and ensure you have your MCP URL available.

Follow the instructions here: Get started with custom connectors using remote MCP and ensure you have your MCP URL available.

We will introduce write capabilities, including:

• Updating process content

• Creating new processes

• Submitting processes for approval

• Reviewing processes

• Publishing processes