Control mysaas.blog with AI

Public read

Tools prefixed with public_ require no token. They only return published posts, public profiles, public comments, tags and categories visible on the site.

Authentication

Private actions use OAuth authorization code + PKCE or a personal agent key. In ChatGPT, the host starts OAuth and keeps the token; the user never pastes a bearer token into the conversation. Scopes separate reading, drafts, media, publishing, comments, SaaS and integrations. OpenAI reviewer access is created and revoked from Admin → Reviewers; Infisical remains reserved for server secrets.

MCP tools

ChatGPT facade

The dedicated /mcp/chatgpt facade exposes 27 tools for profile, editorial preferences, SaaS, category, tag, source, comment and integration coverage as well as writing, review, translation, media import and post lifecycle control. It exposes five importable skills (manage-posts, manage-saas, manage-profile-and-editorial-preferences, manage-community-and-integrations and analytics) covering the seven historical workflows through the MCP skills extension. The workflow accepts fr, en or both in one draft: post_translate prepares a non-persistent proposal, then media, structured sources, tags, categories and SaaS relations are validated before saving and explicit publication. Structured sources are not duplicated as a body bibliography; contextual source citations and SaaS mentions use tracked bindings.

REST API

The full REST contract is machine-readable: every endpoint documents parameters, JSON or multipart bodies, responses, errors and scopes. publication modes now and schedule require posts:publish in addition to posts:write.

Rich post

An agentic post is not raw Markdown. It contains translations, sanitized editor HTML, an SEO image, sources, tags, category, linked SaaS and a publication mode.

{
  "translations": [{
    "locale": "fr",
    "title": "Build log",
    "excerpt": "Résumé SEO",
    "contentHtml": "<h2>...</h2>",
    "seoImage": { "mode": "manual", "mediaId": "cm..." }
  }],
  "tags": ["pricing", "seo"],
  "sources": [{ "url": "https://example.com", "label": "Source" }],
  "relatedSaasIds": ["cm..."],
  "publication": { "mode": "draft" }
}

Responses and retries

REST uses the ok/data/meta envelope and clients read resources from data. MCP exposes the direct structuredContent declared by outputSchema; it is not wrapped in the REST contract. The MCP endpoint serves 2026-07-28 only and has no 2025 fallback.

REST
{
  "ok": true,
  "data": { "post": { "id": "cm..." } },
  "meta": { "scopes": ["posts:read", "posts:write"] }
}

MCP tools/call
{
  "result": {
    "structuredContent": {
      "ok": true,
      "post": { "id": "cm..." },
      "meta": { "idempotency": { "key": "draft-2026-08-01-a", "replayed": false } }
    }
  }
}

Drafts

Drafts are listed with status=draft or status=all, or includeDrafts=true. These views require posts:drafts:read. A mistaken draft can be archived with posts:delete.

GET /api/v1/posts?status=draft
GET /api/v1/posts?status=all
DELETE /api/v1/posts/{id}

Media flow

Import or upload an image, read media.id, then reference mediaId in seoImage or data-media-id inside editor HTML. The server resolves the canonical media URL and preserves omitted SEO metadata in a translation patch.

POST /api/v1/media/import
{ "url": "https://example.com/hero.png" }

{
  "translations": [{
    "seoImage": { "mode": "manual", "mediaId": "cm_media_123" },
    "contentHtml": "<img src=\"https://...\" data-media-id=\"cm_media_123\" alt=\"...\" />"
  }]
}

Permissions

Public content can be read without a key. Write actions require OAuth or an agent key with the matching scopes. Deletion uses posts:delete, disabled by default when a key is created; it archives the post, removes it from public surfaces and releases its slugs.