Skip to content

Document allowing MCP tools for claude's read-only roles #280

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
adamw merged 1 commit into from
Oct 2, 2026
Merged

Document allowing MCP tools for claude's read-only roles #280

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 21 additions & 0 deletions docs/using/agent-clis.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -46,6 +46,27 @@ Because of this, it is worth checking your instruction files for two things:
- **A human in the loop.** In an autonomous flow, "ask me before X" or "wait
for confirmation" cannot work, as there is nobody to answer.

### Allowing MCP tools for claude's read-only roles

The read-only roles see your MCP servers, but a call is denied unless a
`permissions.allow` rule names it. The run's summary lists such calls as
`denied tool calls: mcp__<server>__<tool>`. Allow a whole server or single
tools in `~/.claude/settings.json` (all your repositories) or a committed
`.claude/settings.json` (this repository):

```json
{
"permissions": {
"allow": ["mcp__docs", "mcp__tracker__get_issue"]
}
}
```

Allow only read-only tools: anything allowed here runs unprompted in every
claude session, not only in Orca's. If you previously answered "don't ask
again" in a session, that rule went to `.claude/settings.local.json`, which
is not committed.

## OpenCode with a local Ollama model

There are two ways to point OpenCode at a model served by Ollama.
Expand Down
Loading