INDIVIDUAL MCP TOOL

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 endpoints, and whether a source-map upload key (VINKTAR_CLI_KEY, a secret) exists, with where a person creates one.

vinktar.comnone authenticationAvailability not checked

LIVE ENDPOINT

https://mcp.vinktar.com/mcp

No auth detected

Connect to this endpoint to inspect the live schema for get_project_keys and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Potential side effects detected · medium confidence · heuristic, not a guarantee.

A tool name or description contains a write-action term.
A tool name, description or schema mentions credentials.

Parent server

vinktar.com

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

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

Claude Code

.mcp.json

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

Claude Desktop

Settings → Connectors → Add custom connector

Name: vinktar
Remote MCP URL: https://mcp.vinktar.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

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

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

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

Generic MCP

Client-specific MCP configuration

{
  "name": "vinktar",
  "transport": "streamable-http",
  "url": "https://mcp.vinktar.com/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

Related tools

add_panel — Add a panel to a board.
browse_events — Raw events, newest first, under simple filters: event names, one user (distinctId), page search, property filters or a VinktarQL WHERE expression.
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 how many sessions reached that release, over a horizon of up to 14 days.
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 below a threshold, or changed by a percent against the window before, a week earlier or the trailing week) and who hears it (recipients among members, saved channels, the team by default).
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.
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) and where the code sends it.
delete_board — Delete a board with its panels.
delete_panel — Remove a panel from its board.