feat: expose MCP over HTTP#142
Conversation
Co-authored-by: ecarreras <294235+ecarreras@users.noreply.github.com>
|
@pilipilisbot la url entenc que serà la pública, la captura semblança privada i això ja t'ho havia comentat |
Expose the dashboard URL source in status responses and show it on the MCP setup page so admins can distinguish configured/forwarded public URLs from request-derived local URLs. Warn before sharing request-derived URLs with remote agents. Co-authored-by: ecarreras <294235+ecarreras@users.noreply.github.com>
|
Fixed in
Checks are green: |
|
@pilipilisbot per mi pots eliminar el local fallback |
Co-authored-by: ecarreras <294235+ecarreras@users.noreply.github.com>
|
Implemented in
Verification is green: I also captured a refreshed local screenshot of |
|
Post-merge cleanup complete for PR #142.
|
Summary
POST /api/mcp/api/mcpendpoint without installinggabTests
npm test -- src/main.test.tsx(42 passed)npm run buildPYTHONPATH=src ../github-agent-bridge/.venv/bin/pytest -q tests/test_mcp.py tests/test_backend.py::test_dashboard_status_reports_configured_public_url tests/test_backend.py::test_dashboard_status_reports_forwarded_public_url(5 passed)Follow-up to #141 / #140.
Screenshot