docs · with your agent · v0

Vinktar with v0.

v0 adds MCP servers from the + menu in the prompt form, and offers OAuth as one of four authentication types. Vinktar’s MCP server is a standard Streamable HTTP server with OAuth 2.1 sign-in, so it is added the way v0’s docs describe for any custom server. No key is pasted anywhere.

Add the server to v0

The steps are the ones in v0’s documentation, with Vinktar’s values filled in.

  1. 1

    Open the + menu in the prompt form and select MCPs.

  2. 2

    Add a server with the address below. Of the four authentication types v0 lists, No Auth, Custom Headers, Bearer Token and OAuth, pick OAuth.

    https://mcp.vinktar.com/mcp
  3. 3

    Your browser opens Vinktar. Pick the workspace, optionally one project, and read or read and write, then approve.

The consent screen grants one workspace, optionally one project, and either read or read and write. Setting Vinktar up needs read and write, because the agent fetches the project’s write key and defines the events it adds. Reading analytics and errors needs only read.

Then ask it

The agent reads the tool list itself. Setting a project up is never counted against the monthly allowance; the questions after it are.

set it up

Ask it to install Vinktar. It calls get_install_guide for the SDK and the layout, get_project_keys for the write key, defines each event it adds with define_event, and checks what actually arrived with get_setup_status. The guide says which environment variable to set; put it where your app’s variables live.

Set up Vinktar in this app: call get_install_guide on the Vinktar MCP server and follow it.

read it back

Once events arrive, whats_changed is the overview, list_issues and get_issue are the errors with their stack traces, and get_setup_status reports an event that was defined but never sent.

  • What changed in this project since yesterday?
  • Which errors hit the most people this week? Open the worst one and tell me where it breaks.
  • Is anything in the tracking plan defined but never sent?

Every tool, what it costs, and the full list of what to ask are on connect your agent. Every call lands on the project’s AI agents page as it is made.

What v0’s docs say

Costs on v0’s side

v0’s docs say enabling remote MCP for an integration may increase per-message costs, and that it gives v0 access to tools that read or change external data. Vinktar charges nothing per call; the monthly agent allowance is in the plan table.

The generation cannot call the tools

v0’s docs say the generation it creates cannot use the MCP tools directly; they are there while v0 works on your prompt. The app sends its events and errors through the SDK the agent installs, with the project’s write key, and the MCP connection is how the agent reads back what arrived.

Checked

v0’s documentation at https://v0.app/docs/MCP was read on 2026-10-05, and the labels above are the ones it uses. A live run inside v0’s agent has not been done yet. This page says what that documentation says a custom OAuth MCP server can do there, and what Vinktar’s server is; it does not say the two were tried together. When they have been, this line will say so.