Nexus MCP
Nexus MCP connects an agent to the Nexus CRM’s MCP server. The agent can search contacts, read the record of a contact or an account, look up deals and the sales pipeline, and log notes, calls, tasks and next steps. It can also propose new deals or changes to existing ones, which a person approves in Nexus.
You don’t have to choose an operation: the component gives the agent every tool the server offers, and the agent decides which one to use each time. The agent works as the person who signed in on the credential and only sees what that person sees in Nexus.
When to use it
- A salesperson wants an assistant that prepares every meeting with the customer’s history.
- You want to ask in a chat how the sales pipeline is going or which deals are stuck.
- After a call, the salesperson tells the assistant what was discussed and it logs it in Nexus with the next step.
Configuration
You need an MCP Remote server credential connected to Nexus’s MCP server with your sign-in. See Credentials and Use MCP servers.
- Create an MCP Remote server credential.
- In MCP Server url type your Nexus address followed by
/api/v1/mcp, for examplehttps://nexus.your-company.com/api/v1/mcp. - In MCP Server auth choose
OAuth2.1and click the sign-in button. - Sign in to Nexus with your account. Nexus asks you what NappAI can do: Read only or Read and work. Choose Read and work if the agent must record anything, and click Authorize.
| Field | What it does |
|---|---|
| Credential (required) | The MCP Remote server credential with your Nexus sign-in. |
| MCP server URL | Filled in by the credential: the Nexus address or its MCP server address (the one ending in /api/v1/mcp). |
| Only these tools (advanced) | Optional. The names of the tools you want to give the agent, separated by commas. Empty: every tool the person can use. |
Tools the agent receives
The list comes from Nexus’s server itself when the flow runs, and depends on what the person can do. Among others:
- To read:
search_contacts,get_contact_360,get_contact_timeline,get_account_360,get_my_deals,get_deal,get_deal_activities,get_pipeline_summary,get_offers,get_catalog,search_resourcesandsearch_tenders. - To work:
create_lead,create_note,log_interaction,add_contact_task,add_next_step,create_deal,update_dealandmove_deal_stage.
Output
The Tools output delivers the tools ready for an agent. Connect it to the Tools input of an Agent.
Example
A salesperson wants to prepare her meetings from a chat.
- Build a chat with Chat Input, an Agent and Chat Output.
- Add Nexus MCP with the salesperson’s credential and connect Tools to the agent’s Tools input.
- In the agent’s instructions, explain that it works on the Nexus CRM, that when it proposes a change to a deal it must give the approval link, and that it must never say a deal is closed.
- The salesperson writes “Prepare tomorrow’s meeting with Southern Builders” and the agent looks up the contact, reads their history and open deals, and gives her a summary.
Good practices
- For an assistant that only reads, sign in with Read only, or put only the reading tools in Only these tools.
- For a fixed step of the flow, without an agent, use Nexus CRM.
- If the connection with Nexus stops working, edit the credential and click Revalidate to sign in again.
Security and limitations
- Nexus allows at most 120 calls and 30 actions per minute.
- The agent can’t close deals, send emails from Nexus or use Nexus’s own assistant.
- Whatever the agent records is in the name of the credential’s person.
- You can withdraw NappAI’s access in Nexus, under My profile › Connections › AI assistants.
Related components
- Nexus CRM: fixed steps on the CRM, without an agent.
- Nexus Webhook: starts the flow with what happens in Nexus.
- MCP Connection: connect to any MCP server.