docs: the machines guide still says MCP servers are not lent to an agent on a machine
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 88/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- python
- Domain
- documentation
Research direction
Read the “MCP servers are not lent” paragraphs in docs-site/docs/machines.md and docs-site/docs/machines.zh.md. Update both pages to match the v0.2.5 behavior described in the issue: which entry kinds receive granted servers, how they reach the agent, that servers and keys remain on the host, and that Windows hosts support lending. Done when both pages describe the same current behavior and no longer present #947 as future work.
Written by the indexing model from the issue text.
Description
Summary
The guide to working on registered machines still says the host's MCP servers are not lent across the link, and that lending "is coming, in pull request #947":
docs-site/docs/machines.md, the paragraph that opens with "MCP servers are not lent." (lines 338-341 at v0.2.5);docs-site/docs/machines.zh.md, the same paragraph in Chinese (lines 255-256 at v0.2.5).
Both are live at https://evermind-ai.github.io/Raven/machines/. The guide (#956) merged an hour before #947 on 2026-10-15, and #947 shipped the lending: an acp entry on a registered machine is handed the MCP servers its row grants, through the node's bridge, while the servers, their definitions and their keys stay on this computer. #972 then extended it to Windows hosts. The 0.2.5 release notes describe the lending and link this guide, so a reader of both sees them disagree.
@Handsome-wzw, you wrote the guide and the lending. Could you bring both pages up to date?
Expected behavior
Both pages describe MCP lending as it works at v0.2.5: which entry kinds receive it, that the servers and their keys stay on the host, how a granted server reaches the agent on the machine, and that Windows hosts lend too.
Actual behavior
Both pages say the servers are not lent and point at #947 as future work.
Environment
Raven 0.2.5 (tag v0.2.5); the docs site as deployed from main. Found while writing the 0.2.5 release notes.
- Dominant language
- Python
- Stars
- 4.1k
- Forks
- 94
- Avg merge
- 23h 45m
- Merged PRs (30d)
- 297
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from EverMind-AI/Raven
-
fix(tui): a skipped DAG node read from a snapshot shows a 0s durationPossibly taken @yudongyouqing claimed this 1 day ago. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
EverMind-AI/Raven#1000 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
EverMind-AI/Raven#998 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
EverMind-AI/Raven#997 ·
Maintainers usually reply within 1 day
-
security: tool output scrubbing misses raven's own oauth token filesPossibly taken @akushonkamen claimed this 11 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
EverMind-AI/Raven#842 · 2 comments ·
Maintainers usually reply within 1 day
-
WeChat send silently succeeds when iLink returns non-zero ret with errcode=0Possibly taken @akushonkamen claimed this 6 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
EverMind-AI/Raven#210 · 2 comments ·
Maintainers usually reply within 1 day
All issues in EverMind-AI/Raven
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
MISP/misp-workbench#496 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
fossasia/visdom-dev#69 ·
Maintainers usually reply within 3 days
-
[Bug] Parameters named like a property break to_xcal()Possibly taken @atharvasalunke1267 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
collective/icalendar#2018 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day