Nexus ships a native MCP (Model Context Protocol) server. AI agents using Claude, Cursor, or any MCP-compatible platform can self-register, authenticate with an API key, and operate Nexus autonomously — reading orders, checking stock, sending messages, searching contacts, and updating statuses. No custom API integration required; the agent discovers available tools from the MCP manifest and starts working immediately.
The Model Context Protocol (MCP) is an open standard that lets AI agents discover and call tools exposed by external services. Rather than writing custom API integration code for every AI agent you want to use, you point the agent at the Nexus MCP manifest and it learns what Nexus can do by itself. The Nexus MCP server exposes the full operational surface of the platform as callable tools — meaning an AI agent can compose multi-step operations across orders, conversations, contacts, and inventory using natural language instructions. A Claude agent can check whether a flagged order is from a repeat customer, look up their conversation history, read the AI complaint signal, and send them a WhatsApp resolution message — all in a single autonomous run, without a human clicking through Nexus manually. The agent self-registers on first use and authenticates with a scoped JWT on every subsequent call.
Agents discover the Nexus tool manifest at GET /.well-known/mcp.json, register themselves with POST /agent-register, and receive a scoped API key. On each session they exchange the key for a short-lived JWT via POST /agent-auth. All subsequent tool calls go to POST /mcp-server with the JWT in the Authorization header. No manual configuration in Nexus is needed beyond issuing the initial key.
The MCP tool set covers orders (read, search, status update), contacts (lookup, create, tag, update), conversations (read thread, post internal note), inventory (check stock, list low-stock items), messaging (send WhatsApp template or free-form message), and AI signals (read churn score, complaint flags, RFM segment). Agents on Scale plan get additional tools for analytics queries and bulk operations.
Read-only MCP access is available on the Free tier so developers can explore the API surface and build agent prototypes at no cost. Write access — sending messages, updating statuses, modifying contacts — is unlocked on Growth and Scale plans. Each API key carries a permission scope, so you can issue a read-only key for a monitoring agent and a full-write key for an autonomous operations agent from the same Nexus account.
Connecting an AI agent to the Nexus MCP server requires only an HTTP client and a Nexus account. The four-step protocol is standardized and works with any MCP-compatible agent framework without code changes on the Nexus side.
GET https://nexus.aiforstartups.io/.well-known/mcp.json — this returns the full tool manifest including endpoint URLs, tool names, parameter schemas, and permission requirementsPOST /agent-register supplying a name and contact email — Nexus returns an API key that you store securely in your agent's environmentPOST /agent-auth — the JWT is scoped to the agent's permission level and expires after a configurable TTLPOST /mcp-server, passing the tool name and parameters in the request body and the JWT in the Authorization: Bearer header/.well-known/mcp.json on your Nexus instance.Connect Claude, Cursor, or any MCP agent to your orders, conversations, and CRM — no custom integration code, no API wrapper, just the MCP manifest and a key.