Hosted MCP server/Marketing

Axiom Lab MCP server

Hosted at axiomlab.online·Streamable HTTP

Axiom Lab turns PDF pitch decks, PPTX slides, product photos and briefs into QA-checked commercial videos through MCP. The server can list workflows and the fields each video type needs, upload files, create a plan, start production after approval, follow progress and return download links. Every request needs Authorization: Bearer <API key> from https://axiomlab.online/dev; a missing or wrong key returns HTTP 401. The first five videos are HK$1 each and later videos are HK$30 each, with HTTP 402 when the balance is too low. Starting production spends credits and requires an approved plan.

axiomlab.online Streamable HTTP API key (Bearer AZIMO_API_KEY) Server not checked yet Reviewed 2026-11-16
About

Where it fits

Marketing teams that turn decks, slides and product photos into short commercial videos.

  • List the available video workflows and required fields (no charge).
  • Check the account balance before starting a job.
  • Convert a pitch deck into a video after approving the plan and cost.

A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.

Setup

Install it in your client

Choose a client, run the command or use the one-click install, then verify the connection. The endpoint uses Streamable HTTP.

All client guides
  1. 01

    Run this command in your terminal

    This adds Axiom Lab as a remote Streamable HTTP server in Claude Code.

    Claude Code
    claude mcp add --transport http axiom-lab https://axiomlab.online/mcp --header "Authorization: Bearer $AZIMO_API_KEY" --scope project
  2. 02

    Send the credential

    The provider expects the following header. Replace each placeholder with your own key or token before you connect.

    Required headers
    Authorization: Bearer $AZIMO_API_KEY
  3. 03

    Verify the connection

    Run claude mcp list, or open /mcp in a Claude Code session.

    Learn more about MCP in Claude Code

More clients, including project and global config files, are in the sidebar.

Connection

Endpoint and configuration

Endpoint
https://axiomlab.online/mcp
Host
axiomlab.online · /mcp
Transport
Streamable HTTP
Authentication
API key (Bearer AZIMO_API_KEY)
Server name
axiom-lab
Listing type
Community or directory listing

The installer uses the server name axiom-lab. If you add the endpoint by hand, keep the same name so the guide and your config match.

Verification

Check the connection

After you add the server, confirm that the client can see its tools and that one small request returns what the provider describes.

  1. 1
    Open the tool list.

    Restart the client or start a new session. Confirm that axiom-lab appears and that the tools match the provider documentation.

  2. 2
    Run one small request.

    Start with: List the available video workflows and required fields (no charge). Check the result before you give the server more access.

  3. 3
    Check permissions.

    Review the OAuth scopes or API-key permissions, then remove the server and revoke its token when you no longer need it.

Server not checked yet

We checked the provider's page, not the MCP connection itself. No MCP sign-in or tool call was attempted. A provider page is linked but was not included in the automated check. Open it before setup.

Troubleshooting

Common failure modes

These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.

  • Authentication returns 401 or 403. Check the key, its environment variable, and the permissions attached to it.
  • The key works in the provider dashboard but not in the client. Confirm the client sends it in the header the provider expects.
  • Your client does not support Streamable HTTP. Use a client that does, and confirm the provider's current endpoint and transport in its docs.
Safety

Before you connect

Remote means provider access
  • The provider can see the requests and data your agent sends through the server.
  • Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
  • Use project scope for repository-specific servers; use global scope for personal tools.
  • Remove the server and revoke its token when you stop using it.
Review path

Check the connection before a real task

These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.

Reference

Provider documentation

Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.

Axiom Lab documentationhttps://axiomlab.online/developers/cli-mcp