For the complete documentation index, see llms.txt. This page is also available as Markdown.

Coupa

Coupa is a business spend management platform for procurement, invoicing, expenses, suppliers, and supply chain operations.

  • MCP connection

Connectors

Choose the connector that matches your authentication method. The options below use the names shown in StackAI.

Connector
Authentication

Coupa (MCP)

MCP with OAuth

Coupa (MCP)

Connect to a customer-hosted Coupa MCP server or managed gateway. The server configuration and Coupa permissions govern available tools.

Set up in Coupa

  1. Deploy or obtain access to an OAuth-protected Coupa MCP server or managed gateway. Coupa does not provide a shared first-party endpoint for this connector.

  2. Obtain the HTTPS MCP endpoint and any client registration details required by that server.

Set up in StackAI

  1. Open Settings → Connections, add a connection, and select Coupa (MCP).

  2. Complete the connector configuration below. If you do not have access to these settings, ask your StackAI administrator to configure the connector.

  3. Select Connect, sign in to the provider account, and review the requested access. Complete authorization to return to StackAI.

  4. Save the connection and check its connection status. Select this saved connection when configuring an action or feature that uses it.

Connector configuration

StackAI field
Required
What to enter

Server URL

Yes

The HTTPS endpoint of your Coupa MCP server or managed MCP gateway. Coupa does not operate a shared first-party MCP endpoint.

Scopes

Optional / as applicable

OAuth scopes advertised or required by the MCP server.

Client ID

Optional / as applicable

The OAuth client ID (e.g., 1234567890). You may not need to set this, the OAuth flow will try to set it with Dynamic Client Registration, but some MCP Servers don't support it, so they require a Client ID.

Client Secret

Optional / as applicable

The OAuth client secret (e.g., 1234567890). You may not need to set this, the OAuth flow will try to set it with Dynamic Client Registration, but some MCP Servers don't support it, so they require a Client Secret.

Authorization Endpoint

Optional / as applicable

The OAuth endpoint URL (e.g., https://mcp.example.com/oauth2/authorize). You probably don't have to set this, the OAuth flow will try to discover it on its own.

Custom Headers

Optional / as applicable

Optional custom headers to send to the MCP server for authentication or other purposes.

Provider documentation: Setup reference.

Verify the connection

Check that the connection is healthy. Then run a read operation against a resource the connected account can access. A successful connection check confirms authentication; it does not guarantee permission for every action.

If access is denied, check the credential or OAuth permissions, the selected account or environment, and access to the specific resource. Update expired credentials or reconnect after permissions change.

Important behavior

If an operation is denied, check the connection’s granted permissions and the account’s access in the provider. Reauthorize the connection when it needs additional permissions.

The catalog lists the fields and capabilities available in the supplied provider definition. Availability can also depend on your deployment and organization’s Feature Access settings.

Last updated

Was this helpful?