# Vinktar

Vinktar hands your coding agent error data paired with what the user did right before each crash. It answers questions like what broke after the latest deploy.

- MCP server · `type=mcp` · Claude Code, Codex, Cursor, GitHub Copilot, Windsurf (Devin Desktop), Cline, Zed, Gemini CLI
- Author: vinktarhq
- License: MIT · policy=link-only · description only; the file stays with the author
- Source: https://github.com/vinktarhq/agent
- Updated: 2026-10-21
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/mcp/vinktar

## What it does

The server gives the agent crash data linked to the user actions that preceded each error. Sign-in happens in the browser, where you pick a workspace and decide which projects the agent can read, build, or configure, so there's no key to paste into a config file.

The `setup` skill inspects the repository, installs the SDK matching the stack, pulls the project's write key over the connection, wires up identify calls, error reporting and source maps, documents every event it tracks, and confirms the data actually showed up. The `/vinktar` command either runs that setup or answers a question directly, such as what broke after the last deploy.

No account is required upfront: the agent can spin up an unclaimed project on its own through `start_project` and send you a claim link afterward. An unclaimed project holds up to 10,000 events and gets deleted with its data after 7 days if nobody claims it. Through MCP the agent can only delete boards and panels, both recoverable for 30 days, and can't delete events, errors, or projects themselves.

## Requirements
- Remote server: `https://mcp.vinktar.com/mcp`

## Install

### Claude Code (native platform)

**Platform CLI: remote server**
```bash
claude mcp add --transport http mcp https://mcp.vinktar.com/mcp
```

### Codex

**Platform CLI: remote server**
```bash
codex mcp add vinktar --url https://mcp.vinktar.com/mcp
```

### Cursor

**Config file**
File `.cursor/mcp.json`:
```json
{
    "mcpServers": {
        "vinktar": {
            "url": "https://mcp.vinktar.com/mcp"
        }
    }
}
```

### GitHub Copilot

**Config file**
File `.vscode/mcp.json`:
```json
{
    "servers": {
        "vinktar": {
            "type": "http",
            "url": "https://mcp.vinktar.com/mcp"
        }
    }
}
```

### Gemini CLI

**Platform CLI: remote server**
```bash
gemini mcp add -t http vinktar https://mcp.vinktar.com/mcp
```

## When to use it
- wire up error tracking in an unfamiliar stack without reading SDK docs by hand
- ask the agent what broke after a deploy or release
- spin up an error-tracking project before creating an account
- confirm an identify call or error actually reached the server
- list every environment variable the tracking setup needs

## Example prompts
- /vinktar:setup
- Set up Vinktar in this repo
- /vinktar what broke after the last deploy?

## Similar
- [sentry-debug-issue](https://affpapa.org/en/nevibecode/skills/sentry-debug-issue.md) — skill · 2200 installs
- [instrument-error-tracking](https://affpapa.org/en/nevibecode/skills/instrument-error-tracking.md) — skill · 546 installs
- [triaging-error-issues](https://affpapa.org/en/nevibecode/skills/triaging-error-issues.md) — skill · 361 installs
- [OpenFault](https://affpapa.org/en/nevibecode/mcp/openfault.md) — MCP server · ★ 8 repo stars
- [Talaria](https://affpapa.org/en/nevibecode/mcp/talaria.md) — MCP server
- [LogBrew](https://affpapa.org/en/nevibecode/mcp/logbrew.md) — MCP server

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
