Gwirian MCP Server

Gwirian MCP server exists for a simple reason — assistants are far more useful when they can act on Gwirian directly instead of describing what you should do. Gwirian empowers development teams to manage their BDD features with ease. Create and organize features, define scenarios, track executions, and collaborate with your team—all in one beautiful, fast, and intuitive platform. Built with.

What you get

• Workspaces — Organize teams and projects into separate workspaces
• Projects — Group related features within a workspace
• Features — Define BDD features with descriptions and backgrounds
• Scenarios — Create scenarios with Given/When/Then structure
• Steps — Define detailed steps for each scenario
• Executions — Track scenario execution status and history

What the assistant can call

Once Gwirian is connected, these are the calls the assistant has available:

• RSpec — Testing framework
• FactoryBot — Test data generation
• Rubocop — Code style enforcement
• Brakeman — Security vulnerability scanner
• Capybara — System testing
• Authentication — The Authentication tool exposed by this server
• Authorization — The Authorization tool exposed by this server
• Services — The Services tool exposed by this server
• Prerequisites — The Prerequisites tool exposed by this server
• Documentation — The Documentation tool exposed by this server
• Community — The Community tool exposed by this server

Configuration and credentials

You will need 2 environment variables: DATABASE_URL, ELASTICSEARCH_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• Ruby 4.0.0 (see .ruby-version) - Docker and Docker Compose (for Elasticsearch and Mailhog) - Bundler (Ruby gem manager) - Node.js (for Tailwind CSS compilation)

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Choosing this one

Among the team communication options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Gwirian's toolset — RSpec, FactoryBot, Rubocop and 8 more — is a fair guide to whether it matches your workflow. It is maintained by theacmada; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 11 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Gwirian.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the gwirian mcp server does with a few real requests.