Skip to main content
Glama
ShiYioo

opencode_native_tools

by ShiYioo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to opencode_native_tools

No user-submitted related servers found.

    Related Servers

    • mcp-opencode

      shreeraman96
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that lets an AI coding agent delegate implementation work to the OpenCode CLI, choosing an explicit provider + model on every call.
      3
      MIT

    • claudecode-mcp

      trevoraspencer
      A
      license
      A
      quality
      B
      maintenance
      Local MCP server that wraps the headless Claude Code CLI as MCP tools, providing stateless access to Claude's coding capabilities through prompt-based interactions. It enables users to execute Claude Code commands with various prompt formats and structured outputs directly from MCP clients.
      3
      MIT

    • agent-rack

      lakpriya1s
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that bridges CLI coding agents like Claude Code, Codex, opencode, and Antigravity into any MCP client, enabling synchronous and asynchronous task execution, follow-up input, and a structured code review tool.
      41 npm
      2
      MIT

    • fernhop

      ElusiveKaze
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that lets Claude hand tasks off to OpenCode, which does the hands-on work with whatever model you configure. Claude can dispatch runs, poll progress, review changed files, interrupt sessions, and pick models through aliases.
      MIT
    Deploy Server
    Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

    TDQS

    A3.9/5.0

    Scored across 11 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes: read vs. write vs. edit are separated by whole-file vs. targeted replacement, and webfetch vs. websearch are cleanly split. However, write, edit, apply_patch, and bash all touch file modification, which could cause occasional misselection.

    Naming Consistency3/5

    Names use a mix of single verbs (read, write, edit, glob, grep), compound words (webfetch, websearch, todowrite), a proper command (bash), and one underscored verb_noun (apply_patch). This is readable but lacks a uniform pattern.

    Tool Count5/5

    With 11 tools, the set is well-scoped for a coding assistant: it covers file operations, search, shell execution, web access, task tracking, and skill loading without being bloated or sparse.

    Completeness5/5

    The file lifecycle is complete (create via write, read, update via edit/apply_patch, delete/move via apply_patch), and search, shell, web, task management, and skill loading cover the expected capabilities for a native tool server. No obvious critical gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources