Use Akarso from Claude, Cursor, and any MCP client

Akarso exposes every CLI command as an MCP tool, so AI agents can publish posts, check account health, and reply to comments across 14 social platforms. There are two ways to connect: the remote server at https://akarso.co/mcp (OAuth, zero install) or the local stdio server bundled with the CLI.

  MCP client (claude.ai, Claude Code, Cursor, ChatGPT)
        │
        ├──────────> https://akarso.co/mcp ────> OAuth sign-in with Google, no install
        │                                        tools run against your Akarso account
        │
        └──────────> akarso mcp (stdio) ───────> uses your local CLI login
                                                 supports media upload from local files

Ask AI about this page

Remote server (recommended)

Add the server URL to any MCP client that supports streamable HTTP:

1https://akarso.co/mcp

The first request returns a 401 that points your client at the OAuth flow: it self-registers, opens a browser window, and you sign in with Google. No API keys to copy around.

In Claude Code:

1claude mcp add --transport http akarso https://akarso.co/mcp

In claude.ai or ChatGPT, add a custom connector with the URL above and complete the sign-in popup.

The remote server uses OAuth 2.1 with dynamic client registration, the standard MCP authorization flow. Tokens refresh automatically; revoke access anytime from the dashboard.

API key auth for CI and scripts

Headless environments can skip OAuth and send an API key directly:

123456789{
  "mcpServers": {
    "akarso": {
      "type": "http",
      "url": "https://akarso.co/mcp",
      "headers": { "Authorization": "Bearer ak_your_key_here" }
    }
  }
}

Local stdio server

If you already use the Akarso CLI, the same binary doubles as an MCP server over stdio. It reuses your akarso auth login credentials and additionally exposes media upload for files on your machine:

1akarso mcp

Install it into any client with one command:

12npx @playwriter/install-mcp 'akarso mcp' --client claude-code
npx @playwriter/install-mcp 'akarso mcp' --client cursor

On the remote server, media tools accept https URLs only — local file paths are rejected since the server cannot read your machine. Use the local stdio server when your agent needs to upload files from disk.

Available tools

Every tool maps 1:1 to a CLI command and shares its input schema. Browse the sidebar for per-tool parameter docs, or start with the most used ones:

Tool	What it does
`posts_create`	Create, schedule, or publish a post across platforms
`posts_list`	List posts, filterable by status
`accounts_list`	List connected social accounts
`accounts_health`	Check connection health for all accounts
`accounts_set-channel`	Pick the publishing target for a connected account
`accounts_disconnect`	Disconnect a platform account
`media_upload`	Upload media, returns an upload ID for posts
`inbox_sync`	Import the comments on a published post
`inbox_comments`	List imported comments
`inbox_reply`	Publish a reply in a post comment section
`inbox_comment-action`	Moderate an imported comment (hide, delete, like, ...)
`inbox_reviews-sync`	Import Google Business reviews

Agent skill

Agents work best with the MCP server and the Akarso skill installed. The skill teaches coding agents the CLI workflows, output format, and gotchas:

1npx skills add https://akarso.co

Security model

Each OAuth token or API key is scoped to your account only. Tool calls run through the same authenticated API as the CLI, with the same ownership checks: an agent can never see or touch another user's accounts, posts, or comments.