MCP Server

Reference for the AmpUp MCP server — endpoint, transport, and current tool surface

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.

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.

Setting up a client? The MCP integration guide has copy-paste setup for Claude Code, Claude.ai, Claude Desktop, Codex, and Cursor — most via OAuth, no API key. This page is the technical reference for the endpoint, transport, and current tool surface.

Building a GTM workflow or warehouse pull? Start with the GTM Engineer Quickstart for direct API requests, server-side examples, safe write patterns, and five end-to-end journeys.

Endpoint & transport

Setting	Value
URL	https://app.ampup.ai/mcp
Transport	Streamable HTTP (recommended)
Legacy transport	SSE at https://app.ampup.ai/mcp/sse
Auth	OAuth 2.1, or Authorization: Bearer sk-a79-YOUR_API_KEY
Protocol version	2025-03-26
Server	sales-meeting-analysis (FastMCP 3.x)

Prefer streamable HTTP (/mcp) for new integrations. The SSE endpoint (/mcp/sse) remains for backwards compatibility, but streamable HTTP is more robust behind a multi-replica deployment.

If your org has a dedicated subdomain (e.g. acme.ampup.ai), the endpoint is also exposed at https://<your-org>.ampup.ai/mcp.

Config-file setup (API key)

Clients that connect via a config file with a long-lived bearer token (no OAuth) use:

{
  "mcpServers": {
    "ampup": {
      "url": "https://app.ampup.ai/mcp",
      "headers": {
        "Authorization": "Bearer sk-a79-YOUR_API_KEY"
      }
    }
  }
}

Generate a key at Settings → API Keys in the AmpUp dashboard. Keys inherit the role and permissions of the user who created them and can be revoked at any time. See MCP Server Authentication for the full auth model.

Available Tools

The catalog is dynamic. A fully enabled workspace currently advertises up to 147 tools, while each client sees only the tools allowed by the user’s role, workspace configuration, and enabled products. Treat the response from MCP tools/list as the source of truth for your connection.

AmpUp consolidates related operations into workflow-oriented tools instead of mirroring every REST endpoint. The tables below highlight the current public surface; your AI assistant receives the complete descriptions and parameter schemas automatically through tools/list.

Read Operations

Tool	Description
get_workspace_overview	Current profile, organization, credit balance, and integration summary
list_organizations	Organizations available to the authenticated user
list_integrations	Connected workspace integrations and their status
list_accounts	Search and browse accounts
get_account	Full account details
list_deals	Search and filter deals
get_deal	Deal details, related tasks, and optional context
list_contacts / get_contact	Search contacts and inspect a contact record
list_meetings	Search meetings by status, date, account, or deal
get_meeting	Meeting overview with optional analysis, briefs, participants, and deal state
get_transcript	Full meeting transcript
get_analysis_config	Current analysis methodology
list_evaluation_metrics	Scoring metrics and metric-group configuration
list_tasks / get_task / get_task_feed	Browse tasks and review the current task feed
list_roleplays / get_roleplay	Browse roleplay scenarios and inspect their configuration
get_roleplay_session	Read a completed or in-progress roleplay session
list_courses / get_course	Browse learning courses and course content
list_campaigns / get_campaign	Browse prospecting campaigns and their configuration
get_campaign_analytics	Campaign performance and delivery analytics
list_conversations / get_conversation	Browse outbound conversations and replies
list_senders	Connected email and LinkedIn senders
list_audiences	Saved prospecting audiences
get_icp	Current ideal-customer profile

Write and Workflow Operations

Tool	Description
upsert_accounts / upsert_deals / upsert_contacts	Create or update CRM entities in batches
sync_to_crm	Push supported local records to the connected CRM
analyze_meetings	Run analysis for one or more meetings
update_meetings / update_meeting_brief	Update meeting metadata and briefs
upload_files	Upload recordings, transcripts, or context files
manage_notetaker	Schedule or manage the AmpUp notetaker
propose_tasks / review_task_suggestions	Draft tasks for human review
upsert_tasks / execute_tasks	Persist approved tasks and execute supported actions
set_icp	Define the workspace ideal-customer profile
search_companies / find_prospects	Discover target accounts and contacts
enrich_contacts / score_icp_fit	Enrich prospects and score ICP fit
save_prospects / save_audience	Save qualified prospects and reusable audiences
create_campaign / update_campaign	Create or update an outreach campaign
generate_sequences / edit_sequence	Generate, review, and edit outreach sequences
launch_campaign	Launch a reviewed campaign
reply_conversation / update_conversation	Reply, hand off, snooze, archive, or update an inbox conversation
connect_sender / disconnect_sender	Connect or remove an outbound sender
create_roleplay / update_roleplay	Create or update roleplay scenarios
assign_roleplay / assign_course	Assign coaching with durable due dates and learner targeting
upsert_evaluation_metrics	Create or update scoring metrics and groups
update_analysis_config	Update analysis methodology
select_organization	Change the active organization for the MCP session
send_channel_message	Send a message through a connected workspace channel

Troubleshooting

Connection refused or timeout

Verify your API key is valid and hasn’t expired by running an MCP initialize handshake directly against the endpoint:

curl -sS -X POST https://app.ampup.ai/mcp \
  -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.

Tools not appearing in Claude

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.

Permission denied on write operations

If connecting with OAuth, check that write tools are enabled in your client’s AmpUp connector settings. API key connections have full access by default.

Support

• Email: [e-mail]
• Contact: ampup.ai/contact