com.vinktar/mcp

up checked 2026-11-11T05:37:46.701Z

Unclaimed · Unverified

Agent searches it appeared in, last 30 days: 0. Run this server? Claim the listing: verified label, uptime alerts and analytics.

Publisher-provided title

Vinktar

Publisher-provided description

Error tracking for small teams and their coding agents.

Summary by lookupd

Lets an agent read error issues, query events and metrics, manage alerts and dashboards, and track whether fixes hold.

Install

Claude Code, remote (streamable-http)

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

Codex, remote (streamable-http)

codex mcp add mcp --url https://mcp.vinktar.com/mcp

Cursor, remote (streamable-http) → .cursor/mcp.json

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

Other clients: docs. Or tell your agent: Set up lookupd for me: read https://lookupd.com/agent.md and follow it.

Tools (showing 30 of 31)

Publisher-provided text

• add_panel 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
• browse_events 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
• check_fix 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
• create_alert 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
• create_board 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
• define_event 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)
• delete_board 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 Vinkta
• delete_panel 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 p
• get_alert 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
• get_board 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"
• get_install_guide 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 e
• get_issue 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, browse
• get_project_keys 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 endpo
• get_schema 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 eac
• get_setup_status Check a project's Vinktar install from the data that actually arrived: events and errors received, users identified, releases and environments tagged, source ma
• list_boards 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_boar
• list_issue_occurrences 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 (on
• list_issues Error-tracking issues (errors grouped by fingerprint) for a project, or across several with `projects`, with occurrences and affected users inside the window. D
• list_projects 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
• query_funnel Conversion through an ordered sequence of events (e.g. view_pricing → start_checkout → purchase): how many entered, how many reached each step, where they dropp
• query_retention 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. Us
• query_trends 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 ever
• run_sql 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
• set_project_notes 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 acti
• update_alert 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 Sla
• update_board 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 p
• update_issue 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 l
• update_panel 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_
• whats_changed 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 er
• start_project 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

Details

• Version: 1.0.1
• Transports: streamable-http
• Uptime (7 days): 100%
• Median latency: 964 ms
• First indexed: 2026-11-01T08:59:57.102Z
• Last seen in registry: 2026-11-01T08:59:57.112Z
• Repository: https://github.com/vinktarhq/agent
• Website: https://vinktar.com/docs/mcp

Badge for your README

Shows this live status and links here; updates hourly.

[![lookupd status](https://lookupd.com/badge/com.vinktar/mcp.svg)](https://lookupd.com/servers/com.vinktar/mcp)

• 62033 servers
• Last crawl: 2026-11-11T15:38:39.561Z
• API base: https://api.lookupd.com
• MCP URL: https://api.lookupd.com/mcp