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 (endpoint, transport, full tool catalog).
Endpoint & transport
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: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 viatools/list.
Read Operations
Write Operations
Troubleshooting
Connection refused or timeout
Connection refused or timeout
Verify your API key is valid and hasn’t expired by running an MCP A healthy server returns
initialize handshake directly against the endpoint: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
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
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: support@ampup.ai
- Contact: ampup.ai/contact