Skip to content

Feature Request: Integrate MorphLLM for edit-tool #1591

Closed

Description

@ethan-huo

Consider integrating MorphLLM as a configurable engine for applying AI-generated diffs.

It's specialized for this task, offering high speed and accuracy, with an OpenAI-compatible API. This could improve the reliability of applying complex, multi-file changes.

Activity

  1. changed the title [-]Feature Request: Integrate MorphLLM for diff application[/-] [+]Feature Request: Integrate MorphLLM for edit-tool[/+] on Aug 4, 2025
  2. self-assigned this
    on Aug 4, 2025
  3. garrett-hopper commented on Aug 29, 2025

    @garrett-hopper

    Been having great luck with the MorphLLM MCP server. Great thing about opencode vs claude-code is that the builtin file tools can be disabled instead of having to beg Claude in a context file to always use the right one.

    https://morphllm.com/mcp
    https://docs.morphllm.com/guides/claude-code

    In my opencode.jsonc file:

    {
      "mcp": {
        "filesystem": {
          "enabled": true,
          "type": "local",
          "command": ["npx", "@morph-llm/morph-fast-apply"],
          "environment": {
            "MORPH_API_KEY": "sk-...",
            "ALL_TOOLS": "true",
          },
        },
      },
      "tools": {
        "read": false,
        "edit": false,
        "write": false,
        "list": false,
        "glob": false,
        "grep": false,
        "filesystem_read_file": true,
        "filesystem_read_multiple_files": true,
        "filesystem_list_directory": true,
        "filesystem_list_directory_with_sizes": true,
        "filesystem_directory_tree": true,
        "filesystem_search_files": true,
        "filesystem_get_file_info": true,
        "filesystem_create_directory": true,
        "filesystem_move_file": true,
        "filesystem_edit_file": true, // <-- Only ALL_TOOLS=false tool
        "filesystem_tiny_edit_file": true,
        "filesystem_write_file": true,
        "filesystem_list_allowed_directories": true,
        // OR: "filesystem*": true,
      },
    }

    Of course the filesystem tools don't need to be listed in tools unless you intend to disable some of them.

    I'm currently using ALL_TOOLS=true to try all of them. I don't really know if the non-morph filesystem tools the MCP provides are better or worse than the builtin opencode tools. 🤷

    filesystem_list_allowed_directories is not useful until MCP Roots are supported.

  4. garrett-hopper commented on Aug 29, 2025

    @garrett-hopper

    Note: There appears to be issues when the Morph MCP server detects the root as being above the working directory that opencode is running in. Bash tool will show as the working directory, however files created by the MCP tools will be in the root, leading to confusion.
    Not an issue as long as you start opencode in the directory that will be discovered by the MCP server as the root anyways. (.git, package.json, probably other markers as well)

  5. rekram1-node commented on Dec 28, 2025

    @rekram1-node
    Contributor

    [automated] Closing due to 90+ days of inactivity. Feel free to reopen if you still need this!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions