Can Stackbilt aggregate tools from different backend services?

Yes, it uses a backend adapter pattern to aggregate and namespace tool catalogs from various service bindings. This allows a single MCP endpoint to route calls to multiple backend workers.

Stackbilt is an OAuth-authenticated Model Context Protocol (MCP) gateway that consolidates tool calls from multiple backend services into a single, secure endpoint, streamlining API interactions.

How does Stackbilt handle authentication and security?

It leverages OAuth 2.1 with PKCE, supporting GitHub, Google SSO, and email/password. Stackbilt also features security compliance with tool risk levels, structured audit logging, and HMAC-signed identity tokens.

What data transport protocols does Stackbilt support?

Stackbilt utilizes MCP JSON-RPC over HTTP, providing flexible communication options including both streaming (Server-Sent Events - SSE) and traditional request/response transport.

Stackbilt

Name: Stackbilt
Author: Stackbilt-dev

0•

Routes OAuth-authenticated Model Context Protocol (MCP) tool calls to multiple backend product services via a single endpoint.

The Stackbilt MCP Gateway provides a unified OAuth-authenticated Model Context Protocol (MCP) endpoint for various Stackbilt platform services. It intelligently routes tool calls to distinct backend product workers, such as Stackbilder for architecture flow orchestration and img-forge for AI image generation, simplifying client integration with multiple services through a single MCP connection. Built as a Cloudflare Worker, it ensures secure access, compliance with a security constitution, and efficient dispatch of requests.

Key Features

01MCP JSON-RPC over HTTP, supporting both streaming (SSE) and request/response transport

020 GitHub stars

03Backend adapter pattern for aggregating and namespacing tool catalogs from multiple service bindings

04OAuth 2.1 with PKCE supporting GitHub, Google, and email/password authentication

05Coming-soon gate with `PUBLIC_SIGNUPS_ENABLED` flag to control public access

06Security Constitution compliance with declared tool risk levels, structured audit logging, and HMAC-signed identity tokens

Use Cases

01Unifying access to architecture flow orchestration and AI image generation tools through a consolidated API

02Implementing OAuth-authenticated access for external clients to a suite of internal platform tools

03Providing a single, secure MCP endpoint to manage access to multiple backend platform services