Cursor
IDE
- Open Settings → MCP or the project file
.cursor/mcp.json. - Paste the config above, replace the key, and reload MCP.
Athenous
MCP · AI tool integration
Connect Athenous over MCP. Claude, Cursor, ChatGPT, and any compatible client can schedule posts, sync analytics, and inspect campaigns—using your existing Connections and API key.
In the AI tool, add that URL and send Authorization: Bearer ath_… with a key from Settings → API keys (Pro+).
Compatible clients
Any MCP-compatible host. Social and ad OAuth stay in Athenous Connections; your assistant calls them through the server.
How it works
Same Client API as the dashboard—exposed to your AI over MCP.
Create a key with REST API scope in Settings → API keys.
In your AI tool, add https://mcp.athenous.io/mcp and the header Authorization: Bearer ath_….
Schedule, publish, sync metrics, and list connectors from the same thread you already work in.
Setup
Same URL and header in every tool. Paste your key where it says ath_xxxxxxxx.
{
"mcpServers": {
"athenous": {
"url": "https://mcp.athenous.io/mcp",
"headers": {
"Authorization": "Bearer ath_xxxxxxxx"
}
}
}
}
.cursor/mcp.json.https://mcp.athenous.io/mcp. Header Authorization: Bearer ath_….claude mcp add --transport http athenous https://mcp.athenous.io/mcp --header "Authorization: Bearer ath_xxxxxxxx"
https://mcp.athenous.io/mcp.Authorization: Bearer ath_….If that screen only offers HTTP Actions, use the REST API with the same key.
Authorization header from the config above.Capabilities
Posts, Campaigns, and Connectors—invoked from conversation instead of the UI.
Draft or schedule across connected networks and set publish time without opening the calendar.
Push live now or leave scheduled—the same publish path the app uses.
Pull post and campaign metrics so the assistant can summarize performance in-thread.
Enumerate destinations before scheduling. OAuth remains in Athenous Connections.
Open paid campaigns beside organic work from a single assistant session.
Pro+ API key and workspace quotas—MCP is a thin layer over the REST Client API.
Examples
Each line is one tool call. The panel is the kind of result Athenous returns.
“Schedule this LinkedIn update for Friday at 14:00 UTC.”
Scheduled on LinkedIn for Friday, 14:00 UTC.
“Which accounts are connected, and what’s scheduled this week?”
3 accounts connected. 4 posts already scheduled this week.
“Sync analytics for that post and summarize engagement.”
Reach 12.4k, 860 reactions, 140 link clicks. Up 18% this week.
“Save this as a draft, then publish it to Instagram now.”
Draft saved, then that post went live on Instagram.
“List my campaigns and open the summer launch.”
Summer launch opened. Active, $4,200 spent.
“Sync analytics for the summer launch and tell me spend versus results.”
$4,200 spent, 18.6k results, about 2.4× return.
FAQ
Create an API key in Settings → API keys. In the AI tool, add https://mcp.athenous.io/mcp and send Authorization: Bearer with that key. Then ask it to list connectors, schedule a post, or sync analytics.
Yes. Pro, Agency, or Enterprise with the REST API scope. Send it as Authorization: Bearer ath_… on https://mcp.athenous.io/mcp. Do not commit the key.
List connectors, create and schedule posts, publish, sync post and campaign analytics, and inspect campaigns—via the same Client API as the dashboard.
Any tool that can add a remote MCP server: Claude, Claude Code, Cursor, ChatGPT, Windsurf, and custom agents.
No. Add https://mcp.athenous.io/mcp in the AI tool and send your API key as Authorization: Bearer ath_….
No. Connect networks in Athenous Connections. Your AI tool uses those connectorId values when it schedules or publishes through MCP.
Need a walkthrough? Book a demo and we’ll configure your first client with you.
Athenous
Issue a key, register the MCP server, and run Posts and Campaigns from the assistant you already use.