How to connect Claude to your sales tracker

To connect Claude to your sales tracker, you add the tracker's MCP server as a connector, sign in as yourself, and switch it on in the chat. After that Claude reads and writes your actual record instead of guessing from whatever you typed earlier. The steps take a few minutes and are the same shape for any tracker that publishes a server. This guide uses CalcuCloser's as the worked example, because its steps are published and you can check every one of them against its connect page.

The reason to bother is narrow and practical. Most tracking fails at the moment the call ends and the next one starts, when a form with eleven fields loses to six minutes of breathing room. A connected assistant turns the form into a sentence. That is the whole benefit, and it is worth being clear that it is a smaller claim than most writing about MCP makes.

What connecting Claude to a tracker actually does

Without a connection, anything you tell Claude about a sale lives in the conversation. It is a summary, not a ledger: you cannot filter it by lead source, add it up into a month or check it against what you were paid. With a connection, Claude reaches your tracker through a Model Context Protocol server. It calls a named tool, such as log a sale, and the tracker creates the entry the same way it would if you had filled in the form yourself.

That pattern is what MCP sales tracking, defined refers to, and the category is explained properly there. The short version is that the assistant is the interface and your tracker remains the system of record. If you would rather see the same idea in ChatGPT, it is covered in how to log your sales in ChatGPT.

How to connect Claude to your sales tracker

The prerequisite is a tracker that publishes an MCP server. If yours does not, this route is closed and no amount of prompting opens it. Assuming it does, you need the server address. CalcuCloser's is https://calcucloser.velisi.io/mcp, and its connect page shows it with a copy button.

In Claude

1. Open Claude's custom connector dialog. CalcuCloser's connect page has a link that opens it with the name and address already filled in.
2. Review the details and click Add.
3. If the dialog does not open, go to Claude's Connectors page, choose Add custom connector, name it CalcuCloser and paste the server address.
4. Sign in when prompted. This is the step that makes the connection run as you, rather than through a shared key.
5. Enable the connector from the chat composer, then ask Claude to use it.

Whether custom connectors appear for you may depend on your Claude plan and on workspace settings. On a managed workspace, an administrator may need to switch them on.

In Claude Code

Claude Code connects from the terminal. CalcuCloser's connect page gives the exact command to copy, which adds the server at user scope over HTTP transport, named calcucloser. Then start Claude Code and run /mcp to confirm the connection, and sign in from that menu when it asks. After that, ask Claude Code to use CalcuCloser.

Refreshing after new abilities ship

Assistants remember what a server could do on the day you connected. When a tracker ships new abilities, refresh the connector in Claude, or start a new Claude Code session, so the assistant sees them. If the server address itself has changed, Claude cannot edit an existing address: remove the connector and add it again with the new one.

What to say once it is connected

The wording that works is the wording you would use with a colleague. Log the call I just had, closed at the usual rate, they came from the webinar list. I did forty-one dials and six conversations today. Log that conversation as a no, the objection was timing, they are back in the new quarter. How is my close rate this month against last month?

The point is not elegance. It is that the sentence is cheap enough to say while the tab is still open, which is the failure that ends most spreadsheet habits, described in commission tracking without spreadsheets.

What to check in the first week

Ask Claude to read the details back before it logs anything. Then open the app and look at what landed: the value, the date, the lead source, the commission and the payment schedule. Try being deliberately vague once, because that is the case that will catch you on a busy Friday. And check that correcting an entry in the app is easy, since you will need to do it eventually.

What connecting Claude does not fix

The call you did not mention is still missing. Connect everything available and Claude still only knows what you tell it. There is no version of this where the record fills itself in.

Write access deserves care too. An assistant that misreads a sentence can create an entry you then have to find and correct, which is annoying rather than dangerous, and is the reason the read-back habit is worth forming early. And the connection has no opinion about which numbers matter. It fetches whatever you name.

Where CalcuCloser fits

CalcuCloser by Velisi runs a server at calcucloser.velisi.io/mcp, with setup steps for ChatGPT, Claude, Claude Code and other MCP clients on the connect page. Once connected, your assistant can read your dashboard totals and goal progress, your performance for a week, month or quarter against the period before it, your objections and win and loss reasons, your offers and pay schedules, your upcoming paydays and your recent sales. It can also log a sale, a day of calls, or a full sales conversation with its outcome, which creates the deal, the commission and the payment schedule the same way the app does.

It runs as you, on your own data. It cannot see anyone else's numbers, change your billing or delete anything. It is a post-call system: there is no audio capture and no in-call clock, so nothing in it listens to a conversation while it is happening. What it does is make the minutes after a call cheap enough that the record survives a bad week. See the tracker.

Frequently asked questions