Your career,
in Claude.
Set up your connection
Open connector settings
In Claude, go to Settings, then Connectors, then add a custom connector.
Paste the Tabbio server address
Give the connector a name you will recognise, then paste this address.
Server URL
https://server.tabbio.com/api/mcpApprove access
Claude opens the Tabbio approval screen in your browser. Sign in and approve to finish.
Your client stores a short-lived token and refreshes it on its own. You never handle it, and you can revoke access from Tabbio settings at any time.
Claude documentationWhat your AI can do
The Tabbio MCP server exposes 162 tools. Your AI reads structured career data, not a PDF it has to guess at.
See what you can doYour CV and profile
Read your CV, work history and skills as structured data. Rewrite a summary, or tailor the whole CV for a role.
cvListcvTailorcvExportprofileGetJobs and applications
Run the job search from your chat. Search the same catalog the app shows, from Google Jobs to partner ATS boards, then prepare and track applications.
catalogJobSearchcatalogApplyPrepareapplicationTrackCareer memory
Your AI recalls what it learned last time. Memory access is per client, so you can cut one off without touching the others.
recallMemoryaddMemorymemoryGraphGetSkills and connected tools
Run Agent Skills on a CV, check your automations, and queue an email or Slack message through the tools you connected.
skillRunnovaListsendEmaillistConnectedServices
Things to ask once you connect
Copy a prompt into your connected AI client, or use it inside tabbio chat after signing in with your browser or email.
Find your next role
Find product roles in Dubai that fit my CV.
Make your CV fit
Tailor my CV for this job description and show me what changed.
Keep track of applications
What have I applied to this month, and where did each one get to?
Get a CV ready to share
Export my CV as a PDF and give me the link.
Keep your preferences
Remember that I am only looking at hybrid roles in the UAE.
Follow up with confidence
Draft a follow-up to the recruiter on that Riyadh role.
What you can do from the terminal
The CLI reaches the same 162 tools as the Tabbio MCP server, plus chat, approvals and output your scripts can read.
Get started in three stepstabbio
Your terminal workspace
Your account, recent chats and shortcuts to tools and approvals, together in the Tabbio CLI home screen.
Every tool is a command
Each tool becomes a command such as
tabbio cv list, with flags built from the tool's own schema. Browse them in an interactive list, or print one tool's flags withtabbio tools describe.cv listcatalog job-searchprofile updatecv tailorChat with the Tabbio agent
tabbio chatstreams the answer as it is written, shows each tool the agent calls and keeps your threads. Slash commands switch mode, model and thread, and, where your account has them, turn on web research, images, or an answer as a document, slides or a page.tabbio chat/threads/research on--result documentApprove in the terminal
Actions that send, share, publish or delete stop for your approval. The CLI shows the tool and its arguments, and you approve, reject or leave it pending.
--yesapproves only what that one command created.approvalsapprovals approveapprovals wait--yesScripts and CI
--jsonprints a stable envelope with a schema version. Piped output becomes tab-separated rows, exit codes say what happened, andTABBIO_TOKENsigns a job in without writing anything to disk.--json--fieldsTABBIO_TOKENhelp exit-codesA bridge for MCP clients
Some MCP clients only start local servers.
tabbio mcp servespeaks MCP over stdin and stdout and forwards every call to Tabbio with your CLI sign-in. Clients that support remote servers can taketabbio mcp urlinstead.mcp servemcp urlOne sign-in, three ways
Approve the computer in your browser, use a code sent by email over SSH, or bring a personal token for CI. Credentials sit in a file only you can read (mode 0600), tokens are never printed,
tabbio logoutends the session, and approvals still apply.loginlogin --emaillogin --with-tokenlogout
Get started in three steps
You need Node.js 20 or newer and a Tabbio account. The free plan is enough.
Install
Install the
tabbiocommand, or run it once with npx.npm
npm i -g @tabbio-technologies/clinpx
npx @tabbio-technologies/cliSign in
tabbio loginopens your browser to approve this computer. On a server, add--emailto get a code by email. In CI, setTABBIO_TOKENinstead.Browser sign-in
tabbio loginEmail sign-in
tabbio login --email you@example.comPersonal token
tabbio login --with-tokenEnvironment variable (scripts)
export TABBIO_TOKEN=tabbio_mcp_...Run
List your CVs, search the job catalog as JSON, or open a chat.
Terminal
tabbio cv list tabbio catalog job-search --query "designer" --json tabbio chat
Something off? tabbio doctor checks your setup and says what to fix.
How the Tabbio CLI looks
Real frames from the CLI, captured on a test account.
tabbio tools
Tool browser
tabbio toolsgroups every tool, marks each one read or write, and shows its flags and an example beside the list.tabbio chat
Chat
A short answer from the Tabbio agent, with one line for each tool it called and how long it took.
tabbio chat --research on
Research
With research on, the agent searches the web and lists its sources after the answer.
tabbio cv list
CV list
tabbio cv listprints a table in a terminal. Add--jsonfor every field.tabbio doctor
Doctor
tabbio doctorchecks Node.js, the credentials file, the API, your session, the clock and the MCP catalog.app.tabbio.com/cli/connect
Browser sign-in
tabbio loginopens this page. It shows the account, the computer and the local address the one-time code goes to.tabbio run cv.tailor
Out of credits
When the daily pool is spent, a paid tool is refused before it runs, with the cost, what is left and when the pool refills.
Connect a local MCP client
For clients that launch a local server, sign in to the CLI first, then add this configuration. The bridge forwards calls to the same remote Tabbio MCP server.
JSON
{
"mcpServers": {
"tabbio": {
"command": "npx",
"args": [
"-y",
"@tabbio-technologies/cli",
"mcp",
"serve"
]
}
}
}Made for automation
Every command has a plain-text path for pipes and CI. Without a terminal, or with CI set, the CLI never draws its interactive screens and never prompts.
Exit codes
- 0
- Success
- 1
- Unexpected error
- 2
- Usage error, such as a missing flag
- 3
- Not signed in
- 4
- Not allowed by token scope, plan or credits
- 5
- Not found
- 6
- Waiting for approval
- 7
- Network error
- 8
- Server error
- 130
- Interrupted with Ctrl+C
tabbio cv list --json
{
"data": {
"cvs": [
{
"id": "cv_seeker_1_primary",
"title": "Amina Noor - Product Design",
"isPublic": true,
"updatedAt": "2026-08-01T09:12:44.000Z"
}
],
"defaultCvId": "cv_seeker_1_primary",
"total": 19
},
"meta": {
"schemaVersion": 1,
"tool": "cv.list",
"durationMs": 31
}
}Output of tabbio cv list --json, trimmed to one CV. Within a schema version, fields are only added, never renamed or removed.
Use Tabbio in GitHub Actions
Store a personal token as the TABBIO_TOKEN repository secret. Token access is limited to its tool scopes; chat and approving actions require a browser or email sign-in.
GitHub Actions
- run: npx -y @tabbio-technologies/cli run cv.list --json > cvs.json
env:
TABBIO_TOKEN: ${{ secrets.TABBIO_TOKEN }}Works where you work
macOS
Node.js 20 or newer, in any terminal.
Linux
Desktops, servers and containers. Sign in over SSH with a code sent by email.
Windows
Node.js 20 or newer. The credentials file relies on your Windows user profile's permissions.
CI
Set TABBIO_TOKEN from your secrets. No prompts and no interactive screens.
You stay in control
Access is scoped, revocable and logged. Actions that send, share, publish or delete require your approval.
Two scopes
- mcp:read
Read your CV, profile, jobs and memory. Nothing changes.
- mcp:write
Create and update things, like a tailored CV, an application draft or a memory.
A token with read scope alone cannot write. Employer tools stay out of reach for personal tokens.
Approval before anything leaves
57 actions pause for approval, including submitting an application, sharing your CV, sending a message and deleting data. Approve in the Tabbio app, or in the CLI with a browser or email sign-in. Personal tokens cannot approve actions. The CLI’s --yes flag approves only actions created by that command.
- Sign-in happens in your browser. Your password never passes through the AI client.
- Every call is logged with the client that made it, so you can see what your AI did.
- Connected tools are queued by Tabbio. Your MCP token never reaches Gmail or Slack.
- Deleted memories keep a 30-day undo, and revoking a client ends its access right away.
Free to start
Free accounts get a daily credit pool, the same one the app draws from. Chat replies and AI tools such as CV tailoring spend it, and most tools make no AI call and cost nothing.
CLI and MCP questions
- MCP is the Model Context Protocol, an open standard for connecting AI clients to outside tools and data. An MCP server exposes a set of tools the AI can call. Tabbio runs a remote one, so there is nothing to install: you paste an address into your client, approve access once, and your AI can work with your CV, the job catalog and your applications.
- A remote MCP server that gives your AI client access to your Tabbio account: your CV, the job catalog, your applications and your career memory. Connect it once and your AI can use those tools in any chat.
- A command-line client for your Tabbio account. It turns every tool on the Tabbio MCP server into a command, streams chat with the Tabbio agent, lets you approve actions in the terminal and prints JSON for scripts. It runs anywhere Node.js 20 or newer does.
- The MCP server connects another AI client to your account. Tabbio CLI is for you and your scripts at a terminal, with the same tools plus streaming chat and approvals when signed in with your browser or email. It also bridges clients that only start local servers with
tabbio mcp serve. Both setup paths are in this guide. - Follow the setup instructions for Claude, ChatGPT, Claude Code, Cursor, Gemini CLI, Grok or Perplexity. Tabbio CLI also connects to the same server and can bridge clients that require a local stdio server.
- You need a Tabbio account, and the free plan is enough. You approve the first sign-in in your browser, then the CLI works on its own. It uses the same account, data and limits as the app, so a CV you change in the terminal is the same CV in the app.
- No. Connecting is free and most tools work on the free plan. A few need an upgrade: DOCX, TXT and Markdown exports need Plus or Pro, authoring your own Agent Skill needs Plus, and automations need Pro.
- It keeps one sign-in per profile in a credentials file only your user can read (mode 0600, in a folder set to 0700). It never prints tokens, and debug output and errors redact them.
tabbio logoutends the session on the server, and if you lose the computer, changing your password signs out every device at once. It sends no telemetry, and apart from a daily check for a new version on npm, which you can turn off, it only talks to Tabbio. - Yes. Run
tabbio login --with-tokenand paste a token from Settings, then MCP access, or setTABBIO_TOKEN. A token reaches the tools within its scope, while chat and approving actions need a browser or email sign-in. The CLI never creates a token itself, so it cannot replace the one another client uses. - No. Submitting an application waits for your approval in the Tabbio app, or in the CLI with a browser or email sign-in.
- Anything hard to undo or that reaches other people, such as deleting, submitting or withdrawing an application, sending a message or email, sharing a CV, publishing and starting automations. The CLI shows the tool and its arguments and waits.
--yesapproves only the actions that one command created, and only with a full sign-in. Nothing approves a whole session for you. - Only your own account data, and only what the scope allows. A read-only token cannot change anything, and employer tools stay out of reach for personal tokens.
- For an MCP client, open Settings, then MCP access, and revoke the client or its token. You can revoke one client’s memory access without touching the others. For a CLI app session, run tabbio logout; changing your password signs out all devices.
- Yes. Store a personal token as a CI secret, expose it as
TABBIO_TOKENand add--json. With CI set, the CLI never prompts or draws its interactive screens, and exit codes tell your script what happened. Code 6 means an action is waiting for approval, and 4 means a scope, plan or credit limit.
