Skip to main content
Glama
owlstacks

OwlStack MCP

Official
by owlstacks
README.md
# @owlstackapp/mcp

MCP server for [OwlStack](https://owlstack.app) — manage social media posts, accounts, and AI usage from any MCP-aware client (Claude Desktop, Cursor, ChatGPT desktop, Continue, etc.).

Runs via `npx -y @owlstackapp/mcp`, no install step. Requires Node 18 or newer.

> **0.x release.** Tool names and arguments may still change between minor
> versions. Pin an exact version if that matters to you.

## Tools

| Tool                    | What it does                                                |
| ----------------------- | ----------------------------------------------------------- |
| `list_posts`            | List posts in a workspace, filter by status                 |
| `get_post`              | Fetch a post by id                                          |
| `schedule_post`         | Create a post (draft, scheduled, or publish-now)            |
| `edit_post`             | Update an existing post                                     |
| `cancel_post`           | Cancel a scheduled post                                     |
| `delete_post`           | Permanently delete a post                                   |
| `list_post_deliveries`  | Per-account delivery status for a post                      |
| `list_accounts`         | List connected social accounts                              |
| `get_account_health`    | Check token freshness and rate-limit headroom               |
| `list_workspaces`       | List workspaces the user can access                         |
| `generate_caption`      | AI-generate or improve a caption (1 credit)                 |
| `rewrite_for_platforms` | Rewrite content per target platform (1 credit each)         |
| `repurpose_url`         | Turn a blog URL into N platform-optimized posts (6 credits) |
| `get_ai_credits`        | Show current AI credit balance                              |

## Setup

### 1. Get an API key

Generate one at <https://app.owlstack.app/api-keys> with the scopes you need (`posts`, `accounts`, `workspaces` are most common).

### 2. Add to your MCP client

#### Claude Desktop

Edit `~/Library/Application Support/Claude/claude_desktop_config.json` (macOS) or `%APPDATA%\Claude\claude_desktop_config.json` (Windows):

```json
{
  "mcpServers": {
    "owlstack": {
      "command": "npx",
      "args": ["-y", "@owlstackapp/mcp"],
      "env": {
        "OWLSTACK_API_KEY": "your-api-key"
      }
    }
  }
}
```

#### Cursor / Continue / Other

Use the same `npx -y @owlstackapp/mcp` command with `OWLSTACK_API_KEY` in the environment.

## Configuration

| Variable           | Required | Default                    |
| ------------------ | -------- | -------------------------- |
| `OWLSTACK_API_KEY` | yes      | —                          |
| `OWLSTACK_API_URL` | no       | `https://api.owlstack.app` |

Self-hosted? Point `OWLSTACK_API_URL` at your instance.

## Example prompts

> "List my failed posts from this week and tell me which accounts are unhealthy."

> "Take this URL and turn it into a Twitter thread, a LinkedIn post, and a dev.to summary: https://example.com/blog/post"

> "How many AI credits do I have left this period?"

## Contributing

Issues and pull requests are welcome at
[owlstacks/owlstack-mcp](https://github.com/owlstacks/owlstack-mcp).

```bash
npm install
npm run lint     # tsc --noEmit
npm run build    # tsup -> dist/
```

## License

MIT

TDQS

A4/5.0

Scored across 14 tools

Disambiguation5/5

Each tool targets a distinct resource and action. Post operations are split clearly (get, list, schedule, edit, cancel, delete, delivery), account tools are separate, and AI tools have distinct purposes (caption generation, platform rewriting, URL repurposing). The minimal overlap between get_post and list_post_deliveries is acceptable since the latter provides per-account detail.

Naming Consistency5/5

All tools follow a consistent verb_noun snake_case pattern (e.g., list_posts, schedule_post, get_account_health). Even multi-word actions like repurpose_url and rewrite_for_platforms maintain the structure. No mixing of casing or verb styles.

Tool Count5/5

14 tools is well within the ideal range and each tool earns its place. The count covers post CRUD, delivery, accounts, workspaces, and AI features without feeling bloated or sparse for the domain.

Completeness4/5

The core content scheduling lifecycle is fully covered: create, read, update, cancel, delete, and track delivery. Account management is read-only plus health checks, which is sufficient for the stated purpose. Minor gaps like no single-workspace getter or account update tool exist, but they are not critical for typical workflows.

Maintenance

ActivityMaintained
ResponsivenessSyncing