Before you start
- Amazon Quick Enterprise, with permission to create a team connector. Ask your Quick administrator to handle the one-time setup below.
- A Network Perspective account with access to the company you want to explore. Ask your Network Perspective administrator to enable AI assistant access if it is unavailable.
- Your organization's approval to use Amazon Quick with this data and allow its connection to Network Perspective.
The connection reads the reports and metrics available to your account, including report-visible comments and quotations. It does not change reports or settings.
1. Set up the team connector
Open the connector setup
In Amazon Quick, open Connectors → Create for your team → Model Context Protocol (MCP).
Add Network Perspective
Use these values on the integration details screen.
Network PerspectiveExplore monthly insights into developer experience, collaboration, focus, and delivery. Compare groups, review survey feedback, and track trends using the products enabled for your company.https://app.networkperspective.io/mcpChoose Public network for both Connection type and Auth server connection type, in line with your organization's network policy. Continue with Next.
Choose user authentication
Select User authentication, then Custom user based OAuth if that choice appears. Enter the settings below.
np-amazon-quickLeave the client secret empty. The client ID above is a public setup identifier; you do not need to create an OAuth application or generate a secret.
https://app.networkperspective.io/connect/tokenhttps://app.networkperspective.io/connect/authorizehttps://quick.aws.com/sn/oauthcallbackCheck that Quick's read-only redirect field matches this value. If it differs, contact Network Perspective before continuing. Do not replace it with a guessed callback.
Review and share with your team
Choose Create and continue. Complete sign-in if prompted, review the discovered actions, and continue through Quick's permission and sharing screens.
If your flow shows Manage Write Permissions, Manage Read Permissions, and Publish, review who should manage and use the connector. Network Perspective's tools only read data; those screen labels do not give them the ability to change your reports.
Share or publish the connector only to the intended people in your Quick account. Each person authorizes their own Network Perspective account.
2. Connect your own account
- Open the shared Network Perspective connector in Amazon Quick and start its sign-in flow when prompted.
- Sign in with your own Network Perspective account.
- Choose the intended company or network when offered, review the requested access, and approve the connection.
- Return to Quick and make sure Network Perspective is enabled for your conversation.
Each connection is authorized for one company. To work with another company, use a separate connection where Quick supports it.
3. Ask your first question
Start a conversation in Amazon Quick and ask:
Use Network Perspective to tell me which company I’m connected to and the current reporting month.Check the answer: Quick should use the Network Perspective connector and return the company you intended to connect. Seeing the connector in a list alone does not confirm it is working.
Then try: “What metrics are available?”
If something gets in the way
I cannot create a connector
Check your Quick Enterprise subscription and ask your workspace administrator whether custom connectors are allowed.
Sign-in or company access fails
Check the client ID and both OAuth URLs above. For a missing company or access denied, ask your Network Perspective administrator to check company membership, AI assistant access, and report permissions.
The redirect URL is different
Contact Network Perspective with the callback value and the Quick environment you use. Do not send the full authorization URL, a sign-in code, or any tokens.
Quick cannot reach Network Perspective
Ask your administrator to check the approved network path. Quick connects from AWS, so a working connection in your own browser does not confirm that Quick can reach it.
The connection expires or Quick ignores it
Reconnect through Quick's normal sign-in flow. Check that the connector is enabled for the conversation and explicitly ask Quick to use Network Perspective. If it repeatedly expires, contact support so we can check the connection.
When Network Perspective updates its tools, the connector owner should open its details in Quick and choose Sync. Complete reauthorization if prompted.
Disconnect whenever you need to
In Network Perspective, open Me → Connected agents, find the connection, and disconnect it. This revokes that connection's access.
Removing the connector in Quick alone does not revoke access in Network Perspective. Disconnecting cannot remove information already shared with the AI provider.
Open Connected agents →Need a hand? Contact Network Perspective →
For Amazon Quick's platform details, see the official AWS MCP integration guide.
