Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.ampup.ai/llms.txt

Use this file to discover all available pages before exploring further.

The AmpUp MCP server exposes your sales data — accounts, deals, meetings, analysis, tasks, deal memory, Slack, and CRM sync — as tools that any MCP-compatible AI assistant can call. Set it up in Claude Desktop, Claude Code, or claude.ai. The server runs on FastMCP 3.x, advertises protocol version 2025-03-26, and supports the io.modelcontextprotocol/ui extension so MCP-apps-aware clients can render rich UI surfaces.
For the end-user OAuth setup (no API keys, works in claude.ai), see the MCP integration guide.

Prerequisites

An AmpUp API key (generate one at Settings → API Keys in the dashboard)
An MCP-compatible client (Claude Desktop, Claude Code, Cursor, Windsurf, etc.)

Claude Code

Add AmpUp to your project’s .mcp.json or your global Claude Code settings:
{
  "mcpServers": {
    "ampup": {
      "type": "sse",
      "url": "https://app.ampup.ai/mcp/sse",
      "headers": {
        "Authorization": "Bearer sk-a79-YOUR_API_KEY"
      }
    }
  }
}
Claude Code connects over SSE (server-sent events) — no local process needed.

Claude Desktop

Add the following to your Claude Desktop config file:
Edit ~/Library/Application Support/Claude/claude_desktop_config.json:
{
  "mcpServers": {
    "ampup": {
      "url": "https://app.ampup.ai/mcp/sse",
      "headers": {
        "Authorization": "Bearer sk-a79-YOUR_API_KEY"
      }
    }
  }
}
Restart Claude Desktop after saving the config.

claude.ai

claude.ai uses OAuth — no API key needed:
1

Open MCP settings

In claude.ai, go to Settings → Connected Apps and search for AmpUp.
2

Connect

Click Connect and sign in with your AmpUp account. OAuth handles the rest.
3

Configure permissions

Choose which tools the assistant can use. Read-only tools are enabled by default.
See the full MCP integration guide for screenshots and details.

Other MCP Clients

Any client that supports MCP over SSE can connect using:
SettingValue
URLhttps://app.ampup.ai/mcp/sse
Auth headerAuthorization: Bearer sk-a79-YOUR_API_KEY
TransportSSE (server-sent events)
Protocol version2025-03-26
Serversales-meeting-analysis (FastMCP 3.x)
If your org has a dedicated subdomain (e.g. acme.ampup.ai), the MCP endpoint is also exposed at https://<your-org>.ampup.ai/mcp/sse. Both URLs work with the same API key.

Available Tools

The MCP server exposes 90+ tools organized by domain. Here’s a summary — your AI assistant sees full descriptions and parameter schemas automatically via tools/list.

Read Operations

ToolDescription
get_my_nameCurrent user’s display name (and email-fallback hint for voice agents)
get_orgCurrent org with workspace summary
list_orgsAll orgs the API key can access
get_workspace_statusLocal workspace sync state (last sync, entity counts)
list_accountsSearch and browse accounts
get_accountFull account details
list_opportunitiesSearch and filter deals
get_opportunityDeal details with optional context
get_deal_contextAggregated deal context for prompts
get_deal_memoryPersistent deal memory store
list_deal_filesFiles attached to a deal
list_meetingsSearch meetings by status, date, account, or deal
get_meetingMeeting overview and analysis
get_meeting_transcriptFull verbatim transcript
get_transcript_excerptTranscript slice by time range or chapter
list_meeting_analysesAnalyses run on a meeting
get_pre_meeting_briefPreparation context before a call
get_post_meeting_briefOutcomes and follow-ups after a call
get_opportunity_analysisAggregated analysis across deal meetings
get_rep_contextPer-rep coaching context
get_style_guideOrg’s writing/voice style guide
list_metricsCurrent scoring metrics
list_metric_groupsMetric group configuration
list_practice_scriptsSearch practice scripts
get_practice_scriptFull script details
get_analysis_configCurrent analysis methodology
list_tasks / get_task / get_task_statusBrowse and inspect tasks
list_task_runsPer-task execution history
check_statusProcessing status for a meeting or datasource

Write Operations

ToolDescription
create_accountCreate a company record (optionally sync to CRM)
update_accountModify account details
create_opportunityCreate a deal (optionally sync to CRM)
update_opportunityModify deal details
change_opportunity_stageAdvance or change deal stage
update_meetingModify meeting metadata
sync_meetingRe-sync a meeting from its source
sync_workspaceRefresh local workspace state
run_analysisTrigger AI analysis on a meeting
update_deal_memoryAppend to a deal’s persistent memory
upload_fileUpload a recording or context document
upload_deal_fileAttach a file to a deal
upload_folderBulk upload a folder
add_note_to_opportunityLog a CRM note on a deal
add_task_to_opportunityCreate a CRM task on a deal
add_note_to_accountLog a CRM note on an account
add_task_to_accountCreate a CRM task on an account
sync_account_to_crmPush account to HubSpot/Salesforce
sync_opportunity_to_crmPush deal to HubSpot/Salesforce
create_task / update_task / dismiss_task / execute_taskManage and run tasks
propose_taskPropose a task for user approval
propose_email_draft / update_draft_email_paramsDraft outbound emails
send_slack_messagePost to a connected Slack channel
slack_config_statusInspect the Slack integration status
create_practice_script / update_practice_scriptManage roleplay scenarios
generate_practice_scriptAuto-generate script from a meeting
share_practice_scriptShare a script with teammates
create_metric / bulk_create_metrics / create_metric_groupDefine scoring metrics
update_metric_group / delete_metric_groupManage metric groups
update_analysis_configUpdate analysis methodology
apply_playbook_updatesApply playbook revisions
promote_chat_outputPromote a chat-generated artifact to a deal
switch_orgSwitch the active organization
preview_entity_update / preview_entity_deleteDry-run a write before applying
deleteRemove an account, deal, or meeting

Troubleshooting

Verify your API key is valid and hasn’t expired by running an MCP initialize handshake directly against the SSE endpoint:
curl -sS -X POST https://app.ampup.ai/mcp/sse \
  -H "Authorization: Bearer sk-a79-YOUR_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"smoke","version":"1"}}}'
A healthy server returns serverInfo.name = "sales-meeting-analysis" and a protocolVersion string. A 401 indicates a bad/expired key; 5xx indicates the server itself is unhealthy.
After updating the config, restart Claude Desktop or reload Claude Code (/mcp command). The server registers tools on connection — they should appear within a few seconds.
If using claude.ai with OAuth, check that write tools are enabled in Settings → Connected Apps → AmpUp. API key connections have full access by default.

Support