bb

The Beyond Better bb MCP server is a Deno-based implementation of the Model Context Protocol (MCP) designed to help you build, run, and test modular MCP servers with built-in OAuth support, plugin/workflow discovery, and dual transport options. It exposes a framework for composing tools and workflows that can be discovered and executed by clients or automated agents. With the included example pipelines, you can explore basic tooling (utilities, logging, JSON validation) and progressively add OAuth integrations and multi-step workflows. The server supports both STDIO and HTTP transport, enabling flexible development and testing workflows. To get started, use the provided BB guidelines and the example repositories to see how servers are constructed, configured, and extended with plugins and workflows.

When you run the server via the recommended deno command, you’ll load an example MCP server that demonstrates plugin discovery, environment-based configuration, and a straightforward startup path. You can then adapt the example to your own domain logic, swap in OAuth clients, and wire in additional tools or workflows as needed. The documentation emphasizes using Beyond Better as a companion to generate boilerplate, validate configurations, and help you scaffold your MCP server with best practices in mind.

Prerequisites:

• Install Deno (https://deno.land/manual@v1.29.0/getting_started/installation)
• Optional: familiar with the Beyond Better workflow for generating boilerplate (bb CLI, if you use Beyond Better Cloud or local development)

Installation steps:

1. Install Deno on your system. Follow the official guide for your OS:
   • macOS: brew install deno
   • Windows: scoop install deno or choco install deno
   • Linux: curl -fsSL https://deno.land/x/install/install.sh | sh
2. Verify installation: deno --version
3. Run the BB MCP example locally to explore the server: deno run --allow-all --unstable-kv jsr:@beyondbetter/bb-mcp-server/examples/1-simple
4. If you want to experiment with a local project, clone the repository and start from the 1-simple example, then iteratively add plugins, workflows, and OAuth integrations as needed.

Notes:

• The server is designed to be used with Deno KV-backed storage and supports environment-driven configuration.
• For production-grade setups, consider using Beyond Better Cloud or containerized deployment as described in the BB docs.

Tips and common considerations:

• The server relies on Deno; ensure your runtime supports the necessary permissions (e.g., --allow-all) for development and testing.
• OAuth integration is a core feature; plan to configure OAuth providers and clients in your environment or codebase.
• The example 1-simple demonstrates basic tooling and transport; explore 2-plugin-workflows and 3-plugin-api-auth for more advanced workflows and API authentication patterns.
• If you plan to run in a container, you can adapt the deno run command into a container entrypoint and pass environment variables for configuration.
• When debugging, enable verbose logging and inspect the plugin discovery process to validate that workflows and tools are being loaded correctly.