MCP Server Integration

# Connect an AI Assistant to Nectar DXP

Overview

The Nectar DXP MCP Server lets AI assistants (Claude, ChatGPT, or any client that supports the Model Context Protocol) query your Nectar DXP unified communications and contact center monitoring platform directly, using natural language.

It is built into Nectar DXP. There is nothing to install or deploy on your side, and no API tokens or keys to copy. You sign in with your normal DXP credentials, and the assistant sees exactly what you can already see in DXP: same login, same permissions, same tenants.

Instead of logging into the DXP portal and navigating dashboards, you can ask your AI assistant questions like:

• "How was call quality for the Chicago office last week?"
• "Show me users with the worst Nectar Scores this month."
• "Are there any critical alarms right now?"
• "Why did calls into the Dallas contact center degrade this morning?"
• "What Cisco clusters do we have and are they healthy?"

The assistant translates these questions into calls against the MCP server, which retrieves the data from your DXP tenant and returns a plain-language answer.

Think of it as a third way into the same data, alongside the DXP web portal and the PowerShell / REST API.

Before You Start

You need:

• A working Nectar DXP login that can see the tenants, locations, and platforms you want to ask about. The assistant cannot see anything your account cannot.
• An AI client that supports remote MCP servers with OAuth sign-in. Claude (web, desktop, and Claude Code), ChatGPT on paid plans, and Cursor all qualify. Plan and setup details are below.
• A browser that can open the DXP sign-in window. Pop-up blockers and strict corporate proxies can interfere; see Troubleshooting.

Connecting

Server URL

Your organization's MCP server URL is your DXP hostname with mcp. in front:

https://mcp.<your-dxp-hostname>

For example, if you sign into DXP at https://us.nectar.services, your MCP server URL is:

https://mcp.us.nectar.services

Signing In

Authentication is a browser sign-in with your DXP credentials (OAuth 2.1). When your client first connects, it opens a browser window to your DXP login page. Sign in as you normally would and approve the request. Your client stores the session and reconnects automatically afterwards. If the session expires, the client prompts you to sign in again.

Client Setup

Claude (claude.ai and Claude Desktop)

1. Open Settings → Connectors.
2. Choose Add custom connector.
3. Paste the server URL and click Add, then Connect.
4. Complete the DXP sign-in in the browser window that opens.

On Claude Team and Enterprise plans, an organization owner must add the connector first. Members then enable and authorize it from their own Connectors settings. In each chat, make sure the connector is enabled in the tools menu.

ChatGPT

Custom MCP connectors require a paid ChatGPT plan and Developer Mode.

1. Open Settings → Connectors → Advanced and turn on Developer mode.
2. Back in Connectors, choose Create.
3. Enter a name, paste the server URL, and select OAuth for authentication.
4. Complete the DXP sign-in, then enable the connector in the chat where you want to use it.

Claude Code

claude mcp add --transport http nectar-dxp https://mcp.us.nectar.services

Then run /mcp inside Claude Code to complete the sign-in.

Cursor and other JSON-configured clients

{
  "mcpServers": {
    "nectar-dxp": {
      "url": "https://mcp.us.nectar.services"
    }
  }
}

Other clients that support remote MCP servers with OAuth should work with the same URL. Consult your client's documentation for where to enter it.

Network Note

Cloud-hosted assistants such as claude.ai and ChatGPT connect to the MCP server from the vendor's cloud, not from your laptop. If your organization restricts which sources can reach your DXP hostname, the connector may fail even though the DXP portal works fine for you. Ask your network team to allow the vendor's published egress ranges to reach mcp.<your-dxp-hostname>.

What the Assistant Can See and Do

• Read-only. Every tool the MCP server exposes queries data. The assistant cannot change configuration, acknowledge or clear alarms, create tickets, or modify anything in DXP.
• Your permissions, your tenants. Requests run as your DXP user. Results are limited to the tenants, locations, and platforms your DXP role can already see. If you can see only one tenant in the portal, the assistant sees only that tenant too.
• Multi-tenant and MSP users. If your account spans several tenants, name the tenant in your question ("...for the Acme Corp tenant"). The assistant can list the tenants you have access to if you are unsure of the exact name.
• Disconnecting. Remove or disconnect the connector in your AI client to revoke its access. A DXP administrator can also disable the underlying user account, which cuts off the assistant immediately.

Verify It Works

After connecting, ask:

"Is the DXP connection working?"

The assistant runs a diagnostic tool and should report something like:

• DXP URL: https://us.nectar.services
• Auth method: request headers
• Access token: present, valid, expires in about 55 minutes
• Reachability: HTTP 200 in under a second
• Recommendations: none

A healthy result shows a valid token and a 200 status. Anything else is worth copying into a support request (see Support).

What You Can Ask

You do not need to know tool names. Ask naturally and the assistant picks the right tool or combination of tools.

Health Summaries

Broad "how is X doing?" questions. The assistant pulls quality, volume, alarms, and trends together in one pass.

"How is the Acme Corp tenant doing this week?"
"Give me a health summary for the London office."
"How has Jane Doe's call experience been this month?"

Session Analytics & Call Quality

Call and meeting quality, volume, and trends, from summaries down to individual sessions. A Nectar Score is DXP's 0-to-5 quality rating for a session, combining network and media metrics.

"How many sessions did we have on Teams last week, broken down by quality?"
"Show me the call quality trend for the New York location over the past 30 days."
"Give me the quality metrics for every location, ranked worst to best."
"Find sessions from last Tuesday with poor audio quality on the VPN network."
"Pull up the details for session 1234-5678 and tell me what went wrong."

Meetings & Conferences

Multi-party meeting details: who organized, who joined, how quality changed over the meeting.

"Find Zoom meetings yesterday with more than 20 participants."
"Who had the worst audio in the 9 AM all-hands on Teams?"
"Show me the timeline of quality issues in that meeting."

Contact Center

Conversation journeys across WebRTC-monitored contact center platforms such as Genesys Cloud, Amazon Connect, Five9, and NICE CXone.

"Why did calls into the Dallas contact center degrade this morning?"
"Show me the journey for the conversation with ID 98765 and where quality dropped."
"Which contact center agents had the most poor-quality calls this week?"

Users & Locations

Look up specific users, or the network locations configured in your tenant.

"Find the user John Smith."
"What locations are configured for this tenant?"
"Which locations have no sessions in the last 7 days?"

Rooms & Devices

Inventory and health of meeting-room systems and monitored devices.

"List our meeting rooms and their current status."
"Which devices are showing a problem right now?"

Tenant Management

Which tenants exist, what platforms they use, and their basic details.

"List all the tenants I have access to."
"What platforms are configured for the Acme Corp tenant?"
"How many users are on each platform across all tenants?"

Events & Alarms

System alerts by severity, location, or keyword.

"How many critical alarms happened today?"
"List all major and critical alarms from the Denver location this week."
"Are there any alarms mentioning SIP trunk failures?"

Endpoint Testing

Results from Nectar Endpoint Client diagnostic tests.

"How many endpoint tests passed vs. failed this week?"
"Show me the endpoint test summary broken down by hub."

Cisco Infrastructure

Cisco Unified Communications Manager clusters, servers, services, and inventory.

"List our Cisco clusters and their status."
"How many SIP trunks and gateways do we have in the main cluster?"
"Are any services down on the Cisco publisher?"
"What is CPU and memory usage on the Cisco servers right now?"

Data Pipeline Status

Whether DXP is receiving and processing data from each source.

"Is data flowing from all our sources?"
"When did DXP last receive Teams data?"

Go Further

The MCP server returns data. Your AI assistant adds everything else it can do, such as writing summaries, drafting emails, or building slides. For example:

"What locations had the worst call quality last month? Create a presentation outlining the issues."

The data comes from DXP; the presentation is built by your assistant using its own capabilities.

Supported Platforms

The MCP server can query sessions from every platform your DXP tenant monitors, including Microsoft Teams, Zoom, Cisco Unified CM, Cisco Meeting Server, Cisco Webex Calling, Avaya Aura, Genesys, Jabra, and WebRTC contact center platforms (Genesys Cloud, Amazon Connect, Five9, NICE CXone, Avaya cloud, Webex Contact Center). Legacy Skype for Business and Lync data is also available where still collected.

Tips and Limits

• Be specific about time ranges and locations. "Last 7 days," "the Chicago office," and "this month" all help the assistant scope the query correctly.
• Ask summary questions first. Summaries, trends, and per-location rankings return in seconds. Requests for individual session lists are heavier.
• Session lists are capped. A single request returns at most 500 session records, and the default is 20. Narrow the question (time, location, user, quality) rather than asking for "every session."
• Individual DXP queries time out after 30 seconds. If a very broad question fails, ask for a smaller slice.
• Follow up naturally. You can drill into a specific session, user, or location after seeing a summary. The assistant keeps context within the conversation.
• Ask the assistant to show its work. If a number looks surprising, ask "Which tool did you use and what did it return?" A well-behaved assistant will tell you when a tool call failed rather than guess.

Troubleshooting

Support

If the steps above do not resolve the issue, contact your Nectar administrator or Nectar Support with:

• The output of the diagnostic check ("Is the DXP connection working?")
• Your AI client and version (for example, Claude Desktop 1.x, ChatGPT web, Claude Code 2.x)
• The exact MCP server URL you entered
• Your DXP tenant name
• The approximate time of the failure and the question you asked