Maximizer MCP Server

The Maximizer MCP Server lets AI assistants work with your CRM data. You connect it once, sign in with your Maximizer account, and from then on you can ask your assistant about your contacts, opportunities, tasks and activities, or have it create tasks and notes for you. It is built on the Model Context Protocol (MCP), the open standard AI assistants use to connect to external systems.

✅
What you need

A Maximizer CRM Live account on release M7 or later. The MCP Server is not available for on-premise installations.

An approved AI assistant. Today that is Claude (web, desktop, mobile and Claude Code). See Approved assistants for why.

MCP enabled for your tenant. If sign-in stops with a message that the application is not recognized, contact Maximizer Support.

What you can do

Once connected, the MCP Server gives your assistant what it needs to understand and work with your Maximizer data, so you can ask questions and give instructions in plain language. Your assistant sees exactly what your Maximizer user can see, and nothing more.

Some prompts to try:

Which of my opportunities are closing this month, and what stage is each one in?

Show me the notes and the last five interactions for the Northwind Traders account.

What tasks do I have overdue? Mark the call with Jane Doe as done.

Create a task for next Tuesday to follow up with Contoso about the renewal.

Add a note to the Smith household: they asked about the new fee schedule.

Which leads came in this week and have not been contacted yet?

Rank my households by assets under management.

Connect Claude

Claude connects to this address:

https://mcp.maximizer.com/mcp

Claude (web, desktop and mobile)

Open Settings, then Connectors, and choose Add custom connector. On Team and Enterprise plans an organization owner adds the connector once; members then enable it for themselves.
Give it a name such as Maximizer and paste the address above. Leave the advanced fields empty.
Click Add, then Connect, and follow the Maximizer sign-in in your browser.
Back in Claude, enable the Maximizer connector in the tools menu of your chat and start asking.

Claude Code

In a terminal run:

claude mcp add --transport http maximizer https://mcp.maximizer.com/mcp

Start claude, type /mcp, select maximizer and choose Authenticate, then follow the Maximizer sign-in in your browser.
When the browser reports success, /mcp shows the server as connected.

Security and data

Sign in with your Maximizer account. The first time you connect, Maximizer opens a short sign-in in your browser. Follow the steps, confirm that you allow the assistant to access your tenant, and you are connected. The connection renews itself in the background; you are only asked to sign in again if you disconnect or after a long period without use.
Same permissions as you. Every request runs under your Maximizer user. Records, fields and tenants you cannot see in Maximizer are equally invisible to your assistant.
Live data, nothing stored. The MCP Server keeps no copy of your CRM data. Each question reads the current data through Maximizer, exactly like the Maximizer web application does.
Review before you confirm. AI assistants can be misled by content they read, including text inside a note or an email. Read the summary of any action your assistant proposes, especially anything that deletes data, before you approve it.
Audit. Changes made through the assistant appear in Maximizer under your user, like any other change you make.

🔒
Your password is never shared with the assistant. Sign-in happens on Maximizer's own pages, and the assistant receives only a limited access token that you can revoke at any time by disconnecting the connector in your assistant's settings.

Good to know

Results are capped per question. When a list is cut off, the assistant is told so and can narrow the question or continue with the next page.
Custom fields are supported. If the assistant cannot find a field, ask it to look up the field name first.

Troubleshooting

What you see	What it means	What to do
The assistant says it could not reach the server	A network policy blocks `mcp.maximizer.com`, or the assistant is not approved yet	Ask IT to allow `mcp.maximizer.com` and `auth.maximizer.com`, or check the approved assistants above
Sign-in stops with a message that the application is not recognized	MCP is not enabled for your tenant	Contact Maximizer Support
Sign-in cannot find a Maximizer account for your email	The email is not the one registered on your Maximizer user	Use the email shown under your profile in Maximizer, or ask your administrator to check it
The assistant returns fewer records than you expected	The result hit the per-question cap	Ask it to narrow the search or to continue with the next page

Questions and feedback

The MCP Server keeps growing. If you have questions, run into a problem, or want your assistant to be able to do something it cannot do yet, tell us in the developer forum.

Approved assistants

Connecting an AI assistant to your CRM data is a security decision, so Maximizer approves assistants individually rather than accepting any client that asks. To be approved, an assistant has to implement the current MCP authorization specification in full:

The MCP authorization specification, revision 2025-11-25 or later, over the Streamable HTTP transport.
Discovery of the authorization server through the standard metadata (RFC 9728 protected resource metadata, then RFC 8414 authorization server metadata), starting from the 401 challenge the server returns. Endpoints must not be hardcoded. For reference, a compliant client resolves https://mcp.maximizer.com/.well-known/oauth-protected-resource and then https://auth.maximizer.com/.well-known/oauth-authorization-server/v1.
OAuth 2.1 authorization code flow with PKCE (S256). Refresh tokens are rotated on every use; the client must store the new refresh token returned with each response.
Client identification through a Client ID Metadata Document (CIMD): the client id is an HTTPS URL, hosted by the assistant vendor, that serves the client's metadata (name, redirect URIs). Redirect URIs must use HTTPS, except loopback addresses (localhost or 127.0.0.1 on any port) for native clients.

Claude was the first major assistant to meet this bar, which is why it is the only approved assistant today. We are tracking the other major providers, such as OpenAI (ChatGPT and Codex), Microsoft Copilot, Cursor and Google Gemini, and will approve each one as it adopts these requirements.