MCP server

Vinktar Official

com.vinktar/mcp

Checked 26 Oct 2026, 08:29 UTC · Connected to it and listed its tools

Error tracking for small teams and their coding agents.

Website Source

At a glance

Type

MCP server

Publisher

vinktar.com (verified by the MCP Registry)

Status

Working at last check

Tools

31

Token cost

About 33,275 tokens per request

Sets up in

Claude Code, Claude Desktop, Codex, Gemini CLI, Cursor, VS Code, Antigravity, ChatGPT, OpenAI API, Grok

Last checked

26 Oct 2026, 08:29 UTC

Connect it to your agent

Add to CursorAdd to VS CodeVS Code Insiders

Opens the app, which shows the server and asks you to confirm. For other apps, copy the setup below.

Claude Code

claude mcp add --transport http vinktar https://mcp.vinktar.com/mcp

Claude Desktop

Settings → Connectors → Add custom connector, and paste the URL.

Codex (config.toml)

[mcp_servers.vinktar]
url = "https://mcp.vinktar.com/mcp"

Gemini CLI

{"mcpServers":{"vinktar":{"httpUrl":"https://mcp.vinktar.com/mcp"}}}

Cursor

{"mcpServers":{"vinktar":{"url":"https://mcp.vinktar.com/mcp"}}}

VS Code

{"servers":{"vinktar":{"type":"http","url":"https://mcp.vinktar.com/mcp"}}}

Antigravity

agy mcp add vinktar https://mcp.vinktar.com/mcp

ChatGPT

Settings → Apps & Connectors → Advanced settings: turn on Developer mode, then Create a connector and paste the URL. Which plans can do this varies.

OpenAI API (Responses tools)

{"type":"mcp","server_label":"vinktar","server_url":"https://mcp.vinktar.com/mcp","require_approval":"always"}

Grok (xAI API tools)

{"type":"mcp","server_label":"vinktar","server_url":"https://mcp.vinktar.com/mcp"}

Tools

• add_panel ~7652 tokens
  Add a panel to a board. Each panel answers one question and reads at a glance: a number, a line or a bar. Build it from the structured types; `sql` is the last resort. Choose in this order: `funnel` for conversion through ordered events (viewed pricing → started checkout → paid), with a breakdown fo
• browse_events Browses the web · ~765 tokens
  Raw events, newest first, under simple filters: event names, one user (distinctId), page search, property filters or a VinktarQL WHERE expression. Use it to see what one user did, or to inspect real payloads. Pass `eventId` instead to get that one event in full, every column and the whole payload. W
• check_fix ~374 tokens
  After a fix for an issue ships, start a server-side check of whether it comes back: occurrences on the fix release (or the next release seen) and later, against how many sessions reached that release, over a horizon of up to 14 days. It keeps running after this session. Read the result later with ge
• create_alert ~1571 tokens
  Create an alert: a query (source events, errors or sql; measure count or unique_users; filters; an optional groupBy; a window in minutes), a condition (above or below a threshold, or changed by a percent against the window before, a week earlier or the trailing week) and who hears it (recipients amo
• create_board ~764 tokens
  Create an empty board in the workspace, to leave the user a view of what you found; fill it with add_panel, where each panel says which projects it reads. First decide what kind of board the request is, from the decision the user wants to make with it: "launch" when one feature or release just shipp
• define_event ~787 tokens
  Define an event in the project's tracking plan: what it means, its role, the properties it carries (type, unit, whether every send must include it, an example) and where the code sends it. Call it in the same step as adding or changing a track() call, before any data arrives; and for existing events
• delete_board Deletes data · ~126 tokens
  Delete a board with its panels. Only when the user asked for it, or agreed when you proposed it; name the board before you do. A person can restore it in Vinktar from the boards page for 30 days.
• delete_panel Deletes data · ~132 tokens
  Remove a panel from its board. Only when the user asked for it, or agreed when you proposed it; say which panel before you do. The panel id is in get_board. A person can restore it in Vinktar from the boards page for 30 days.
• get_alert ~283 tokens
  Read alerts and what they said. Pass alertId for one alert: its query and condition, whether it is on or snoozed, what its last check read per series, who hears it and what it said recently. issueId gives that issue's latest fix check (awaiting_release, watching, recurred, no_recurrence, not_enough_
• get_board ~250 tokens
  Read a board: every panel computed over a window with the change against the previous period, as headline numbers. The quickest way to answer "how are we doing" in the terms the team already tracks. Each panel shows its id, for update_panel and delete_panel.
• get_install_guide ~348 tokens
  The step-by-step guide for setting Vinktar up in the app you are working in: which SDK fits the stack (with current versions), the recommended file layout and environment variables, defining the tracking plan as you add events, proving it with get_setup_status, and the handover telling the person wh
• get_issue ~312 tokens
  Everything needed to debug one error issue: what it is, its status and history, how often and for whom it happens in the window (by release, environment, browser, URL, tag), the latest occurrence's stack trace (source-mapped when available, each in-app frame linking to its file in the repository onc
• get_project_keys ~205 tokens
  The keys installing Vinktar needs: the project's public write key (VINKTAR_KEY) with the ingest host, the Sentry-compatible DSN and the Bugsnag-compatible endpoints, and whether a source-map upload key (VINKTAR_CLI_KEY, a secret) exists, with where a person creates one. The secret is never returned:
• get_schema ~521 tokens
  What a project tracks (or several, with `projects`, each under its own heading): event names with their volume over the last 30 days, the payload properties each event carries, user trait keys, and the columns and functions VinktarQL (run_sql) accepts. Call before any query so names are real. Pass `
• get_setup_status ~206 tokens
  Check a project's Vinktar install from the data that actually arrived: events and errors received, users identified, releases and environments tagged, source maps for the latest release, items the SDK dropped, and key events described. Each gap comes with the next step. Call it after installing, and
• get_start_status ~149 tokens
  Whether events and errors have arrived for a project started with start_project, by its write key, and whether the person has claimed it yet. Call it after installing the SDK and sending a first event. Projects someone already claimed answer only after sign-in, through get_setup_status.
• list_boards ~214 tokens
  The boards whose panels read from a project, or from any of several with `projects`. A board shows what the team already decided matters; read one with get_board.
• list_issue_occurrences ~191 tokens
  Recent individual occurrences of one issue, newest first: when, which user and session, release, environment, page, browser and OS. Use it to spot a pattern (one browser, one release, one customer) or to pick a user or session to follow in browse_events.
• list_issues ~562 tokens
  Error-tracking issues (errors grouped by fingerprint) for a project, or across several with `projects`, with occurrences and affected users inside the window. Default: open issues (unresolved + regressed) sorted by occurrences over the last 14 days. Follow up with get_issue for the stack trace.
• list_projects ~101 tokens
  List the Vinktar projects this connection can read (a project is one app or site sending events and errors), with the workspace plan and what this connection is allowed to do. Call this first when you do not know the project handle.
• query_funnel ~2670 tokens
  Conversion through an ordered sequence of events (e.g. view_pricing → start_checkout → purchase): how many entered, how many reached each step, where they dropped, how long converting took, optionally by segment.
• query_retention ~1432 tokens
  Cohort retention: users who did targetEvent in a period form a cohort, and the table shows what share of each cohort did returningEvent in each later period. Use it for "do people come back" and "did retention improve after the change".
• query_trends ~2862 tokens
  Metrics over time: event counts, unique users or sessions, the sum, average or p95 of a numeric property, optionally split by a property (one breakdown for every series, or each series by its own) and compared to the previous period. The workhorse for "how many / how much / is it growing" questions.
• run_sql ~467 tokens
  Run a read-only VinktarQL SELECT over the project's `events` table, for anything query_trends, query_funnel and query_retention cannot express; start with those, since what they run is what a board panel should be. A ClickHouse-flavoured subset: WHERE, GROUP BY, HAVING, ORDER BY, LIMIT, DISTINCT, IN
• set_project_notes ~243 tokens
  Write the project's notes for AI agents: what the product does and for whom, the flows that matter (signup, activation, the paid action), what counts as an active user, and anything that makes the data easy to misread. Write them from the codebase during setup, in plain sentences, up to 2,000 charac
• start_project ~277 tokens
  Before the person has signed in to Vinktar: start a project for their app now, so setup can run and data can arrive before anyone makes an account. Returns the project's write key (public, safe in browser code) and a claim link that only the person should open: it signs them in, or makes them an acc
• update_alert ~1304 tokens
  Change an alert from get_alert: any part of its query, condition, timing, recipients (workspace members) and channels (saved ids or "#name" in the connected Slack). Or hold its news with snoozeMinutes (0 ends a snooze; a week at most). Switching an alert off or deleting it is a person's, in Vinktar.
• update_board ~601 tokens
  Rename a board, rewrite the line under its title, change when it deletes itself, or lay its panels out. A board is a grid: every row spans the full width, its panels share it (one to four) at one height, equally unless you give widths. Pass `rows` to set the layout outright, top to bottom, as rows o
• update_issue ~381 tokens
  Change an error issue's status or assignee: resolve it (optionally in the release that ships the fix, or in the next release when it has not shipped yet, so a later occurrence reopens it as a regression), ignore it, reopen it, or assign it to a teammate. Only act on an issue when the user asked you
• update_panel ~7204 tokens
  Change a panel on a board: its title, how it draws, its number format or what it shows. Pass only what changes; the rest stays as it is. The panel id is in get_board. To turn it into another type, pass `type` with the full spec for it, the same fields as add_panel. A changed panel is run and held to
• whats_changed ~321 tokens
  Start here. One project's window, or several pooled with `projects` (every row then names its project), compared with the one before it, across analytics and errors: traffic (events, active users, sessions), the events that rose, fell, appeared or stopped, error volume, new, regressed and fastest-gr

Browse

• Sentry tools
• Website monitoring
• Databases
• Errors and monitoring
• Shipping and parcels

Related MCP servers

• GovInbox
  Federal contract opportunities for government contractors. Set-aside coverage is the deepest part.
• ClusterHack
  Run hackathons end to end: events, teams, submissions, judging and winners.
• Lightbringer
  Register innovations, request patent preparation, and collaborate with Lightbringer’s patent team.
• Sparkling Tracks Tours
  Read-only MCP for Sparkling Tracks European tours: packages, itineraries, pricing, contacts.
• Kitfinch
  Business software by trade for US small service businesses, with prices verified at the source.
• Suara
  Social media posts for small businesses from their own photos. Owner approves every post.
• ClickUp MCP by usefulapi
  Read teams, spaces, lists and tasks; create, update and comment on tasks and track time.
• Royaltea Public
  Free no-auth game-dev tools: revenue splits with real store cuts, agreement drafts, studio setup.

Badge for your README

[![AptLynx](https://aptlynx.net/badge/com.vinktar/mcp.svg)](https://aptlynx.net/servers/com.vinktar/mcp)

Listing text is written by the maker; AptLynx lists tools and does not vouch for them. Find another tool · Browse by topic · For agents