Developers

Use Sales Montana from Claude or ChatGPT soon

Connect your workspace to the assistant you already pay for, and ask it about your own sales floor in your own words. No dashboard, no export, no SQL.

What this is

Sales Montana exposes an MCP server. MCP is the open standard for letting an assistant use an outside system, and both Claude and ChatGPT speak it. Connect it once and the assistant can read your workspace and, if you allow it, act in it.

This is not a chatbot we built. It is your Claude or your ChatGPT, with your sales data available to it, alongside everything else it can already do.

Connecting

1. In Sales Montana, open Settings, then Developers, and create a connection. You choose the workspace and the access level.
2. Copy the server URL and the key it gives you. The key is shown once.
3. In Claude, add it under Connectors. In ChatGPT, add it as a connector in settings. Both will ask you to confirm what it is allowed to do.

{
  "mcpServers": {
    "sales-montana": {
      "url": "https://mcp.salesmontana.com/v1",
      "headers": {
        "Authorization": "Bearer sm_live_..."
      }
    }
  }
}

What you can ask it

Anything you could work out from your own data, in the words you would use with a colleague. Four people get four different things out of it.

If you are a rep

• Brief me on this account before my two o'clock. What did we say last time and what did they push back on?
• Who should I call first this morning and why?
• Draft the follow-up for the call I just had with the operations director.
• Which of my accounts have gone quiet for more than two weeks?
• What does the brain say about the pricing objection? Give me the line that works.

If you run the floor

• What changed this week? Read the calls, not the dashboard.
• Which objection came up most, and what did each rep say back to it?
• Show me every call over three minutes that did not end with a next step, grouped by rep.
• Compare this week's connect rate by hour against last month and tell me if our calling window is wrong.
• Which rep improved most, and what specifically did they change?
• Write my Monday update and put it in the team channel.

If you own the number

• What is our conversion rate by campaign, and where exactly are we losing people?
• Which campaign is worth more budget and which should we kill?
• Model what happens to pipeline if we add two reps to the campaign with the best connect rate.
• How much did we spend on minutes and AI this month against what we sold?
• Which accounts in the pipeline have stalled longer than they normally do at this stage?

If you run an agency

• Build this client's monthly report: calls made, meetings booked, what the market said back.
• Compare all three of my clients on connect rate and tell me which one's list is the problem.
• Which of my clients is quietly about to churn, based on how the calls are going?

Joining it to everything else

This is the part that a dashboard cannot do. It is your assistant, so your sales data sits alongside everything else it can already reach, and a request can cross the boundary in one go.

• Pull this week's objections and write them into the sales playbook doc.
• Take the accounts that booked meetings and check them against the finance spreadsheet to see which ones actually paid.
• Read the pricing page on a prospect's website, compare it with what they told us on the call, and tell me where the gap is.
• Draft the follow-ups for yesterday's interested leads, put them past me, then send the ones I approve.
• Every Monday at eight, write the floor update and post it.

Saving a job so you do not retype it

Both assistants let you save instructions and reuse them, as a Claude Project or a custom GPT. Point one at this connection, write the job once, and you have a purpose-built tool: a briefing assistant your reps open before every call, a reporting assistant that writes the same client report every month, a pipeline assistant that answers the questions your board asks.

That is the same idea as a skill, run from your side rather than ours. Use a skill when the job should happen on a schedule whether anybody is watching or not. Use a saved assistant when the job needs a person in the loop and needs to reach your other systems as well as this one.

The tools it gets

Permissions

A connection never has more access than the person who created it. An agent's connection sees the agent's accounts; an admin's sees the workspace. On top of that you pick a level when you create it, and you can only narrow, never widen.

Two things no connection can ever do, at any level: place a call, and change billing. Calling costs carrier money in real time and billing is not something an assistant should be able to reach by accident.

Safety

Every call through the connection is logged with the tool, the arguments and the result, visible under Settings, then Developers. Keys can be revoked instantly and are scoped to one workspace, so a person who works across three clients needs three keys and cannot mix them up.

Sales Montana documentation. Anything marked soon is designed and specified but not yet shipped.