writefreely-mcp-server

A Model Context Protocol (MCP) server that connects AI agents to WriteFreely/Write.as, providing tools to authenticate and to publish, edit, delete, and read posts/collections, as well as browse public feeds.

Evaluated Apr 04, 2026 (17d ago)

Homepage ↗ Repo ↗ Cms mcp writefreely write-as blogging content-management ai-agents python

⚙ Agent Friendliness

/ 100

Can an agent use this?

🔒 Security

/ 100

Is it safe for agents?

⚡ Reliability

/ 100

Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality

Documentation

Error Messages

Auth Simplicity

Rate Limits

🔒 Security

TLS Enforcement

Auth Strength

Scope Granularity

Dep. Hygiene

Secret Handling

Assumes HTTPS endpoints for Write.as by default (WRITEFREELY_BASE_URL). The README indicates an access token is supplied via environment variable, but does not describe how secrets are logged, how token storage/rotation is handled, or whether scopes/permissions are minimized. Dependency hygiene is unknown beyond listing common libraries.

⚡ Reliability

Uptime/SLA

Version Stability

Breaking Changes

Error Recovery

Best When

You want an agent-friendly MCP tool layer to interact with Write.as or a self-hosted WriteFreely instance and you can supply an access token via environment variables.

Avoid When

You require documented rate limits, strong idempotency guarantees for write operations, or you cannot safely handle and store access tokens.

Use Cases

• Letting an AI agent publish and manage blog posts on WriteFreely
• Automating content workflows (drafting/editing/publishing) against Write.as or self-hosted instances
• Reading and summarizing posts/feeds for downstream AI applications

Not For

• High-assurance or compliance-critical publishing workflows without additional review/guardrails
• Use cases requiring first-class moderation/approval flows (not described)
• Teams needing a fully documented REST/SDK interface beyond MCP

Interface

REST API

GraphQL

gRPC

MCP Server

Yes

SDK

Webhooks

Authentication

Methods: Access token via WRITEFREELY_ACCESS_TOKEN environment variable (implied by configuration) login() tool using username/password (implied by available tool list)

OAuth: No Scopes: No

Authentication is token-based for the MCP server runtime (env var). A login() tool also appears to support username/password authentication; the README does not describe scope granularity or refresh/rotation behavior.

Pricing

Free tier: No

Requires CC: No

The package itself is MIT licensed (open-source). Any usage costs depend on the Write.as/self-hosted target, not described here.

Agent Metadata

Pagination

none

Idempotent

False

Retry Guidance

Not documented

Known Gotchas

⚠ Write operations (publish/edit/delete) may not be idempotent; agents may create duplicates if retries occur.
⚠ Authentication must be provided to the MCP server process via env vars (or via login tool); missing/invalid tokens will prevent write actions.
⚠ No explicit rate-limit documentation is provided in the README, so agents may hit throttling without backoff guidance.

Alternatives

Direct calls to the WriteFreely API from your application (HTTP client) Use an MCP server that provides generic blogging CMS operations (if available) or a write-focused integration you already run Build a lightweight MCP wrapper around the WriteFreely REST API

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for writefreely-mcp-server.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

API endpoint ↗ Agent guide ↗ Report inaccuracy

Scores are editorial opinions as of 2026-04-04.