github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-07-16 14:24:24 -05:00
Code Issues 2.4k Packages Projects Releases 129 Wiki Activity

[GH-ISSUE #24504] feat: P2PCLAW MCP Server — Publish Scientific Papers from OpenWebUI #91058

New Issue
Closed
opened 2026-05-15 16:19:42 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-05-15 16:19:42 -05:00
Owner
Copy Link

Originally created by @Agnuxo1 on GitHub (May 9, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/24504

Proposal: P2PCLAW MCP Integration for Scientific Paper Publishing

Hi OpenWebUI team! First off, amazing work on the native MCP support in v0.4+ — the tool-calling flow is clean and the mcpo proxy makes integrations straightforward.

What is P2PCLAW?

P2PCLAW is a decentralized scientific research network with 14 autonomous AI agents:

  • BenchClaw — Multi-dimensional agent benchmarking (17-judge Tribunal)
  • PaperClaw — AI paper generation with structured academic output
  • CAJAL — Local scientific LLM (2GB, runs on RTX 3090 or CPU)
  • EnigmAgent — Security-focused agent for vulnerability research
  • And 10 more specialized agents...

Technical Fit

  • MCP Server: (already live)
  • Protocol: Standard MCP with OpenAPI-compatible endpoints
  • Use Case: OpenWebUI users doing local research can publish verified papers with agent peer review
  • Workflow: User writes research in OpenWebUI → P2PCLAW MCP server → distributed to 14 agents for review → published on P2PCLAW network

Why This Makes Sense for OpenWebUI

  1. Academic users — Many OpenWebUI users run local models for research; P2PCLAW gives them a publishing outlet
  2. Verified output — Papers go through multi-agent Tribunal scoring (0-10) before publication
  3. Zero cloud dependency — CAJAL runs entirely locally, matching OpenWebUI's self-hosted philosophy
  4. Real-time leaderboard — Papers get scored and ranked at

Links

Category

Feature Request / MCP Integration

Disclaimer: I am the creator of P2PCLAW. Happy to discuss implementation details or provide a PR if there's interest.

cc: @tjbck @jannikbuschke

Originally created by @Agnuxo1 on GitHub (May 9, 2026). Original GitHub issue: https://github.com/open-webui/open-webui/issues/24504 ## Proposal: P2PCLAW MCP Integration for Scientific Paper Publishing Hi OpenWebUI team! First off, amazing work on the native MCP support in v0.4+ — the tool-calling flow is clean and the mcpo proxy makes integrations straightforward. ### What is P2PCLAW? **P2PCLAW** is a decentralized scientific research network with 14 autonomous AI agents: - **BenchClaw** — Multi-dimensional agent benchmarking (17-judge Tribunal) - **PaperClaw** — AI paper generation with structured academic output - **CAJAL** — Local scientific LLM (2GB, runs on RTX 3090 or CPU) - **EnigmAgent** — Security-focused agent for vulnerability research - And 10 more specialized agents... ### Technical Fit - **MCP Server:** (already live) - **Protocol:** Standard MCP with OpenAPI-compatible endpoints - **Use Case:** OpenWebUI users doing local research can publish verified papers with agent peer review - **Workflow:** User writes research in OpenWebUI → P2PCLAW MCP server → distributed to 14 agents for review → published on P2PCLAW network ### Why This Makes Sense for OpenWebUI 1. **Academic users** — Many OpenWebUI users run local models for research; P2PCLAW gives them a publishing outlet 2. **Verified output** — Papers go through multi-agent Tribunal scoring (0-10) before publication 3. **Zero cloud dependency** — CAJAL runs entirely locally, matching OpenWebUI's self-hosted philosophy 4. **Real-time leaderboard** — Papers get scored and ranked at ### Links - **P2PCLAW GitHub:** https://github.com/Agnuxo1/OpenCLAW-P2P - **MCP Server:** https://github.com/Agnuxo1/p2pclaw-mcp-server - **Demo:** https://www.p2pclaw.com/silicon - **Paper Example:** https://www.researchgate.net/publication/403659551 ### Category Feature Request / MCP Integration --- _Disclaimer: I am the creator of P2PCLAW. Happy to discuss implementation details or provide a PR if there's interest._ cc: @tjbck @jannikbuschke
GiteaMirror commented 2026-05-15 16:19:43 -05:00
Author
Owner
Copy Link

@owui-terminator[bot] commented on GitHub (May 9, 2026):

🔍 Related Issues Found

I found some existing issues that might be related. Please check if any of these are duplicates or contain helpful solutions:

  1. 🟣 #23835 Integration: PaperClaw (autonomous peer-reviewed paper generator for Open WebUI)
    This is the same PaperClaw/P2PCLAW integration request from the same author, proposing Open WebUI integration for autonomous paper generation and publication. The new issue extends that idea specifically to an MCP server, so it is directly related.
    by Agnuxo1

  2. 🟣 #23817 Integration: PaperClaw (autonomous peer-reviewed paper generator for Open WebUI)
    This is a duplicate PaperClaw integration request that describes the same P2PCLAW-driven research/paper publishing workflow for Open WebUI. It overlaps heavily with the new MCP-server proposal and is clearly related.
    by Agnuxo1

  3. 🟣 #24117 feat: Expose Open WebUI as a native MCP server — enable direct Hermes Agent-to-WebUI communication and full headless control
    This asks for Open WebUI to expose itself as a native MCP server for direct agent communication. While broader than the new issue, it is the same MCP-server integration theme and directly relevant to MCP exposure/integration discussions.
    by githb-ac

💡 If your issue is a duplicate, please close it and add any additional details to the existing issue instead.

This comment was generated automatically. React with 👍 if helpful, 👎 if not.

<!-- gh-comment-id:4413248141 --> @owui-terminator[bot] commented on GitHub (May 9, 2026): <!-- terminator-bot:related-issues-reply --> 🔍 **Related Issues Found** I found some existing issues that might be related. Please check if any of these are duplicates or contain helpful solutions: 1. 🟣 [#23835](https://github.com/open-webui/open-webui/issues/23835) **Integration: PaperClaw (autonomous peer-reviewed paper generator for Open WebUI)** *This is the same PaperClaw/P2PCLAW integration request from the same author, proposing Open WebUI integration for autonomous paper generation and publication. The new issue extends that idea specifically to an MCP server, so it is directly related.* *by Agnuxo1* 2. 🟣 [#23817](https://github.com/open-webui/open-webui/issues/23817) **Integration: PaperClaw (autonomous peer-reviewed paper generator for Open WebUI)** *This is a duplicate PaperClaw integration request that describes the same P2PCLAW-driven research/paper publishing workflow for Open WebUI. It overlaps heavily with the new MCP-server proposal and is clearly related.* *by Agnuxo1* 3. 🟣 [#24117](https://github.com/open-webui/open-webui/issues/24117) **feat: Expose Open WebUI as a native MCP server — enable direct Hermes Agent-to-WebUI communication and full headless control** *This asks for Open WebUI to expose itself as a native MCP server for direct agent communication. While broader than the new issue, it is the same MCP-server integration theme and directly relevant to MCP exposure/integration discussions.* *by githb-ac* --- 💡 If your issue is a duplicate, please close it and add any additional details to the existing issue instead. *This comment was generated automatically.* React with 👍 if helpful, 👎 if not.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
confirmed
confirmed issue
core
documentation
enhancement
good first issue
help wanted
non-core
pull-request
Mirrored from GitHub Pull Request
 python
question
testing wanted
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#91058
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?