SEODrafts

Use SEODrafts from a compatible AI agent.

Inspect projects, opportunities, losslessly ranged posts, revisions, insights, billing, and audit events through a project-allowlisted MCP connection. Make bounded editorial changes with optimistic versions, then separately schedule or approve an exact reviewed version for customer-owned publishing.

The hosted MCP surface exposes 14 read tools and 11 bounded write tools. It exposes no publish tool, provider credential, shell, SQL, or arbitrary-URL capability.

⌕

Read the work

List granted projects, evidence-backed opportunities, complete post metadata and lossless bounded body chunks, revision history, editorial insights, integration health, billing entitlements, and token audit events.

✓

Edit with scoped authority

Update reviewed context or a contrast-checked project hero palette, create one evidence-backed opportunity or review-only post, revise or decline an exact content/state version, separately schedule an approved version, trigger one qualified generation, or approve only with the separate scope and required attestations.

↗

Publish through your stack

Use tenant-side CLI, SDK, Git, CMS, or signed-webhook paths for approved content while provider credentials remain in CI or server-side storage.

What the MCP connection can do

Use a compatible MCP client to inspect and make bounded changes inside explicitly granted projects.

Read tools

get_agent_capabilities, list_projects, get_project, list_posts, get_post, list_post_revisions, list_opportunities, get_opportunity, get_editorial_insights, get_integration_health, get_billing_status, list_agent_audit_events, recommend_publisher_integration, list_publisher_integrations

Write tools

update_project_context, update_project_image_style, create_post_draft, update_post, schedule_post, approve_post, decline_post, restore_post_to_review, check_post_publish_health, create_opportunity, generate_review_draft

Approval is separately scoped

approve_post requires the separately granted posts:approve scope, exact current contentVersion and stateVersion values, the exact editorialResponsibilityVersion discovered from capabilities, and explicit responsibility, claim-verification, original-value, and author-identity attestations. Scheduling is a separate posts:schedule operation. Approval returns an approvalEpoch that binds the later asynchronous publisher handoff; it cannot publish directly.

Race-safe by contract

  • Read contextVersion and send it as expectedContextVersion with the complete contextSourceUrls replacement list.
  • Before every mutation of an existing post and every publication-health check, read and send its current expectedContentVersion and expectedStateVersion.
  • Read editorialResponsibilityVersion from capabilities, attest explicitly, and observe the returned approvalEpoch; approval never grants scheduling authority.
  • Customer-owned asynchronous publishers must bind contentVersion, stateVersion, and approvalEpoch so stale attempts cannot overwrite newer editorial state.
  • MCP exposes no direct publish-now tool. A separately scoped approval binds exact contentVersion and stateVersion values and returns an approvalEpoch for the later customer-owned publisher handoff; scheduling remains separately scoped.
  • MCP exposes no shell, SQL, arbitrary-URL fetch, bulk page factory, or provider-credential tool.
  • CMS, Git, webhook, and publish credentials stay in tenant CI, encrypted server-side storage, or a tenant-owned secret store; they never enter MCP tool arguments.
  • Hosted MCP currently requires a configured, expiring, revocable Bearer token with an exact project allowlist. SEODrafts does not advertise a one-click OAuth connection.
  • Agent access and publishing do not guarantee indexing, rankings, traffic, backlinks, or AI citations.

Choose the interface that matches the job

Tenant CLI

Use the published package for project-allowlisted agent workflows, secure token management, tenant-side setup, and customer-owned publishing. Check its --help output before relying on a newly released command.

View published package

TypeScript SDK

Use the typed Agent API client for all scoped project, post, opportunity, insight, integration, billing, and audit operations, or build a customer-owned publisher without exposing tokens to browser code.

View published package

Give your agent the public contract.

Start with the machine-readable capability catalog or the tenant integration skill. Check the currently published CLI help before relying on any newly released package command.

Open capability catalog Read the agent skill

Agent access FAQ

Can an MCP client publish a post immediately?

MCP exposes no direct publish-now tool. A separately scoped approval binds exact contentVersion and stateVersion values and returns an approvalEpoch for the later customer-owned publisher handoff; scheduling remains separately scoped.

How does hosted MCP authenticate?

Configure a revocable, expiring sda_live_ agent token with explicit tool scopes and project grants in a compatible MCP client. Hosted MCP currently requires a configured, expiring, revocable Bearer token with an exact project allowlist. SEODrafts does not advertise a one-click OAuth connection.

Where do publishing credentials live?

CMS, Git, webhook, and publish credentials stay in tenant CI, encrypted server-side storage, or a tenant-owned secret store; they never enter MCP tool arguments.

When should I use the TypeScript SDK?

Use the typed Agent API client for all scoped project, post, opportunity, insight, integration, billing, and audit operations, or build a customer-owned publisher without exposing tokens to browser code.