Other clients

Advibly is a standard Streamable HTTP MCP server with OAuth, so any compliant client works. The two pieces of information every client needs:

OpenClaw

openclaw mcp set advibly '{"url":"https://advibly.com/mcp","transport":"streamable-http","auth":"oauth"}'
openclaw mcp login advibly

Hermes and others

Point the client at the URL and let it run the OAuth flow. If your client supports dynamic client registration - most do - there is nothing to configure beyond the URL.

The connection is complete when tools/list includes advibly_list_brands and calling it returns the signed-in account's brands. Use advibly_check_credits as the second read-only verification call.

Writing your own client

The endpoint speaks the current MCP specification over Streamable HTTP and is stateless, so it works with standard SDK clients without special handling. Discovery starts at /.well-known/mcp.json.

The client must preserve the OAuth token, send it as a bearer token, and accept the tool schemas returned by tools/list rather than hard-coding arguments. Generation calls may return either a completed result or a pending generation_id; see Generation statuses.

If you would rather not write a client at all, the advibly CLI is one: it logs in through the same chain and turns tools/list into subcommands.