Connect your AI agent to Vybrane

Vybrane is your company’s brain: it knows your code, numbers, decisions and who owns what. Connect your AI agent and it works with that context. It can ask the brain, take the jobs your team queues (questions and fixes), and propose posts and emails for a founder to approve.

Before you start

You need a Vybrane workspace. Sign up (free, no card) and connect GitHub during onboarding (one button, no token). Curious how fixes work? Let your own Claude or Codex fix things. Want to look first? Try the live demo on a public repo.

Claude (claude.ai, desktop and mobile)

Settings → Connectors → Add custom connector.
Paste this address, then tap Add: https://tryvybrane.com/api/mcp
Vybrane opens: sign in, pick your workspace and tap Allow. No key to copy.

Claude Code

claude mcp add --transport http vybrane https://tryvybrane.com/api/mcp

Then type /mcp, pick vybrane and choose Authenticate.

Codex

codex mcp add vybrane --url https://tryvybrane.com/api/mcp

Then run codex mcp login vybrane.

Grok Bot, Muse, ChatGPT, Cursor and other MCP apps

Copy the address above.
In Grok Bot or Muse, ask it: “Add a custom connector”. When it asks for the address, paste it and name it Vybrane. If the bot can’t do that from the chat, add it in the app’s settings under Connectors, Apps or MCP.
A Vybrane page opens: sign in, pick your workspace and tap Allow. No key to copy.
Try: “Get today’s marketing brief from Vybrane and propose three posts.” They wait on the Marketing board for your approval.

ChatGPT, Cursor and any other app that takes an MCP server work the same way.

Try it

“Ask Vybrane what shipped this week and what needs attention.”
“Do the Vybrane jobs.” (takes the questions and fixes your team queued)
“What did we decide about pricing?”

Fix bugs with your own Claude

Vybrane finds bugs and writes the job. Your own Claude (on your Claude Pro or Max plan, or an API key) does the fix on a new branch and opens a pull request. A person always merges. Nothing reaches your main branch without you.

1. Connect GitHub (a founder, once)

In Vybrane, tap Connectors at the top → GitHub → Connect, and pick your repo.
Vybrane can now read your code and commits. Questions about the code are answered right away, without Claude.

2. Connect your Claude to Vybrane (each person who wants to)

Claude (claude.ai, desktop or mobile): Settings → Connectors → Add custom connector, paste https://tryvybrane.com/api/mcp then sign in, pick your workspace and tap Allow.
Or Claude Code: run claude mcp add --transport http vybrane https://tryvybrane.com/api/mcp then /mcp → vybrane → Authenticate.
Or Codex: run codex mcp add vybrane --url https://tryvybrane.com/api/mcp then codex mcp login vybrane
Your agent acts as you, with your role. It shows up in the Agents tab.

3. Run the jobs

No setup needed: in Claude Code or Codex (connected in step 2), say “Do the Vybrane jobs”. It takes every fix and question your team queued, one by one, until none are left.

Want it to happen with no one asking? A founder sets it up once per repo in Connectors → Coding agent → Run on its own:

In Claude (every hour, one message). Open Claude Code on the web on your repo and send the message Vybrane gives you: it creates an hourly task that takes Vybrane’s jobs. An hour with no jobs stops at the first check.
GitHub (starts in about a minute, ~5 minutes to set up). Install Claude’s GitHub app on your repo. On your computer run claude setup-token and copy the token (starts with sk-ant-oat). In Vybrane tap Make a key. Add both as repository secrets: VYBRANE_KEY and CLAUDE_CODE_OAUTH_TOKEN (or ANTHROPIC_API_KEY). Tap Add it on GitHub to commit the workflow file. The card turns ✓.

4. Fix a bug

From a bug Vybrane found. The morning review checks yesterday’s code and the daily watch checks Sentry, Stripe, Vercel, PostHog and your database. Each problem comes with a Fix button.
From your own words. In Ask or team chat: “ask Claude to fix the login redirect after sign-up”. Add what you know: the error, the page, how to reproduce it.
Before it starts you see what Claude will do, what it can reach, who sees the result, and every line of context it gets. Untick anything it shouldn’t see, then approve.
Claude takes the job, works on a new branch, runs your tests and opens a pull request. The job and its PR link show in the Agents tab and in chat.
Review the pull request and merge it on GitHub, or a founder taps Merge in Vybrane (only when its checks pass).
3 and 7 days later Vybrane checks whether the fix worked and keeps the lesson.

Questions, not changes

“Ask Claude why checkout fails on Safari” reads the code and answers with file and line references. It changes nothing.

Who can ask for fixes

Founders, and the roles a founder allows in Rules → Who can do what (code fixes). Everyone else can still ask questions about the code.

If nothing happens

Job stuck at “waiting”: no one has run the jobs yet. Say “Do the Vybrane jobs” in Claude Code or Codex. If you set up Run on its own, check for its ✓ in Connectors → Coding agent (on GitHub, a missing secret is the usual cause).
Claude can’t see Vybrane: in Claude, open the connector and sign in again.
The GitHub run fails: open the repo’s Actions tab → “Vybrane jobs” for the log. Vybrane restarts missed jobs on its own.

Tools

Tool	What it does	Changes data?
`next_job` Take the next job	Take the next job your team queued in Vybrane.	Records or proposes; nothing goes out without approval
`finish_job` Finish a job	Report a job: a fix job with its pull request link and a short summary; a question job with your answer in report (also a fix job that turned out to be a question or to need no change: no pr_url, your answer in report); or failed with why.	Records or proposes; nothing goes out without approval
`get_context` Get company context	Company context for what you are about to do: the founders' rules, decisions, to-dos and facts that match, relevant team documents, and who works on it.	No (read-only)
`search_memory` Search team memory	Search the team's memory: decisions, to-dos, deadlines, facts and lessons (current ones, with when they were saved).	No (read-only)
`search_docs` Search team documents	Search documents the team uploaded (specs, PDFs, notes, screenshots, user reviews).	No (read-only)
`get_rules` Get the founders' rules	The founders' rules everyone (and every agent) follows at this company.	No (read-only)
`report_back` Report back to the team	Tell the team what you just did or found (shipped a change, found a bug, made a decision while coding).	Records or proposes; nothing goes out without approval
`ask_brain` Ask the Brain	Ask the company's Brain anything, as the person who connected you: what shipped, what was decided, who owns what, and live numbers from the company's own database (sign-ups, trials, active users).	No (read-only)
`ask_founder` Ask a founder	Ask the company’s founders something you need and Vybrane doesn’t know (ask_brain and get_context didn’t answer it): a policy, a preference, a decision, a number nobody recorded.	Records or proposes; nothing goes out without approval
`get_answers` Founders’ answers	Questions asked of the founders: the ones still waiting, and the latest answers.	No (read-only)
`remember` Save to memory	Save something to the team's memory: a decision, fact, lesson, to-do or deadline (it waits in Memory as a suggestion until a founder keeps it).	Records or proposes; nothing goes out without approval
`get_shipped` What shipped	What the team shipped: pull requests merged into the company's repo in the last N days (default 7), with links.	No (read-only)
`get_post_drafts` Post drafts	The Brain's own social post drafts (LinkedIn, X, Reddit), written from real work in the team's voice.	No (read-only)
`propose_post` Propose a post	Propose a post for the founder's own account on X (a post, a thread with parts separated by a line of ---, or a reply: pass reply_to_url), LinkedIn, Threads, or a Reddit draft (pass community, e.g.	Records or proposes; nothing goes out without approval
`propose_email` Propose an email	Propose one personal email (one recipient) from the person's own Gmail or Outlook, e.g.	Records or proposes; nothing goes out without approval
`log_result` Log a result	Record how an approved post or email did, by its proposal id or the post URL: likes, replies, reposts, impressions, clicks, booked (calls booked).	Records or proposes; nothing goes out without approval
`can_post` May I post now?	Call BEFORE every post, reply or comment you make yourself.	No (read-only)
`log_post` Log a post	Record something you just posted yourself (post, reply, comment, quote, DM) with its link, and the person it was to or with (with_handle), so Vybrane remembers what was said and to whom.	Records or proposes; nothing goes out without approval
`find_contact` Look up a person	Everything Vybrane knows about a person before you talk to them again: stage (lead, customer…), notes, and every past post, reply and DM with them.	No (read-only)
`log_contact` Remember a person	Remember a person you found or talked to (a lead, a customer, someone interested): their handle, name, stage and a one-line note.	Records or proposes; nothing goes out without approval
`mark_email_sent` Mark an approved email sent	After you send an email a person approved for you (list_proposals shows it with status "approved" and send_it: true), call this with its id so Vybrane records it as sent.	Records or proposes; nothing goes out without approval
`list_proposals` List proposals	The posts and emails agents proposed in this workspace and what happened to each (waiting, approved, posted, sent, declined), with results.	No (read-only)
`list_jobs` List jobs	The workspace's recent coding jobs and their status (queued, working, PR open, failed).	No (read-only)
`write_posts` Write posts with Vybrane	Have Vybrane write the posts: give it the person's idea in their own words (or a topic).	Records or proposes; nothing goes out without approval
`get_marketing_brief` Today's marketing brief	Marketing agents: call this FIRST every day.	No (read-only)
`get_skills` Get the team's skills	The team's skills: playbooks they added (marketing, SEO, X, LinkedIn, Reddit, engineering…).	No (read-only)

Safety

Your agent acts as you, in the workspace you picked. Fixes arrive as pull requests a person merges. Emails wait for a founder’s Approve unless a founder put emails on autopilot; posts are always published by a person or their own agent. Founders can pause every action at once and see everything in the audit log. Revoke an agent any time in Connectors → Coding agent.

Help

Email founder@findvyb.com. Privacy: vybrane privacy policy.