MCP server overview
The Warmup MCP server lets AI assistants work with your Warmup account through the Model Context Protocol. Once connected, an agent can manage projects, connect social networks and answer questions about your analytics.
Connection details
Section titled “Connection details”| Server URL | https://mcp.warmup.social/mcp |
| Transport | Streamable HTTP (stateless) |
| Authentication | OAuth 2.1 with dynamic client registration; API token as a fallback |
| Health check | GET https://mcp.warmup.social/health → { "ok": true } |
What the agent can do
Section titled “What the agent can do”- Projects — list, create, update and delete projects.
- Connections — start connecting Facebook, Instagram or Threads to a project and finish choosing a Facebook Page.
- Analytics — key metrics with period-over-period change, network comparison, top posts, best content types and posting times, video length insights and posting regularity — for your own accounts or competitors.
See the full list in Tools.
How it works
Section titled “How it works”The server is a thin layer over the REST API: every tool call becomes an API request made with your access token. The agent sees only your data and can do only what you can do in the dashboard.
When the client connects, the server sends short instructions for the model: where to start (get_analytics_filters for analytics, list_projects for projects), to always mention the period the numbers cover, and to ask you before deleting a project or disconnecting a network.
Safety
Section titled “Safety”Every tool is marked with MCP tool annotations:
- read-only tools (all analytics, listing projects) can run without confirmation;
delete_projectanddisconnectare marked destructive, so clients ask you before running them;start_connection,select_facebook_pageanddisconnecttouch Meta, outside Warmup.
Connecting a network always ends in your browser: the agent gives you a link and you approve access yourself.
You can see and revoke connected apps in the dashboard under MCP.