> ## 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.
# MCP Server
> Reference for the AmpUp MCP server — endpoint, transport, and the full tool catalog
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](/integrations/claude-mcp) 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 (endpoint, transport, full tool catalog).
## 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://.ampup.ai/mcp`.
## Config-file setup (API key)
Clients that connect via a config file with a long-lived bearer token (no OAuth) use:
```json theme={null}
{
"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](/security/mcp-oauth) for the full auth model.
## 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
| Tool | Description |
| --------------------------------------------- | ---------------------------------------------------------------------- |
| `get_my_name` | Current user's display name (and email-fallback hint for voice agents) |
| `get_org` | Current org with workspace summary |
| `list_orgs` | All orgs the API key can access |
| `get_workspace_status` | Local workspace sync state (last sync, entity counts) |
| `list_accounts` | Search and browse accounts |
| `get_account` | Full account details |
| `list_opportunities` | Search and filter deals |
| `get_opportunity` | Deal details with optional context |
| `get_deal_context` | Aggregated deal context for prompts |
| `get_deal_memory` | Persistent deal memory store |
| `list_deal_files` | Files attached to a deal |
| `list_meetings` | Search meetings by status, date, account, or deal |
| `get_meeting` | Meeting overview and analysis |
| `get_meeting_transcript` | Full verbatim transcript |
| `get_transcript_excerpt` | Transcript slice by time range or chapter |
| `list_meeting_analyses` | Analyses run on a meeting |
| `get_pre_meeting_brief` | Preparation context before a call |
| `get_post_meeting_brief` | Outcomes and follow-ups after a call |
| `get_opportunity_analysis` | Aggregated analysis across deal meetings |
| `get_rep_context` | Per-rep coaching context |
| `get_style_guide` | Org's writing/voice style guide |
| `list_metrics` | Current scoring metrics |
| `list_metric_groups` | Metric group configuration |
| `list_practice_scripts` | Search practice scripts |
| `get_practice_script` | Full script details |
| `get_analysis_config` | Current analysis methodology |
| `list_tasks` / `get_task` / `get_task_status` | Browse and inspect tasks |
| `list_task_runs` | Per-task execution history |
| `check_status` | Processing status for a meeting or datasource |
### Write Operations
| Tool | Description |
| --------------------------------------------------------------- | ------------------------------------------------ |
| `create_account` | Create a company record (optionally sync to CRM) |
| `update_account` | Modify account details |
| `create_opportunity` | Create a deal (optionally sync to CRM) |
| `update_opportunity` | Modify deal details |
| `change_opportunity_stage` | Advance or change deal stage |
| `update_meeting` | Modify meeting metadata |
| `sync_meeting` | Re-sync a meeting from its source |
| `sync_workspace` | Refresh local workspace state |
| `run_analysis` | Trigger AI analysis on a meeting |
| `update_deal_memory` | Append to a deal's persistent memory |
| `upload_file` | Upload a recording or context document |
| `upload_deal_file` | Attach a file to a deal |
| `upload_folder` | Bulk upload a folder |
| `add_note_to_opportunity` | Log a CRM note on a deal |
| `add_task_to_opportunity` | Create a CRM task on a deal |
| `add_note_to_account` | Log a CRM note on an account |
| `add_task_to_account` | Create a CRM task on an account |
| `sync_account_to_crm` | Push account to HubSpot/Salesforce |
| `sync_opportunity_to_crm` | Push deal to HubSpot/Salesforce |
| `create_task` / `update_task` / `dismiss_task` / `execute_task` | Manage and run tasks |
| `propose_task` | Propose a task for user approval |
| `propose_email_draft` / `update_draft_email_params` | Draft outbound emails |
| `send_slack_message` | Post to a connected Slack channel |
| `slack_config_status` | Inspect the Slack integration status |
| `create_practice_script` / `update_practice_script` | Manage roleplay scenarios |
| `generate_practice_script` | Auto-generate script from a meeting |
| `share_practice_script` | Share a script with teammates |
| `create_metric` / `bulk_create_metrics` / `create_metric_group` | Define scoring metrics |
| `update_metric_group` / `delete_metric_group` | Manage metric groups |
| `update_analysis_config` | Update analysis methodology |
| `apply_playbook_updates` | Apply playbook revisions |
| `promote_chat_output` | Promote a chat-generated artifact to a deal |
| `switch_org` | Switch the active organization |
| `preview_entity_update` / `preview_entity_delete` | Dry-run a write before applying |
| `delete` | Remove 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 endpoint:
```bash theme={null}
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.
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 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:** [support@ampup.ai](mailto:support@ampup.ai)
* **Contact:** [ampup.ai/contact](https://www.ampup.ai/contact)