Skip to content

ci(clara): load MCP config from pinned clara_workflow ref - #3773

Merged
ubyndr merged 1 commit into
masterfrom
clara-mcp-from-workflow-ref
Oct 1, 2026
Merged

ubyndr merged 1 commit into
masterfrom
clara-mcp-from-workflow-ref

Conversation

@ubyndr

@ubyndr ubyndr commented Oct 1, 2026

Copy link
Copy Markdown
Collaborator

What

Why

The agent's instructions were already versioned through CLARA_WORKFLOW_REF, but its MCP servers came from this repo's root .mcp.json. That's why the invalid Asta entry had to be fixed in two places (#3772). Reading the config from the pinned ref keeps instructions and tool wiring in step.

This is safe for PR runs: clara_workflow_ref/ is checked out from Cellular-Semantics at a pinned SHA, so PR content can't change it.

Root .mcp.json is kept

The root file is used elsewhere, so it stays. The action enables all project MCP servers, so it still loads as a project config. When the same server name is defined in both, --mcp-config takes precedence. I checked this locally with Claude Code 2.1.286: with a broken Asta URL in the project .mcp.json and a valid one passed via --mcp-config, Asta connected with source: dynamic and snippet_search returned results.

Testing

Not yet run in CI. Next /clara run: check that the init log shows Asta_semanticscholar connected (source: dynamic) and that runs/CL_…/tool_calls.jsonl contains snippet_search calls.

🤖 Generated with Claude Code

Point --mcp-config at clara_workflow_ref/.mcp.json so the agent's tool
wiring is versioned together with agent_instructions.md via
CLARA_WORKFLOW_REF, rather than depending on the root .mcp.json. Bump
the pin to 234ac67, which contains the fixed Asta config
(Cellular-Semantics/clara_workflow#10). The root .mcp.json is kept for
other uses; --mcp-config takes precedence for same-named servers.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@ubyndr
ubyndr merged commit b7cb31d into master Oct 1, 2026
3 checks passed
@ubyndr
ubyndr deleted the clara-mcp-from-workflow-ref branch October 1, 2026 12:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant