OwlStack MCP
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OWLSTACK_API_KEY | Yes | Your OwlStack API key. Generate one at https://app.owlstack.app/api-keys with the scopes you need. | |
| OWLSTACK_API_URL | No | Base URL for the OwlStack API. Configure if self-hosting. | https://api.owlstack.app |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_postsA | List posts in a workspace. Filter by status (draft, scheduled, published, failed) and pagination. Returns content, scheduled time, target accounts, and delivery status. |
| get_postA | Fetch a single post by id with full content, settings, and delivery records. |
| schedule_postA | Create and schedule a post. Pass the body text, target account ids, and an ISO 8601 schedule_at. Omit schedule_at to save as draft. Use publish_now=true to publish immediately after creation. |
| edit_postA | Update an existing post. Only provided fields are changed. |
| cancel_postA | Cancel a scheduled post. The post stays in the system but will not be published. |
| delete_postA | Permanently delete a post. Cannot be undone. |
| list_post_deliveriesB | Show per-account delivery status (queued, publishing, published, failed) for a post. |
| list_accountsA | List connected social accounts in a workspace. Returns platform, username, primary flag, and connection status. |
| get_account_healthA | Check token freshness and rate-limit headroom for a single account. Useful when posts are failing — tells you if the OAuth token has expired. |
| list_workspacesA | List workspaces the authenticated user has access to. |
| generate_captionA | Generate or improve a social media caption with AI. Optionally pass current draft text and target platforms for tone-aware output. Costs 1 AI credit. |
| rewrite_for_platformsB | Rewrite a piece of content for one or more target platforms, applying platform-specific tone and length constraints. Costs 1 AI credit per platform. |
| repurpose_urlA | Fetch a blog/article URL and generate one optimized post per requested platform in a single call. The flagship "Developer Content Stack" feature — write once, get 16 versions. Costs 6 AI credits per call regardless of platform count. |
| get_ai_creditsA | Show the current AI credit balance, usage this period, and reset date. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 14 tools
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.
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.
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.
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.