Archive

UGC and creator insights

Archive helps teams search workspace social content and creators, inspect campaigns, saved views, collections, operations, and webhooks, and manage those workspace records through your AI.

What you can ask

Search for creators in this workspace and show the top 3 by follower count, with their recent posts.
Example path →

MCP connector

Server URL: https://app.archive.com/api/v2/mcp
Login: OAuth
Protocol: MCP 2026-07-28
Instructions: Archive's workspace-scoped social-content API. Call getWorkspaces first to list the workspaces these credentials can access. Every other tool operates on ONE workspace, resolved per call in this order: 1) an explicit workspaceId tool argument, 2) the WORKSPACE-ID HTTP header, 3) automatic default when exactly one workspace is accessible. With none of those (multiple accessible workspaces, no selection) the call returns an error listing your accessible workspaces - pass workspaceId to choose one. Argument casing: every enumerated tool argument is camelCase (e.g. itemId, presetId, collectionId, viewIds), matching the /api/v2 GraphQL field names 1:1; a rejected unexpected-field error names the correct key when a stale snake_case name was sent. Exception: stored keys inside the opaque saved-view filters blob stay snake_case - clone them verbatim. Write tools: API (bearer) tokens are always write-capable; OAuth tokens can write only when the optional write scope was granted at consent. Without write access, write tools are omitted from tools/list and calling one returns the unknown-tool error. Alpha tools: opt in to the campaign-creator-view tools by sending the X-Archive-Alpha-Features header with campaign_creator_views; without it they are hidden from tools/list and behave as unknown tools. Rate limiting: workspace-scoped calls charge a weighted cost against the workspace's rate-limit bucket (shared with the /api/v2 GraphQL API); getWorkspaces charges a principal-scoped bucket. A throttled call returns isError text: "Rate limit exceeded. Retry after N seconds." - wait, then retry. Write results: userErrors report domain rejections in a SUCCESSFUL result, not a crash. Atomicity is tool-specific; valid changes may apply alongside errors. Inspect each field, message and returned state; verify what applied before retrying rejected work.

Tools

Reads data39

Changes data12

Deletes or can't be undone25

Skills

None in the store listings or on the server

MCP connector

Server URL

https://app.archive.com/api/v2/mcp

OAuth

Protocol

MCP 2026-07-28

Instructions

Archive's workspace-scoped social-content API. Call getWorkspaces first to list the workspaces these credentials can access. Every other tool operates on ONE workspace, resolved per call in this order: 1) an explicit workspaceId tool argument, 2) the WORKSPACE-ID HTTP header, 3) automatic default when exactly one workspace is accessible. With none of those (multiple accessible workspaces, no selection) the call returns an error listing your accessible workspaces - pass workspaceId to choose one. Argument casing: every enumerated tool argument is camelCase (e.g. itemId, presetId, collectionId, viewIds), matching the /api/v2 GraphQL field names 1:1; a rejected unexpected-field error names the correct key when a stale snake_case name was sent. Exception: stored keys inside the opaque saved-view filters blob stay snake_case - clone them verbatim. Write tools: API (bearer) tokens are always write-capable; OAuth tokens can write only when the optional write scope was granted at consent. Without write access, write tools are omitted from tools/list and calling one returns the unknown-tool error. Alpha tools: opt in to the campaign-creator-view tools by sending the X-Archive-Alpha-Features header with campaign_creator_views; without it they are hidden from tools/list and behave as unknown tools. Rate limiting: workspace-scoped calls charge a weighted cost against the workspace's rate-limit bucket (shared with the /api/v2 GraphQL API); getWorkspaces charges a principal-scoped bucket. A throttled call returns isError text: "Rate limit exceeded. Retry after N seconds." - wait, then retry. Write results: userErrors report domain rejections in a SUCCESSFUL result, not a crash. Atomicity is tool-specific; valid changes may apply alongside errors. Inspect each field, message and returned state; verify what applied before retrying rejected work.

Tools