Skip to main content
Glama
BlackFoil

claude-token-saver-mcp

by BlackFoil
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Related Servers

Alternatives to claude-token-saver-mcp

No user-submitted related servers found.

    Related Servers

    • Ollama MCP Server

      Jadael
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables Claude to delegate coding tasks to local Ollama models, reducing API token usage by up to 98.75% while leveraging local compute resources. Supports code generation, review, refactoring, and file analysis with Claude providing oversight and quality assurance.
      330 npm
      24
      AGPL 3.0

    • localagents

      ccebelenski
      A
      license
      A
      quality
      C
      maintenance
      Enables Claude Code to delegate agent tasks to local LLMs via llama.cpp or vLLM servers on your own hardware, reducing API usage while maintaining full agent capabilities.
      11
      5
      MIT

    • Ollama MCP Server

      JMRussas
      A
      license
      Not graded
      quality
      D
      maintenance
      Exposes local Ollama instances as tools for Claude Code, allowing users to offload code generation, text drafting, and embedding tasks to local GPUs. It supports multi-turn conversations and model management through the Model Context Protocol.
      MIT

    • Ollama MCP Server

      ngc-shj
      A
      license
      Not graded
      quality
      D
      maintenance
      A bridge that enables Claude Code to interact with local Ollama instances for text generation, multi-turn chat, and vision-based analysis. It supports model management tasks such as listing, pulling, and showing details, alongside generating text embeddings.
      330 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 11 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: metrics, model listing, downloading, task offloading (single and batch), context compression, cost dashboard, model recommendation, VRAM preloading, configuration, and automated setup. No two tools overlap in functionality.

    Naming Consistency5/5

    All tools follow the verb_noun snake_case pattern without exception. Names like 'get_metrics', 'offload_work', 'batch_offload', and 'auto_setup' are predictable and consistent.

    Tool Count5/5

    11 tools is appropriate for a server focused on saving tokens via local LLMs. Each tool addresses a specific aspect (model management, task offloading, monitoring, configuration) without being excessive or insufficient.

    Completeness4/5

    The tool set covers the full workflow: model installation, recommendation, preloading, offloading, context compression, and monitoring. Minor gaps exist: there is no tool to unload models from VRAM or delete models, but these are not critical for the primary use case.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources