Other clients
Avada AI Blog Builder works with any assistant that speaks MCP over Streamable HTTP and can send an Authorization header.
Set it up
Create an access token
On the MCP page, in the Access tokens card, click Create token, name it after the client you're setting up, and copy the token. It is shown only once — see Access tokens for the full walkthrough.
Copy your endpoint
Scroll to Setup guide and copy the MCP endpoint:
https://…/mcpAdd it as a remote MCP server
In your client, add it wherever remote or HTTP MCP servers go. Name it something you'll recognise, such as avada-blog, and set the authorization header:
Authorization: Bearer YOUR_TOKENReplace YOUR_TOKEN with the token you created.
Check it worked
Restart the client and ask it something only your store would know, such as "how many posts does my blog have?"
What the server needs from your client
| Transport | MCP over Streamable HTTP |
| Authentication | An Authorization: Bearer … header on every request |
| Endpoint | The same URL for everyone — the token is what identifies your store |
A client that only speaks stdio, or that cannot set a request header, cannot connect.
Tell us what you use
Don't see your client covered? On the MCP page, open Setup guide, choose the Other clients tab and click Contact us — it opens support with your client's name so we can look at adding a guide for it.
Trouble connecting? See Troubleshooting.