Before you start
- Claude Code with remote MCP and OAuth support. Use a current release with the localhost callback restored in version 2.1.231. Run the browser and CLI on the same machine.
- 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 this tool with your 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. Add Network Perspective
Add the project configuration
Create or edit .mcp.json in your project root.
If this file already exists, merge the np entry into its existing configuration. Preserve your other servers and settings. These values are public setup identifiers; no client secret is needed.
{
"mcpServers": {
"np": {
"type": "http",
"url": "https://app.networkperspective.io/mcp",
"oauth": {
"clientId": "np-claude-code",
"scopes": "np.read offline_access"
}
}
}
}Load the server
Open Claude Code in that project and approve the project MCP configuration when prompted. A shared configuration does not share sign-in credentials: each person connects their own account.
2. Connect your own account
Run /mcp inside Claude Code, choose np, and start authentication. Complete the browser sign-in, then return to Claude Code.
- Sign in with your own Network Perspective account in the browser.
- Choose the intended company or network when offered, review the requested access, and approve the connection.
- Return to your tool and check that Network Perspective is connected.
Each connection is authorized for one company. To work with another company, use a separate connection where your tool supports it.
3. Try the connection
Start a conversation in Claude Code and ask:
Use Network Perspective to tell me which company I’m connected to and the current reporting month.Check the answer: the assistant should use Network Perspective’s get_company_info tool and return the company you intended to connect and its current reporting month. A server appearing in a list alone does not confirm it is working.
Then try: “What metrics are available?”
If something gets in the way
The project server is missing
Check that .mcp.json is in the project root, contains valid JSON, and has been approved in Claude Code. Restart the session after changing the file if needed.
A localhost callback error appears
The registered callback is http://localhost/callback, with a runtime port chosen by the client. Version 2.1.229 changed the host; version 2.1.231 restored localhost. Update to a compatible release instead of replacing localhost with 127.0.0.1.
Authentication expires
Open /mcp and use the server’s authentication flow again. Confirm np is enabled before asking it to use Network Perspective.
Sign-in or company access fails
Check the exact client ID in this guide. If the client is rejected, contact Network Perspective. For a missing company or access denied, ask your Network Perspective administrator to check membership, AI assistant access, and report permissions.
The callback does not match
Contact support with the client version and callback value only. Do not send a full authorization URL, sign-in code, token, or secret. Do not change callback hosts or paths to work around an error.
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 it from your AI tool or clearing local files 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 →
Claude Code setup: Official MCP guide.
