Vivreal MCP Server

The Vivreal MCP Server lets AI agents (Claude, Claude Code, and any MCP-compatible client) operate on your Vivreal content the same way you do in the portal: create collections, publish posts, manage sites, view Stripe orders and balance, and more.

It implements the Model Context Protocol — an open standard for connecting LLMs to tools and data — over OAuth 2.1 with PKCE.

Quick Facts

What It Does

Every Vivreal operation is group-scoped. After authenticating, agents call set-active-group to pick a tenant, then issue tool calls against that group's content.

The tool catalog covers the same surface as the portal:

• Collections & content — create content types, CRUD on content items, bulk operations
• Media — presigned uploads, attach/reorder/delete media on objects
• Calendar — list scheduled posts across collections and channels
• Sites — create, deploy, version, redirect, custom domains
• Channels (integrations) — read connected accounts and publish/schedule posts to X / LinkedIn (including Company Pages) / Instagram / Facebook (Pages) / TikTok / Mailchimp; sync from Stripe. Channel setup (OAuth connect, API keys, account activation) is portal-only — the MCP is a posting + reading surface, not a setup surface.
• Stripe — list orders, view balance, subscription info, customer portal (read-only)
• Group management — invite/remove/role members, update company info
• Docs — search and read the Vivreal documentation itself
• Dashboard — pull the same metrics the portal home page shows

See the full tool reference.

When To Use It

The MCP server is the right surface when:

• You want an agent to do the work — drafting and scheduling posts across channels, importing a CSV of products, updating prices in bulk
• You want automation that survives Vivreal API changes — tool schemas stay stable even when underlying REST routes evolve
• You're building inside Claude.ai or Claude Code and want one-click install with OAuth

For traditional server-to-server integration, use the REST API instead — same data, less protocol overhead.

How It's Hosted

Deployed on AWS Lambda + API Gateway behind the mcp.vivreal.io domain. The OAuth dance is brokered: MCP clients see mcp.vivreal.io as the authorization server, and we relay to Cognito under the hood with stable broker callbacks. Random loopback ports, Claude.ai's /api/mcp/auth_callback, and any other compliant redirect URI all work without pre-registration.

Sessions live in DynamoDB with TTL. Tier-based rate limits apply per session.

Next Steps

• Connecting from Claude.ai — Self-serve install in three clicks
• Tool Catalog — Every tool, its scope, and its destructive/read classification
• OAuth & Scopes — Auth flow details and scope semantics
• Troubleshooting — Common errors and how to fix them