Integrations

Connect Bynary with your existing tools: GitHub for source control, MCP servers for extending the AI, and Coolify for preview deployments.

Purpose

Bynary is designed to work alongside your existing tools, not replace them. GitHub is the source of truth for code, MCP servers give the AI controlled access to external services, and Coolify runs preview deployments.

Why We Built This

Teams rarely adopt tools that force them to abandon their existing workflows. Bynary works through your repositories and pull requests, so its output fits how your team already ships.

•Works with your repository — Everything Bynary builds arrives as a branch and a pull request
•Controlled tool access — MCP servers have per-server safety rules that you review before a build starts

Setting Up MCP Servers

Open Project Settings

Go to your project's settings, where MCP servers are managed.

Add a Server

Choose a preset, such as Supabase, Stripe, Sentry, Neon, Resend, DigitalOcean, Upstash, Brave Search, Shopify or Twilio, or add a custom server with its name, transport and connection details. Credentials are encrypted before storage.

Test the Connection

Use the test button to check that the server is reachable and responding.

GitHub (Core Integration)

Every project maps to a GitHub repository, through a GitHub App or a Personal Access Token.

Repository creation

Create new repos directly from project setup.

Branch management

Creates a dedicated branch for each build attempt.

Pull requests

Creates a pull request with a detailed description when a cycle completes.

Codebase analysis

Clones and analyses existing repositories during project setup.

Auto-sync

Detects changes pushed to the default branch outside Bynary and records them as a retroactive cycle.

MCP Servers (Optional)

Extend AI capabilities during planning and building:

Database access

Query your database schema or data, with isolation for services that support branching.

API documentation

Give the AI access to your API docs or OpenAPI specs.

Custom tools

Connect any tool that speaks the MCP protocol.

Coolify (Optional)

An administrator can connect a Coolify server so builds deploy to live preview URLs. Projects can switch this off individually.

Frequently Asked Questions

Is GitHub integration required?

Yes. Every project must be linked to a GitHub repository. GitHub is the source of truth for code.

Can MCP servers be used during planning?

Yes. MCP servers configured for a project are available during planning as well as to the build agent.

What MCP server types are supported?

Bynary supports stdio (local process), SSE and streamable HTTP transports.

Do you integrate with Jira?

Not currently. Jira integration isn't available in the product today.

Current Considerations

We've thought carefully about these areas. Some are intentional design choices, others are on our roadmap.

GitHub-only source control

GitLab, Bitbucket and Azure DevOps are not supported.

MCP servers are configured manually

Each server is set up per project from a preset or custom details. There is no marketplace or auto-discovery.