Skip to main content
Glama
fopost

@fopost/mcp

Official
by fopost

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
FOPOST_API_KEYYesYour FoPost API key
FOPOST_API_URLNoBase URL for the FoPost APIhttps://api.fopost.com

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

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
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

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.9/5.0

Scored across 14 tools

Disambiguation4/5

Post lifecycle tools are clearly distinct: schedule_post creates, edit_post updates, cancel_post cancels, delete_post removes. The AI tools have some overlap, but generate_caption, rewrite_for_platforms, and repurpose_url are differentiated by input and output scope.

Naming Consistency5/5

Tool names consistently follow a snake_case verb_noun pattern: list_posts, get_post, schedule_post, edit_post, delete_post, list_accounts. Minor multi-word names like list_post_deliveries and rewrite_for_platforms still fit the overall convention.

Tool Count5/5

14 tools is well-scoped for a social media scheduling and AI content assistant. Each tool covers a distinct operation across posts, accounts, workspaces, and AI generation without feeling bloated.

Completeness4/5

Posts have full lifecycle coverage: create/schedule, read, update, cancel, delete, list, and delivery tracking. Minor gaps exist around account connection/disconnection and workspace management, but the core scheduling workflow is complete.

Maintenance

ActivityMaintained
ResponsivenessNo issues