MCP and AI assistants

Connect an MCP-compatible assistant to read content, review exact revisions, and propose changes.

PeopleTide Content · HTTP integration guides

Configure a Streamable HTTP connection.

Set your MCP client’s remote server URL to https://content.peopletide.com/mcp and configure Authorization: Bearer YOUR_AGENT_KEY using its private credential settings. Client configuration syntax varies; use a client that supports authenticated Streamable HTTP. This endpoint accepts POST, not an SSE GET connection.

Read schemas before writing.

Use get_schemas, list_content, read_content_batch, and get_references to understand the site. Search and inventory are discovery tools, not a stable full-library review.

Review a pinned snapshot.

Call create_review_snapshot, paginate read_review_snapshot using its id, offset, and limit, then call mark_reviewed with the exact content IDs and revisions examined. Finish all pages before claiming complete coverage.

Submit a proposal for a person to review.

Use propose_changeset with expected revisions, followed by validate_changeset. Include the snapshotId for a snapshot-based review. A publisher opens the proposal in the workspace to approve or reject; no MCP publication-approval tool is available.

Handle expiry and conflicts.

Use one site-specific key per assistant, keep it out of prompts and browser bundles, and rotate it before expiry. On a revision conflict, read the changed content and prepare a fresh proposal. Revoked keys fail subsequent calls.