Use Vincia in your AI client

Vincia exposes a public MCP server at https://mcp.vincia.io. Add it to your LLM client and 31 contributor tools appear in your chat — scaffold, build, preview, simulate, lint, AND publish your contribution to the marketplace, all without leaving the conversation. Sign in once via the connector's OAuth flow and your contributor identity is cached client-side.

One-click add

Pick your client. The buttons below open your client's connector flow with the URL pre-filled. If your browser doesn't handle the deep link, use the copy-button below and paste manually.

  • Claude Desktop

    Free tier — smoothest path. Click to open the connector flow.

    Add Vincia →
  • Cursor

    Click to install via Cursor's MCP deep link.

    Add Vincia →
  • Windsurf

    Click to add the Vincia MCP server.

    Add Vincia →
  • VS Code Copilot Chat

    Click to install via VS Code's mcp:install handler.

    Add Vincia →
  • Claude.ai (web)

    Pro+ plan required.

    Settings → Connectors → Add custom connector → paste the MCP URL.

  • ChatGPT (web)

    Plus+ plan + Developer mode required.

    Settings → Apps → Advanced settings → Developer mode ON → Create app → paste the MCP URL, set Auth to "No Auth".

https://mcp.vincia.io

What you get

The public surface exposes 38 tools from Vincia's contributor MCP and 8 docs resources covering the contributor platform end-to-end. As of G-S93 the loop is fully chat-first end-to-end: scaffold → build → preview → simulate → publish → see install counts, earnings, review queue, and what to build next, all without leaving the conversation. The CLI remains available for power users who prefer it.

Catalog & lookup

Validation

Webhook testing (chat-first)

Analytics & discovery (new in G-S93)

Mutate & ship (G-S91)

Scaffold, build & preview (G-S90)

Preview-call boundary: bundle bytes are accepted as base64 in the MCP tool arg, capped at 5 MiB raw. Oversize calls return BUNDLE_TOO_LARGE at the wrapper, not at the backend. Outbound calls from preview-mode connectors stay rejected with PREVIEW_MODE — same boundary as the stdio path.

Studio-owner draft tier (new in G-S95)

Studio users (app owners and editors) can branch a draft, make changes via chat against the draft instead of live, preview the draft at a sandbox URL, then atomically publish — or discard. Available on the studio-owner surface at mcp.studio.vincia.io (separate vst_ Bearer; the same vst_ OAuth scope covers both live and draft tools, no re-auth needed).

Onboarding prompts

Six guided prompts (audit, scaffold, simulate, lint, search, publish) walk an LLM through a first contribution — useful as self-directed onboarding inside any client.

Docs resources

The MCP resources/list exposes 8 docs sections at vincia://docs/<slug>: preview map, sandbox previews, simulations, webhook inboxes, CLI reference, MCP tools, auth + rate limits, troubleshooting. Ask the LLM and it pulls the relevant section automatically.

The CLI is still available for power users

As of G-S91, every contributor action — including publish, version bumps, scope edits, and metadata edits — works from chat. The CLI remains an option if you prefer working from a terminal or have a large bundle (>5 MiB raw) that doesn't fit in an MCP tool argument:

curl -fsSL https://get.vincia.io/install | bash
vincia login            # one-time, saves a contributor token
vincia publish ./path   # mutates the marketplace

Bundles up to 5 MiB raw go inline through the chat-first path; larger bundles fall back to the CLI for now (the upload-token path that lifts this cap is queued for a future release).

If your LLM client caches the tools/list response per session, disconnect + reconnect the connector after a server upgrade to pick up new tools (the 4 mutating tools appear after upgrading to a G-S91+ server).

Try these prompts

  1. Browse the catalog

    Use the Vincia connector. List the SDK capabilities, then find me three payment-connector examples.

  2. Validate a manifest

    Lint this connector manifest against Vincia's v1.0 contract: {paste your manifest.json here}.

  3. Look up the rules

    What are the per-tier resource caps in Vincia? Show me T1 specifically.

  4. Test a webhook handler (chat-first)

    Create a webhook inbox labelled 'stripe-test'. I'll paste the URL into Stripe's dashboard. When events arrive, convert one into a vincia simulate fixture so I can replay it.

  5. Build + preview a widget end-to-end (new in G-S90)

    Scaffold a T3 widget called 'tip-jar' that shows a 'Buy us a coffee' button. Build the bundle in chat, then render a preview at sandbox.vincia.io using vincia_render_widget_preview and give me the URL.

  6. Preview a blueprint (chat-first)

    Here is a T0 blueprint manifest with one collection and one workflow: {paste blueprint.json}. Use vincia_render_blueprint_preview to host it at sandbox.vincia.io and give me the admin_url so I can poke at it.

  7. Publish a connector — full chat-first loop (new in G-S91)

    Scaffold a T1 Stripe payments connector called 'stripe-checkout'. Once the code looks good, render a sandbox simulation with vincia_render_simulation to confirm it works against the mock Stripe fixture. Then call vincia_publish with the manifest and the built bundle to ship it to the marketplace. Show me the marketplace_url when done.

  8. Ship a bug fix without opening a terminal

    I just fixed the retry logic in my 'connector-acme' contribution. Use vincia_bump_version with bump='patch' and changelog='Fix retry loop on 429 responses' to publish the fix. Confirm the new version_id and whether reviewers will need to re-check it.

  9. Edit marketplace metadata in chat

    The description for my 'connector-acme' has a typo. Use vincia_edit_metadata to update the description to 'A Stripe-style payments connector with idempotent retry semantics.' Confirm that no new version was created (this should be a metadata-only edit).

  10. How are my contributions doing? (new in G-S93)

    Use vincia_get_my_contributions to list everything I've published. Then for my top earner call vincia_get_contribution_stats with window=90d and tell me whether it's growing or declining. Finally call vincia_get_my_earnings with breakdown_by=tier and summarise the mix.

  11. What should I build next? (new in G-S93)

    I want to find an under-served opportunity. Call vincia_list_underserved_capabilities (tier T1 only) and vincia_get_marketplace_trends in parallel, then suggest 2 specific contributions I should build based on the demand/supply ratio AND what would compose well with my existing portfolio (which you can fetch via vincia_get_my_contributions). Give me MRR estimates and a quick scaffold plan.

  12. Where is my submission in the review queue? (new in G-S93)

    Call vincia_get_review_status with slug='connector-acme'. Tell me my queue position, the ETA, and whether it's in_review yet. The ETA is an estimate based on rolling 7-day median review time — surface that nuance, do not promise a precise hour.

Subscription tiers (heads-up, not a block)

Server status

Liveness: https://mcp.vincia.io/health. Anonymous per-IP rate limits: 60 read-only tool calls per minute, 5 heavy calls per hour. Limits emit as tool-result envelopes (not HTTP 503) so your client renders them inline.