# Barbacane MCP server

> Compiles an OpenAPI or AsyncAPI spec into a signed API gateway artifact that enforces routing, validation, auth, rate limits, and a WAF.

- Repository: https://github.com/barbacane-dev/barbacane
- Page: https://hostedmcp.org/servers/barbacane-dev/barbacane
- Transport: —
- Stars: 29
- License: AGPL-3.0

## Environment variables

| Name | Required | Secret | Description |
|---|---|---|---|
| `BARBACANE_SIGNING_KEY` | no | no |  |
| `BARBACANE_TRUSTED_PUBKEY` | no | no |  |

## FAQ

### What spec formats does Barbacane support?

Barbacane uses OpenAPI 3.x or AsyncAPI 3.x specifications as its configuration source, compiling them into a sealed .bca artifact.

### Does Barbacane include a web application firewall?

Yes, it has a built-in ModSecurity/CRS-compatible WAF that runs inline in scoring or blocking mode and is configured with an x-barbacane-waf block.

### What authentication methods can Barbacane enforce?

It offers plugins for JWT, API key, basic, OAuth2, OIDC, and LDAP authentication, plus authorization plugins such as ACL, OPA, and CEL.

### Can I write custom plugins for Barbacane?

Yes, you can write plugins in any language that compiles to WebAssembly, and they run sandboxed so a faulty plugin cannot take down the gateway.
