MCP Server

The Ayrshare MCP Server lets AI agents drive the Ayrshare API through Model Context Protocol (MCP) tools. Instead of writing REST calls by hand, an agent connects to the MCP Server and calls Ayrshare tools to publish posts, fetch history and analytics, manage comments and direct messages, create profiles, and more.

​

How it works

Each MCP tool call is dispatched in-process through the same Ayrshare API chain that powers the REST API:

• Authentication of your API key.
• Rate limiting for your plan tier.
• Quota and usage enforcement.
• OpenAPI request validation.
• The same controllers that serve the REST endpoints.

Because tools run through the real API chain, the MCP Server returns the same data and enforces the same rules as the REST API. There is no separate behavior to learn or maintain.

​

Who it’s for

• Agent builders connecting an LLM agent to the Ayrshare API to publish and analyze content.
• Claude Code users who want to post, fetch history, and manage profiles from their editor (see the Claude Code Plugin).
• Integrators onboarding clients’ social accounts under sub-profiles (see Client Onboarding).

​

Endpoint and transport

The production MCP Server is available at: https://api.ayrshare.com/mcp It uses Streamable HTTP transport and is stateless — there is no session to maintain between calls. See Connect & Setup for the full connection and authentication details.

​

Relationship to the REST API and Documentation MCP

• REST API — the Ayrshare API is the underlying interface. The MCP Server dispatches each tool call through that same API chain, so behavior, rules, and data match.
• Documentation MCP — the separate Documentation MCP is a read-only server that searches Ayrshare’s API documentation. It does not perform actions. Use the MCP Server (this page) to actually drive the API.

​

Next steps