Skip to main content
Glama
Sign In
BitPull

BitPull

by SamuealPK
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to BitPull

No user-submitted related servers found.

    Related Servers

    • Toskar

      yeixio
      A
      license
      A
      quality
      B
      maintenance
      Run local AI across all your computers. Toskar's MCP server lets Claude, Cursor, and other clients ask your own local models and search your connected knowledge, with nothing leaving your machines.
      3
      5
      AGPL 3.0

    • Vibecoders MCP

      RaedBerjaoui
      A
      license
      A
      quality
      D
      maintenance
      One MCP that turns Claude Code into your whole dev stack by swallowing other MCP servers, delegating to Codex & Gemini on your CLI subscriptions, remembering projects in a searchable knowledge graph, and carrying setup across sessions — secret-free by design.
      23
      4
      MIT

    • KeepContext

      darshanbajgain
      A
      license
      Not graded
      quality
      B
      maintenance
      A self-hosted MCP server that gives every connected AI app (ChatGPT, Claude, Gemini, Cursor, Codex, Copilot) one shared memory of ideas, decisions, todos, notes and standing instructions to read and write. It also lets apps start multi-step tasks and save checkpoints on a git branch, so when one hits its usage limit another can resume the work and the original app can later review what changed.
      4
      AGPL 3.0

    • Commons

      Neoo-Blue
      A
      license
      B
      quality
      B
      maintenance
      Lets multiple AI agents and parallel coding sessions share one memory and task ledger, so they can claim work instead of duplicating it, resume each other's handoffs and reasoning, and use credentials without ever seeing the keys. Connects assistants such as Claude Code, Codex, Cursor, Gemini, ChatGPT and custom agents over MCP, backed by a single local SQLite file or a self-hosted Postgres hub.
      41
      MIT

    • FIREFIGHTER

      JoshWright22
      A
      license
      A
      quality
      B
      maintenance
      Your AI agents won't set your GPU on fire. GPU/CPU/RAM scheduler + market maker for AI coding agents (Claude Code, Codex, Gemini, Cursor, Grok, OpenCode, Kimi, Copilot and more) sharing one PC. Any mix of GPUs, MCP server, one-command install, Windows/macOS/Linux.
      5
      MIT

    • agent-bus-mcp

      MustaphaSteph
      A
      license
      Not graded
      quality
      C
      maintenance
      A local MCP server that connects AI coding agents (Claude Code, Codex, Cursor, etc.) on the same machine via a shared message bus, enabling them to chat, delegate tasks, and collaborate privately without cloud or internet.
      33 npm
      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

    C2.8/5.0

    Scored across 72 tools

    Disambiguation3/5

    Several clusters are genuinely hard to tell apart from names alone: ask_open_model vs ask_group_model vs use_open_model vs ask_ai_model, list_open_models vs list_ai_models vs list_group_models vs bitpull_chat_models, and bitpull_status vs bitpull_setup_status vs job_status vs bitpull_site_job. The long descriptions do resolve most of these once read, but an agent scanning names will misselect frequently in the model and status families.

    Naming Consistency2/5

    All names are snake_case, but prefixing is inconsistent: some are bitpull_*, others are bare (search_repos, run_job, my_balance, publish_repo, preview_click). Verb styles also vary, with noun-only names like bitpull_site_job, bitpull_groups, bitpull_site_accounts mixed against verb-led names.

    Tool Count1/5

    72 tools is far beyond a reasonable surface for one server; the domains span publishing, databases, scheduling, local compute lending, model access, preview/browser control, repos, and setup checks. Many tools are narrow one-shot variants that could be folded into a handful of parameterised tools.

    Completeness4/5

    Across its many sub-domains the core lifecycle is largely covered: create/authorise/remove folders, prepare/publish/remove repos, create/claim/disconnect accounts, schedule create/run/delete, and job run/status/save files. Gaps are minor (no explicit unpublish/delete-site or edit-manifest operation), and agents can work around them.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources