Skip to main content
Glama
pranshuguptaa

Wick MCP

by pranshuguptaa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Wick MCP

No user-submitted related servers found.

    Related Servers

    • ai-usage-mcp

      MohitBansal321
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables local-first tracking of AI token usage and costs from Claude Code and OpenCode, answering queries about tokens, models, sessions, and cost through MCP tools and a CLI, with no network calls.
      414 npm
      1
      MIT

    • MCP_ClaudeOps

      skdkfk8758
      F
      license
      Not graded
      quality
      D
      maintenance
      A comprehensive MCP server for monitoring Claude Code sessions, agent performance, cost tracking, project management, and GitHub synchronization with 89 tools and a real-time dashboard.
      -

    • token-meter

      whdrnr2583-cmd
      A
      license
      A
      quality
      A
      maintenance
      Local-first dashboard + MCP server that parses Claude Code and Codex JSONL files into a SQLite cost / token tracker. Per-MCP and per-tool breakdown, session drill-down, dedup by request_id; never talks to vendor APIs
      5
      100 npm
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: track records usage, status shows current session stats, reset clears the counter, export outputs data, and summary provides all-time totals. There is no ambiguity between them as the descriptions are explicitly differentiated.

    Naming Consistency4/5

    All tool names follow a consistent 'wick_' prefix and use lowercase single-word names. However, the second part mixes verbs (track, reset, export) with nouns (status, summary), deviating slightly from a verb_noun pattern, but the overall style is uniform and predictable.

    Tool Count5/5

    With 5 tools, the server is well-scoped for its purpose of token usage tracking. Each tool serves a necessary function without redundancy, and the count is within the ideal 3-15 range.

    Completeness5/5

    The tool set covers the full lifecycle of usage tracking: recording (track), viewing current status (status), resetting sessions (reset), exporting data (export), and summarizing all-time usage (summary). There are no obvious gaps for this domain.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources