Is there a way to override the mcps?

[OneOfOne]

For example I'd like to use a local context7 and use searnxg for websearch.

[Zaradacht]

TL;DR for humans

Yes, but in your current OMO Slim/OpenCode setup they are not actually replaced yet.

Right now, OMO Slim has built-in websearch and context7 disabled, which is the right first step if you want to provide your own MCP servers with those names. However, your OpenCode mcp config is currently empty, and your OMO Slim agents all have mcps: [], so there is no local Context7 or SearXNG MCP available to the agents yet.

The practical setup is:

{
  "mcp": {
    "context7": {
      "type": "local",
      "command": ["<command-that-starts-your-local-context7-mcp>"]
    },
    "websearch": {
      "type": "local",
      "command": ["<command-that-starts-your-searxng-mcp>"]
    }
  }
}

Then allow those MCPs on the agents that should use them, for example the librarian:

"librarian": {
  "mcps": ["context7", "websearch"]
}

OMO Slim’s built-in websearch.provider only supports Exa/Tavily today, so SearXNG needs to be configured as a custom/local OpenCode MCP rather than as a websearch.provider value.

Prompt for the agent

Inspect current OMO Slim and OpenCode MCP merge behavior and document the supported way to replace built-in MCPs with local ones. Specifically verify:

• built-in websearch, context7, and gh_grep registration behavior
• whether built-ins overwrite same-name OpenCode mcp entries unless disabled
• how disabled_mcps interacts with custom same-name MCP entries
• how agent mcps allowlists affect permissions
• whether websearch.provider supports only Exa/Tavily or can support SearXNG

Then update the docs with a short “Using custom MCPs instead of built-ins” section showing:

• disable the built-in MCP
• add a same-name custom OpenCode mcp entry
• allow that MCP on the relevant OMO Slim agents
• restart OpenCode after config changes

[mhenke]

Answered by @Zaradacht: replace built-ins via a custom mcp config + agent mcps allowlists — see docs/mcps.md.