Configure GitHub Bridge access, publish Model Context Protocol capabilities, and manage OpenAPI, REST API, and discovery documents from one Power369 developer surface.
Mint scoped tokens for AI tools and human collaborators, with folder-level allow and block rules.
Prepare a model-facing server surface that exposes only the repo areas and tools each token is allowed to use.
Publish structured route data and generate reusable OpenAPI endpoint definitions for trusted AI and developer clients.
Document direct HTTP access patterns for bridge consumers, automation scripts, and internal product flows.
Each key is tied to one GitHub repository and uses your own PAT. Tokens auto-expire and can be revoked anytime.
Let the business owner or lead admin decide what each token is allowed to do before it is shared with a person or AI workflow.
BeginnerRead-focused access for safe areas only.DeveloperNormal branch work on selected paths.AdminHighest trust for platform operators and policy owners.Bring your own GitHub credentials, but keep the bridge selective. The safest pattern is to connect one repository at a time, use a fine-grained token, and only grant the exact permissions needed for the work.
Step 1Choose the exact repo you want the bridge to access.Step 2Create a fine-grained GitHub token for that repo only.Step 3Start with selective permissions such as metadata and contents, then add more only if a feature truly needs them.Step 4Mint a Power369 token with a named owner, selected role, and clear path limits.Treat this area like a proper Power369 developer console. Create one scoped token, then decide whether it should power GitHub Bridge, MCP, Open API, REST API, or a combined developer integration.
This repo already contains a public OpenAPI page, a root OpenAPI spec, and a dedicated Model Context Protocol package. The next backend pass should build around these existing assets rather than replacing them.
public/openapi/index.htmlCurrent public OpenAPI landing page.openapi/openapi.yamlCurrent root OpenAPI specification file.mcp/src/index.tsCurrent Model Context Protocol adapter server over the bridge REST API.mcp/README.mdCurrent setup and client configuration guidance.These public discovery files and specifications already exist in the repo and should be surfaced clearly in the Power369 developer area for integrators, API consumers, and AI clients.
/.well-known/mcp.jsonModel Context Protocol discovery document for MCP-aware clients./.well-known/ai-plugin.jsonAI plugin discovery document for compatible integrations./.well-known/openapi.jsonPublic OpenAPI discovery file for tooling and automated clients./openapi/openapi.yamlCanonical OpenAPI specification source./openapiPublic OpenAPI landing page currently served from public/openapi/index.html.Suggested endpoint surface for your Power369 developer area, based on your existing public OpenAPI, root MCP package, and API discovery setup. These routes should all validate the same scoped token and respect the same allowed and blocked areas.
GET /api/mcp/manifestDescribe Model Context Protocol server identity and enabled tools.GET /api/mcp/resourcesList token-allowed repo resources.POST /api/mcp/tools/:nameInvoke named tools with token-scoped permissions.GET /api/mcp/openapi.jsonPublish generated OpenAPI description for AI clients.GET /api/bridge-ext/treeFiltered repo tree for direct REST consumers.GET /api/bridge/filePrimary single-file read endpoint; supports full reads and optional chunked paging.Give developers and AI tools a fast starting point with direct discovery URLs and ready-to-copy configuration snippets.
https://power369.uk/.well-known/mcp.json
Model Context Protocol discovery URL.
https://power369.uk/openapi/openapi.yaml
Canonical OpenAPI specification URL.
https://power369.uk/.well-known/ai-plugin.json
Plugin discovery URL.
{
"mcpServers": {
"power369-bridge": {
"command": "node",
"args": ["/path/to/power369-bridge-mcp/dist/index.js"],
"env": {
"BRIDGE_URL": "https://power369.uk",
"BRIDGE_EXT_TOKEN": "{{TOKEN_WILL_APPEAR_HERE}}"
}
}
}
}
curl "https://power369.uk/api/bridge-ext/tree?key={{TOKEN_WILL_APPEAR_HERE}}"
GET /api/bridge-ext/configInspect repo and policy for the current bridge token.GET /api/bridge-ext/treeList filtered files and folders for REST consumers.GET /api/bridge-ext/fileRead one allowed file by repo-relative path.POST /api/bridge-ext/push-branchWrite whole-file updates to a new branch when push is allowed./api/bridge-ext/* with the key. Power 369 unwraps the key server-side and acts on your repo using your PAT. The AI never sees the PAT.Get notified the moment an AI pushes a branch, a token expires, or a rate limit is hit. Power369 signs every delivery with HMAC-SHA256 so your endpoint can verify it.