Mailchimp
The Mailchimp enables tools and to call Mailchimp Marketing APIs on behalf of a using OAuth 2.0 authentication.
Want to quickly get started with Mailchimp in your or AI app? The pre-built Arcade Mailchimp Marketing MCP Server is what you want!
What’s documented here
This page describes how to use and configure Mailchimp auth with Arcade.
This is used by:
- The Arcade Mailchimp Marketing MCP Server, which provides pre-built for interacting with Mailchimp
- Your app code that needs to call the Mailchimp API
- Or, your custom tools that need to call the Mailchimp API
Configuring Mailchimp auth
When using your own app credentials, make sure you configure your to use a custom user verifier. Without this, your end-users will not be able to use your app or in production.
In a production environment, you will most likely want to use your own Mailchimp app credentials. This way, your will see your application’s name requesting permission.
Before showing how to configure your Mailchimp app credentials, let’s go through the steps to create a Mailchimp app.
Create a Mailchimp app
To integrate with Mailchimp’s API, you’ll need to register an OAuth application:
Log into your Mailchimp account
- Navigate to mailchimp.com and log in to your
- Go to > Extras > Registered Apps
- Alternatively, you can directly access the Registered Apps page
Register a new OAuth application
- Click on Register an App
- Fill in the required details:
- Application Name: Choose a descriptive name for your application
- Company/Organization: Enter your company or organization name
- Website URL: Your application’s website URL
- Description: Brief description of your application
- Redirect URI: Add the redirect URL generated by Arcade (see configuration section below)
- This is the URL where Mailchimp will redirect after authorization
- For development, you can use
http://localhost:9099/oauth/callbackor your Arcade instance URL
Save your credentials
- After registration, you’ll receive your Client ID and Client Secret
- Important: Copy and save these credentials immediately in a secure location
- You can always view your Client ID later, but the Client Secret should be stored securely
For detailed instructions, refer to Mailchimp’s OAuth 2.0 documentation and API documentation .
Next, add the Mailchimp app to Arcade.
Configuring your own Mailchimp Auth Provider in Arcade
Dashboard GUI
Configure Mailchimp Auth Using the Arcade Dashboard GUI
Access the Arcade Dashboard
To access the Arcade Cloud dashboard, go to api.arcade.dev/dashboard . If you are self-hosting, by default the dashboard will be available at http://localhost:9099/dashboard . Adjust the host and port number to match your environment.
Navigate to the OAuth Providers page
- Under the OAuth section of the Arcade Dashboard left-side menu, click Providers.
- Click Add OAuth Provider in the top right corner.
- Select the OAuth 2.0 tab at the top.
Enter the provider details
- Choose a unique ID for your provider (e.g. “arcade-mailchimp”).
- Optionally enter a Description.
- Enter the Client ID and Client Secret from your Mailchimp app.
- Configure the OAuth 2.0 endpoints:
- Authorization URL:
https://login.mailchimp.com/oauth2/authorize - Token URL:
https://login.mailchimp.com/oauth2/token
- Authorization URL:
- Note the Redirect URL generated by Arcade. This must be set as your Mailchimp app’s Redirect URI.
Create the provider
Hit the Create button and the provider will be ready to be used.
When you use tools that require Mailchimp auth using your Arcade credentials, Arcade will automatically use this Mailchimp OAuth provider. If you have multiple Mailchimp providers, see using multiple auth providers of the same type for more information.
Using Mailchimp auth in app code
Use the Mailchimp in your own and AI apps to get a token for the Mailchimp API. See authorizing agents with Arcade to understand how this works.
Use client.auth.start() to get a token for the Mailchimp API:
Python
from arcadepy import Arcade
client = Arcade() # Automatically finds the `ARCADE_API_KEY` env variable
user_id = "{arcade_user_id}"
# Start the authorization process
auth_response = client.auth.start(
user_id=user_id,
provider="arcade-mailchimp"
)
if auth_response.status != "completed":
print("Please complete the authorization challenge in your browser:")
print(auth_response.url)
# Wait for the authorization to complete
auth_response = client.auth.wait_for_completion(auth_response)
token = auth_response.context.token
# Do something interesting with the token...Getting the API endpoint
Mailchimp requires you to determine the correct API endpoint for each . After obtaining the access token, make a request to the metadata endpoint:
Python
import httpx
# Get the user's API endpoint
async with httpx.AsyncClient() as client:
metadata_response = await client.get(
"https://login.mailchimp.com/oauth2/metadata",
headers={"Authorization": f"Bearer {token}"}
)
metadata = metadata_response.json()
api_endpoint = metadata["api_endpoint"]
# Now use the api_endpoint for all API calls
# Example: f"{api_endpoint}/3.0/lists"Using Mailchimp auth in custom tools
You can use the pre-built Arcade Mailchimp Marketing MCP Server to quickly build and AI apps that interact with Mailchimp.
If the pre-built tools in the Mailchimp Server don’t meet your needs, you can author your own custom tools that interact with the Mailchimp API.
Use the OAuth2() auth class to specify that a requires authorization with Mailchimp. The context.authorization.token field will be automatically populated with the ’s Mailchimp token:
from typing import Annotated
import httpx
from arcade_tdk import ToolContext, tool
from arcade_tdk.auth import OAuth2
@tool(
requires_auth=OAuth2(provider_id="arcade-mailchimp")
)
async def get_mailchimp_lists(
context: ToolContext,
) -> Annotated[dict, "The user's Mailchimp lists."]:
"""
Retrieve all mailing lists from the authenticated user's Mailchimp account.
"""
# First, get the API endpoint for this user
async with httpx.AsyncClient() as client:
metadata_response = await client.get(
"https://login.mailchimp.com/oauth2/metadata",
headers={"Authorization": f"Bearer {context.authorization.token}"}
)
api_endpoint = metadata_response.json()["api_endpoint"]
# Now get the lists
response = await client.get(
f"{api_endpoint}/3.0/lists",
headers={"Authorization": f"Bearer {context.authorization.token}"}
)
response.raise_for_status()
return dict(response.json())Important: Mailchimp access tokens do not expire unless the revokes access. However, it’s good practice to handle potential errors gracefully and provide users with options to re-authenticate if necessary.
For more details about Mailchimp’s authentication, refer to the Mailchimp OAuth 2.0 documentation .