Vuti remote MCP server

What this server exposes

• Read-only discovery via search, fetch, search_web, fetch_url, extract_source, whoami, list_workspaces, get_workspace_overview, get_brand_voice, what_worked, list_posts, get_next_post, get_post, get_post_assets, list_library_assets, get_brand_kit_context, list_catalog_items, list_inspiration_items, and get_inspiration_item.
• Admin-only read-only operating tools for Vuti leadership: get_vuti_business_snapshot, get_vuti_product_analytics, list_vuti_admin_workspaces, list_vuti_admin_users, get_vuti_nia_usage, get_vuti_mcp_adoption, and get_vuti_waitlist_summary. These require the connected Vuti user email to be present in ADMIN_EMAILS.
• Workflow mutations via create_post, create_posts, create_plan, update_post, reschedule_post, set_post_status, generate_post_images, generate_post_video, cancel_video_generation_job, select_post_image, use_library_asset, run_photoshoot, save_catalog_item, save_inspiration_item, save_inspiration_brief, and update_inspiration_status.
• generate_post_images and generate_post_video accept an optional slot_id. Omit it to generate directly into the reusable Asset Library without creating a post or calendar slot.
• Use create_post for one fresh platform-specific draft, create_posts for coordinated multi-platform drafts, create_plan for a generated planning batch, update_post to revise an existing slot, and set_post_status only when changing approval or publishing queue state.
• To create a LinkedIn document carousel, find a saved PDF, PPT, PPTX, DOC, or DOCX with list_library_assets, then pass its asset_id to create_post. Use asset_alt_text for the document title.
• Use list_inspiration_items before drafting from saved inspiration, get_inspiration_item for full source context, and save_inspiration_item for low-friction capture. Rebuild ideas in the user's own voice instead of closely paraphrasing the source.
• Use list_catalog_items before drafting product, service, offer, or campaign-specific content. Use save_catalog_item only when the user supplies durable business facts to remember.
• Use whoami, get_workspace_overview, get_brand_voice, and what_worked before planning or drafting so agents start from workspace identity, brand voice, workflow context, and available performance signals.
• Use search_web, fetch_url, and extract_source for public web research before source-backed planning or drafting. Returned public web ids use web:<encoded_url> and can also be passed to fetch.
• get_brand_kit_context exposes safe Brand Kit guidance: colors, avoid rules, logo assets, voice, visual direction, image/layout rules, and approved examples.
• Operational checks are available at /mcp/health.
• Tool failures return a structured JSON error envelope with a stable code, retryability, user-facing message, and optional suggested next tool.
• Media uploads from chat are limited by MCP client support. Prefer saved library assets with list_library_assets, create_post.asset_id, and use_library_asset; use source_data_url for photoshoots only when the client can forward image bytes.
• scheduled_for can be a target time before a post is truly queued. Only status=scheduled or queue_state=queued means a post is actually queued for publishing.
• OAuth 2.1 with dynamic client registration at the app root. Protected resource metadata is published automatically for /mcp.

Connection details

{
  "mcp_url": "https://www.app.vuti.io/mcp",
  "agent_onboarding_url": "https://www.app.vuti.io/agents",
  "authorization_endpoint": "https://www.app.vuti.io/authorize",
  "token_endpoint": "https://www.app.vuti.io/token",
  "register_endpoint": "https://www.app.vuti.io/register",
  "protected_resource_metadata": "https://www.app.vuti.io/.well-known/oauth-protected-resource/mcp"
}

First test prompt

After connecting, ask the client: Use Vuti to run whoami, then tell me which workspace is active and what I should do next if no workspace is active.

A healthy connection returns your Vuti user, one active workspace or a list of accessible workspaces, and guidance about whether future tool calls need workspace_id.

Environment

• MCP_PUBLIC_BASE_URL is optional but recommended in production so the metadata and connector URLs resolve to the public host.
• The sign-in step relies on the same Supabase auth configuration Vuti already uses for product login.
• TAVILY_API_KEY enables public web research tools. Without it, private Vuti search/fetch still works but search_web, fetch_url, and extract_source return a configuration error.
• ADMIN_EMAILS controls Vuti-wide admin MCP tools. Keep this list narrow for leadership or internal operator agents.
• Registered OAuth clients, authorization codes, access tokens, and refresh tokens are stored in the database. Authorization codes and tokens are persisted as hashes.
• Authorization, token, session, tool-call, and citation document events are recorded for operational visibility when the database is available.