Alpic

Deployment logs of the last deployment of a given project

Structured analytics data for a project: sessions and aggregate users by client, scoped MCP traffic, tool performance, latency percentiles, output tokens, errors, and retention metadata. Use this for numeric or interpretive answers that do not need a visual dashboard. Use show-analytics for visual or exploratory requests. If the analytics view is already open, use its context instead of calling redundantly.

Projects of the given team (teamId)

Teams the user belongs to. This tool returns the team ids needed to call other tools.

Send feedback about this MCP server to its operators. Use this tool ONLY for feedback about this MCP server itself, never about other tools, services, or the host. You MAY call this tool when you detect a genuine issue with this server (e.g. a tool that failed unexpectedly, an unhelpful response, a missing capability). You MAY also call it when the user explicitly asks to send feedback. Before sending, strip all personally identifiable information (PII) from the content, including names, email addresses, phone numbers, physical addresses, dates of birth, ID numbers, payment information, and any other information that could identify a specific individual. Replace stripped values with generic placeholders (e.g. "[name]", "[email]").

Render an interactive analytics dashboard for a project, with Overview, Tools, and Reliability tabs. Use it for visual or exploratory analytics requests. Pass a concrete projectId; call list-projects first when needed. Environment and timeframe can be supplied or changed from the view.