Model Context Protocol (MCP)
Connect Claude Desktop, Cursor IDE, Windsurf, and LLM coding assistants directly to ESER AI multi-platform publishing tools via standard open protocols.
Let an AI client discover ESER tools instead of hard-coding every screen.
MCP is a standard way for a compatible AI client to discover tools and call them with structured inputs. ESER uses it to expose authenticated content and publishing workflows while your accounts, drafts and delivery state remain in the ESER workspace.
Example conversation
Illustrative interaction. The client decides how tool approval is presented; ESER validates credentials and provider readiness.
Connect securely, then test a non-destructive action.
Create credentials
Sign in and generate an API key from the API Dashboard.
Configure the client
Add the ESER MCP endpoint and authorization header to your compatible client.
Discover tools
Restart or reconnect the client so it can load the ESER tool definitions.
Review before publish
Begin with discovery or draft preparation; confirm account and provider status before publishing.
Authentication basics
Treat an ESER API key like a password. Store it in the client’s secret configuration, rotate it if exposed, and never include it in screenshots or a public repository.
MCP or REST?
Use MCP when an AI client should discover and call tools. Use REST when your application controls the workflow directly and needs predictable HTTP requests.
Provider readiness
An MCP tool contract does not override external platform approval. ESER labels the concrete live connector and routes that require connection or provider activation.
{
"mcpServers": {
"eser-ai": {
"url": "https://app.eserai.tech/mcp",
"headers": {
"Authorization": "Bearer eser_sk_YOUR_KEY"
}
}
}
}Ready to give your agent a governed social workflow?
Create an account, generate credentials in the API Dashboard, and follow the guide for your AI client.