Affise MCP server › Other clients
The Affise MCP server implements the open Model Context Protocol, so anything that speaks MCP can use it. This page covers the generic remote config, static bearer tokens for automation, and the local stdio install.
Before you start
Any MCP-capable client. For the local server, Node.js 18 or newer.
{
"mcpServers": {
"affise": {
"type": "http",
"url": "https://mcp.affise.com/mcp"
}
}
}Clients that support OAuth will prompt you to sign in on first use.{
"mcpServers": {
"affise": {
"type": "http",
"url": "https://mcp.affise.com/mcp",
"headers": {
"Authorization": "Bearer <your-token>"
}
}
}
}Static tokens are a self-hosted feature — set REMOTE_MCP_TOKEN on your own deployment. The hosted endpoint is OAuth-only.npm install -g @affise/mcp-server export AFFISE_API_KEY="your-api-key" export AFFISE_BASE_URL="https://api.affise.com" affise-mcp-serverThen point your client at the
affise-mcp-server command with "type": "stdio".401 and an OAuth discovery document at /.well-known/oauth-protected-resource.Ask your client for your offer categories. A healthy connection returns the list configured on your Affise account.
mcp-remote.Authorization header. Check the header name and the Bearer prefix.429 response carries a ratelimit-reset header with the seconds left in the current window.Once you are connected, these are good first questions. See more examples or the full tool reference.