[ MCP SERVER SUMMARY ]
Antom MCP server summary
Connect your AI Agents to Antom Checkout Payment. Connect Antom through Bifrost MCP Gateway to centralize access control, virtual keys, and tool-call observability for your AI assistants.
| Property | Details |
|---|---|
| Company | Upstream maintainer |
| Connection type | Confirm upstream transport |
| Authentication | Varies by upstream server |
| Package or endpoint | See upstream documentation |
| Capabilities | Antom tools over MCP, AI assistant connectivity, Governed tool access through Bifrost |
| Official documentation | Antom MCP documentation |
Before you start
- Review the Antom upstream documentation for its installation requirements
- Obtain any credentials required by the upstream service
- A running Bifrost MCP Gateway instance
What you can do with Antom
- Connect your AI Agents to Antom Checkout Payment.
- Expose Antom tools to Claude, Cursor, and other MCP clients through one endpoint
- Apply virtual keys, tool allowlists, and audit logging at the gateway
[ HOW TO CONNECT ]
Connect Antom to Bifrost in three steps
Install Bifrost
Start the gateway locally or deploy in your VPC.
npx -y @maximhq/bifrost
Add Antom in MCP Gateway
Open MCP Gateway in the Bifrost dashboard, click New MCP Server, and select the transport documented by the upstream server. Or register via the API below.
• Confirm the transport, command or endpoint, and authentication requirements in the Antom upstream documentation.
• Replace every placeholder in the example before sending the request.
Point clients at Bifrost /mcp
Configure Claude Desktop, Cursor, or Claude Code to use your Bifrost endpoint with a virtual key instead of connecting directly to Antom.
{
"mcpServers": {
"bifrost": {
"url": "http://localhost:8080/mcp",
"headers": {
"Authorization": "Bearer vk_your_virtual_key"
}
}
}
}[ EXAMPLE CONFIG ]
Register Antom via API
Add this MCP client with a POST to /api/mcp/client. See Connecting to MCP Servers for full options.
# For a remote HTTP or SSE server:
curl -X POST http://localhost:8080/api/mcp/client \
-H "Content-Type: application/json" \
-d '{
"name": "antom",
"connection_type": "<http|sse>",
"connection_string": "<upstream MCP endpoint>",
"tools_to_execute": ["*"]
}'
# For a local STDIO server:
curl -X POST http://localhost:8080/api/mcp/client \
-H "Content-Type: application/json" \
-d '{
"name": "antom",
"connection_type": "stdio",
"stdio_config": {
"command": "<upstream command>",
"args": ["<arg>"]
},
"tools_to_execute": ["*"]
}'[ WHY BIFROST ]
Run Antom through one governed gateway
Access control
Virtual keys, RBAC, and tool allowlists per team or agent.
Cost governance
Attribute MCP tool spend alongside LLM usage in one view.
Observability
Log every tool call with latency, server, and virtual key metadata.
Credential isolation
Upstream secrets stay in the gateway — not on every laptop.
[ FAQ ]
Common questions
What does the Antom MCP server do?
Connect your AI Agents to Antom Checkout Payment. The exact tools available depend on the upstream server version and configuration.
How do I connect Antom to Bifrost?
Check the upstream documentation to determine whether Antom uses STDIO, Streamable HTTP, or SSE. Then add it as an MCP client in Bifrost using the corresponding command or endpoint.
Does Bifrost replace the Antom MCP server?
No. Bifrost connects to Antom as an upstream MCP client and adds a governed gateway between that server and your AI assistants.
[ RELATED SERVERS ]
More MCP integrations
Alpaca
Connect AI agents to Alpaca’s stock trading and financial market data APIs through an MCP server.
AlphaVantage
Connect to 100+ APIs for financial market data, including stock prices, fundamentals, and more from AlphaVantage
Amplitude
The Amplitude MCP server enables seamless integration between AI assistants and your product data, allowing you to search, analyze, and query charts, dashboards, experiments, feature flags, and metrics directly from your AI interface.