MCP server
Claude, ChatGPT, Codex, Cursor, and any other MCP client can call Athenous through the hosted server. The package is not on the public npm registry.
Setup
- Use a Pro, Agency, or Enterprise plan.
- Create a key in Settings → API keys with REST API enabled.
- Connect networks in the app. The server does not run OAuth and does not store network tokens.
Server URL: https://mcp.athenous.io/mcp. Send Authorization: Bearer ath_… on every request. X-Api-Key is also accepted. Health check, with no key: GET https://mcp.athenous.io/health.
Clients
Cursor, in Settings → MCP or in .cursor/mcp.json:
{
"mcpServers": {
"athenous": {
"url": "https://mcp.athenous.io/mcp",
"headers": { "Authorization": "Bearer ath_xxxxxxxx" }
}
}
}
Claude Code:
claude mcp add --transport http athenous https://mcp.athenous.io/mcp \
--header "Authorization: Bearer ath_xxxxxxxx"
Claude, ChatGPT, and Windsurf take the same URL as a remote MCP connector. If the form has a header field, use Authorization: Bearer ath_xxxxxxxx. Product setup is also on athenous.io/mcp-server.
Tools
| Tool | What it does |
|---|---|
whoami | Checks the key and the account. |
list_connectors | Lists connected accounts. Use these ids in schedule_post. |
list_posts, get_post | Browse posts. |
schedule_post | Creates a draft or a scheduled post. Scheduling records an approval, then places the post on the calendar. |
publish_post | Publishes now. |
sync_post_analytics | Pulls channel metrics for one post. |
list_campaigns, get_campaign | Browse campaigns. |
sync_campaign_analytics | Syncs campaign metrics. |
mcp_setup_hint | Returns the API base URL and this tool list. It does not return the key. |
schedule_post needs channelSettings with a connectorId on each channel. A non-blank caption on a channel replaces the shared body for that network. scheduledAt is ISO-8601 UTC.Things to ask
- List my connected accounts.
- Schedule this LinkedIn post for Friday at 14:00 UTC.
- Show scheduled posts.
- Sync metrics for this post id.
- List campaigns and sync analytics for one campaign id.
Publish and sync run with your workspace permissions and plan limits. The same routes are in the API reference if the client cannot use MCP.