MCP
MCP
Meridian Ads from Yelle Software exposes advertiser and publisher console actions as a hosted MCP. Cursor and other MCP clients sign in with the same Logto account used in the console.
https://mcp.meridianads.tech/mcpConnect
Point the MCP client at the Streamable HTTP endpoint. The client discovers OAuth from the MCP origin and opens a browser to Logto. Do not paste a Logto client secret into Cursor.
{
"mcpServers": {
"meridian-ads": {
"url": "https://mcp.meridianads.tech/mcp"
}
}
}OAuth
MCP is a Logto confidential-app BFF. Cursor registers with MCP (RFC 7591), MCP redirects to Logto, then MCP stores encrypted Logto refresh tokens and issues its own access token. Tool calls attach the user JWT to https://api.meridianads.tech/api/v1. Tenant binding stays the verified Logto sub. MCP never treats X-Organization-Id as a tenant key.
Tools
Apps, placements, SDK keys, campaigns, creatives (including submit and asset upload), segments, credits, auto-reload, payouts status, Connect session URL, Checkout URL, and reporting. Campaign CPM and budgets are USD in tool arguments and micro-USD on the API. Checkout and Connect return a URL. Finish payment and bank onboarding in the browser.
prepare_publisher_integration finds or creates an app and placement, then returns a language-specific SDK snippet. It does not issue an SDK key. Open the app in the console, issue a production key, and save the public prefix and one-time secret in environment variables.