feat(agents): wire MCP servers + skills into the Gemini and OpenClaw CLI agents#34
Draft
pradeepvrd wants to merge 1 commit into
Draft
feat(agents): wire MCP servers + skills into the Gemini and OpenClaw CLI agents#34pradeepvrd wants to merge 1 commit into
pradeepvrd wants to merge 1 commit into
Conversation
c820ad0 to
58d521b
Compare
7cd085e to
cbd1afd
Compare
58d521b to
c9553ba
Compare
cbd1afd to
940c4ea
Compare
c9553ba to
0e2995e
Compare
b66af88 to
030b34c
Compare
0e2995e to
a01e4c7
Compare
030b34c to
5d8e551
Compare
a01e4c7 to
fec6322
Compare
5d8e551 to
6b298b2
Compare
fec6322 to
104e20a
Compare
6b298b2 to
d4fbeae
Compare
104e20a to
6b67eed
Compare
d4fbeae to
d0a67cd
Compare
…CLI agents The Gemini and OpenClaw CLI agents declared rules/MCP/skills capabilities but only pre-approved tool names and delivered the operator brief — MCP servers were never launched and skills were ignored. This wires both agents to actually deliver MCP + skills through each binary's native, per-run channels. **Behavior changes** - Gemini: command-bearing MCP bindings are written as `mcpServers` in a per-run `<cwd>/.gemini/settings.json`, and skills are materialized to `<cwd>/.gemini/skills/<name>/SKILL.md` with `skills.enabled`; the binary then spawns the servers and loads the skills. - OpenClaw: MCP bindings are written as `mcp.servers` in a per-run isolated config (`OPENCLAW_CONFIG_PATH`) and skills under `<OPENCLAW_STATE_DIR>/skills/`, both per-run so nothing touches `~/.openclaw`; the embedded `oc agent --local` consumes them. The model API key is threaded into the provider env var, and the agent id defaults to `oc`'s built-in `main`. - Both agents now assign `mcp_servers` + `skills`, so they structurally satisfy `SupportsMcp` / `SupportsSkills`; granting those bindings used to be a silent no-op.
6b67eed to
8fdeb40
Compare
d0a67cd to
9b39991
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The Gemini and OpenClaw CLI agents declared rules/MCP/skills capabilities but only pre-approved tool names and delivered the operator brief — MCP servers were never launched and skills were ignored. This wires both agents to actually deliver MCP + skills through each binary's native, per-run channels.
Behavior changes
mcpServersin a per-run<cwd>/.gemini/settings.json, and skills are materialized to<cwd>/.gemini/skills/<name>/SKILL.mdwithskills.enabled; the binary then spawns the servers and loads the skills.mcp.serversin a per-run isolated config (OPENCLAW_CONFIG_PATH) and skills under<OPENCLAW_STATE_DIR>/skills/, both per-run so nothing touches~/.openclaw; the embeddedoc agent --localconsumes them. The model API key is threaded into the provider env var, and the agent id defaults tooc's built-inmain.mcp_servers+skills, so they structurally satisfySupportsMcp/SupportsSkills; granting those bindings used to be a silent no-op.