Skip to main content
Glama
wagyourtail

openai-mcp

by wagyourtail
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to openai-mcp

No user-submitted related servers found.

    Related Servers

    • Houtini LM

      emilyg61627
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables Claude Code and other MCP clients to offload bounded tasks to a local or cloud LLM (LM Studio, Ollama, vLLM, LiteLLM, OpenRouter, DeepSeek, Groq, Cerebras, OpenAI) so files are read and drafted outside the orchestrator's context window, cutting token costs. It also provides a cheap second model for code review, test stubs, commit messages, format conversion, and embeddings.
      MIT

    • Houtini LM

      Somchai2984
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables an MCP client to offload bounded tasks such as code review, boilerplate generation, commit messages, and format conversion to a local or cloud LLM, keeping those files out of the main model's context window to cut token costs. It also provides a cheap second model for reviewing code and drafting content while the primary model handles planning and tool use.
      MIT

    • Houtini LM

      SoyeonSantos0239
      F
      license
      Not graded
      quality
      A
      maintenance
      Lets an MCP client hand bounded work such as code review, boilerplate, commit messages, format conversion or embeddings to a local or cloud OpenAI-compatible LLM, so file contents never enter the orchestrating model's context and token costs drop. It also provides a second model to sanity-check code and drafts while the main assistant keeps planning and tool use.
      -

    • Houtini LM

      ryujikim
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables an MCP client such as Claude Code to hand bounded work — code review, test stubs, commit messages, format conversion, embeddings — to a local or cloud OpenAI-compatible model, so the files being processed never enter the orchestrator's context window and token costs drop. It also provides a cheap second model for reviewing code and checking work without consuming the primary assistant's quota.
      -

    • Strata Coder

      huyinghuan
      A
      license
      Not graded
      quality
      F
      maintenance
      Enables a primary coding agent to delegate bounded implementation and repair tasks to a local OpenAI-compatible model that edits a copy of the project, runs configured checks, and returns artifacts for review. Exposes stdio tools for capability discovery, task submission, progress polling, artifact reading, and cancellation.
      MIT

    • Houtini LM

      ThuSyed
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables Claude and other MCP clients to hand off bounded work — code review, test stubs, boilerplate, commit messages, docs, format conversion, embeddings — to local or cloud OpenAI-compatible models while the main assistant keeps planning and QA. Keeps large source files out of the orchestrator's context window, cutting token costs and providing a cheap second opinion on code.
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A3.6/5.0

    Scored across 42 tools

    Disambiguation4/5

    The 42 tools cover distinct sub-domains, and detailed descriptions differentiate overlapping pairs like propose_write/propose_edit and revert_write/uncommit_write. However, a few pairs (e.g., decide vs classify, revert_write vs uncommit_write) could still cause misselection without careful reading.

    Naming Consistency4/5

    Nearly all tools use snake_case verb_noun (list_staged, commit_write, pull_model), with a few single-verb actions (chat, summarize, extract) that remain stylistically consistent. No mixed camelCase or chaotic patterns.

    Tool Count3/5

    42 tools is heavy for a single MCP server, exceeding the typical 3-15 range, though the server's broad scope (staged writes, model management, jobs, local LLM tasks, config) justifies many of them. It risks overwhelming an agent's tool selection.

    Completeness5/5

    The surface covers full lifecycle for staged writes (stage, review, commit, revert, uncommit, verify, discard), model management (search, pull, download, delete, prune, unload, recommend), jobs, local inference tasks, and config. No obvious gaps in the stated domain.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources