Claude connector

Connect Claude to Byblos AI

The Byblos AI connector is for founders and developers who work in Claude or Claude Code: it brings your Byblos AI workspace into Claude through the Model Context Protocol (MCP). Sign in, choose its permissions, and Claude can read your projects, PRD, roadmap and brand guidelines and make the changes you allowed, under the app’s role and plan checks.

Server URL

https://byblosai.app/api/byblosai/mcp

Before you start

Byblos AI
Any account, Free included. There is nothing to request or install. Some tools need a feature from your plan, or from the project owner’s plan, and say so when it is missing.
Claude
Any plan: Free, Pro, Max, Team or Enterprise. A Free Claude account can hold one custom connector at a time.
Claude Team or Enterprise
An organization Owner adds the connector once, in Organization settings → Connectors. Each member then connects it to their own Byblos AI account.

What the connector does

  • Read what you can open in Byblos AI: Product Manager projects and documents, campaign posts, settings, metrics and agent chats, brand profiles and artifacts, website overviews, tasks, uploaded documents and project images, calendar and bookings, inbox and notifications, support cases, feedback, expert reviews, and your usage.
  • Search across your workspace, on plans that include workspace search, with each result linking to the item in Byblos AI.
  • Work through a project in co-founder mode, on the same plans: Claude asks Byblos AI for the next action, does it with you, and Byblos AI checks the project before it counts the action as done.
  • Make the changes your write permissions allow, as you: draft and edit campaign posts, change their review status, move already-scheduled posts and change campaign settings; generate, edit, approve and revoke Product Manager and brand content, including a brand import from a public website; create and update tasks; book meetings; update your profile; file feedback and support cases; and request expert reviews from your review allowance.
  • With the separate Create projects permission, create new projects you own, with the name you give. Each one uses a slot in your plan's project allowance; it can't delete projects or spend AI credits. Existing connections need that additional approval.
  • Act only as you. Every call runs the same project membership, role and plan checks as the app, and anything you cannot open answers “not found”.

How an AI assistant connects to Byblos AI through MCP

Claude, Claude Code, ChatGPT or another MCP client connects to Byblos AI, you sign in and approve its permissions, every call passes the same role and plan checks as the app, and the assistant works with the projects you can access, but never secret values or first-time publishing.

Diagram, not a product screenshot: the Byblos AI MCP connection. You can revoke a connection from Connected apps in your account.

Connect

You sign in with your existing Byblos AI account and choose which permissions to give. There is no client ID, client secret or API key to enter.

Connect Byblos AI to Claude

Add Byblos AI as a custom connector in Claude. Connectors belong to your Claude account, so it is also there in Claude Desktop.

  1. Open Customize → Connectors. In Claude, open Customize and then Connectors. Choose +, then Add custom connector.
  2. Paste your workspace address. Give it a name you will recognise, paste the URL above into the URL field and choose Continue. On the next screen keep the detected defaults (Authentication: Always required; OAuth client: Anthropic’s hosted client metadata). There is no client ID or secret to enter.
  3. Connect and approve. Finish adding it and choose Connect, sign in with your existing Byblos AI account, tick the permissions you want to give it, and approve. In a chat, switch Byblos AI on from + and then Connectors.

On a Claude Team or Enterprise plan, an organization Owner first adds Byblos AI in Organization settings → Connectors (Add, then Custom, then Web); each member then chooses Connect on it in Customize → Connectors. A Free Claude account holds one custom connector at a time. Using Claude Desktop? Connectors belong to your Claude account, so one added on claude.ai is already there in Desktop, and one added in Desktop is on claude.ai.

Open Claude connectors

Connect Byblos AI to Claude Code

Add the server once from your terminal, then sign in from inside a session.

  1. Add the server. Run this in your terminal. It registers the workspace as byblosai for every project on this computer.
    claude mcp add --transport http --scope user byblosai https://byblosai.app/api/byblosai/mcp
  2. Sign in from a session. Start Claude Code, run /mcp, pick byblosai and choose Authenticate. A browser tab opens on the Byblos AI consent page; if it does not, open the link Claude Code shows.
  3. Approve and return. Tick the permissions you want to give it and approve, then go back to the terminal. Running claude mcp list now shows byblosai as connected.

Try asking

Once connected, ask in your own words. A few to start with:

  • “What projects do I have in Byblos AI?”
  • “Start co-founder mode on my project”
  • “What campaign drafts do I have for next week?”
  • “What's on my calendar this week?”
  • “How much of my monthly allowance is left?”

Permissions

Reading is always included. Every other permission is optional: you tick it on the Byblos AI consent screen, and a connection only sees the tools its permissions cover. These are the sentences the consent screen shows.

Read workspace data

  • Read workspace data

    Read your projects, Product Manager documents, campaigns, brand, website overviews, tasks, files, calendar and bookings, inbox and notifications, support cases, feedback, expert reviews, profile and usage, and search across them(byblosai:read)Always included

    Read

Actions and manage access

  • Product Manager content

    Create, edit and generate Product Manager project content, suggest roadmap features and update roadmap delivery status on your behalf. Approve, record phase decisions, revoke approvals or promote drafts only within the permissions you explicitly grant; otherwise request confirmation in Byblos AI.(byblosai:sypm:write)Optional

    Manage
  • Brand identity

    Import, generate and replace brand identity content on your behalf. Approve or revoke approvals only within the permissions you explicitly grant; otherwise request confirmation in Byblos AI.(byblosai:brand:write)Optional

    Manage
  • Campaign drafts and settings

    Create and edit campaign drafts, approve review states, move scheduled posts, change campaign settings, and confirm creation, editing or deletion of Campaign-local steering notes on your behalf(byblosai:campaign:write)Optional

    Manage
  • Tasks and action results

    Create, assign and update authorized tasks, and record co-founder action results, on your behalf(byblosai:tasks:write)Optional

    Manage
  • Profile, support and expert reviews

    Update your profile, file feedback and support cases, mark notifications read, and request or cancel expert reviews using your review allowance(byblosai:self:write)Optional

    Manage
  • Calendar and bookings

    Book meetings and RSVP for you, and ask you to approve moving or cancelling them(byblosai:calendar:write)Optional

    Manage
  • Inbox messages

    Send Inbox messages to active project members only after you approve the recipients and body for each send; recipients may receive email notifications(byblosai:inbox:write)Optional

    Manage
  • Create projects

    Create new projects you own, with the name you give. Each one uses a slot in your plan's project allowance. This can't delete projects or spend AI credits.(byblosai:projects:create)Optional

    Manage

What stays in the Byblos AI app

  • Publishing campaign posts, scheduling a post for the first time, and deleting posts.
  • AI image generation, and editing or deleting images.
  • Payments, billing and plan changes.
  • Inviting members, changing roles, and deleting projects.
  • Connecting social media and calendar accounts.
  • Uploading files and brand assets.
  • Anything in the Secrets Manager.

Disconnect and revoke

In Byblos AI
Open Account → Connected apps and choose Revoke on the app. That ends the approval, its refresh token and every access token issued from it, and the app’s next call fails, whichever client it is.
In Claude
Open Customize → Connectors, find Byblos AI and remove it. On Team and Enterprise plans only an Owner can remove it from the organization, in Organization settings → Connectors; revoking in Byblos AI ends your own connection either way.
In Claude Code
Remove the server with this command, or choose Clear authentication for byblosai in /mcp to sign out and keep the server.
claude mcp remove byblosai

If something goes wrong

The app cannot reach the server
Check the address matches the one above exactly, including the path. A trailing slash or a missing path is the usual cause.
The sign-in window never opened
Your browser most likely blocked the pop-up. Allow pop-ups for the app and start the connection again.
It connected but is not in the tools menu
Most clients need the connection switched on for the conversation you are in. In Claude, choose + in the message box, then Connectors, and turn Byblos AI on.
It is missing a permission it needs
Permissions are fixed when you approve, so they cannot be added later. Revoke the app in Account → Connected apps, connect it again, and tick the permission you need on the consent page.

Your data

What Byblos AI receives
Only the arguments Claude sends to a tool, such as a project or the text of a draft you asked for. Your conversations with Claude are never sent.
Changes
Anything a connection changes is saved to your workspace exactly as if you had made it in the app, and kept on the same terms.
Call log
Each call records the tool, your user id, whether it succeeded, how long it took, a failure code and a masked credential prefix, never what the call read or wrote. It is deleted automatically after 30 days. A feedback report you file through the connection keeps a copy of your calls from the 30 minutes before it, for as long as the report exists.
Usage
Calls count toward your plan’s usage allowances, the same as the matching actions in the app. Hourly activity counts per module are kept for 180 days.
Connection records
Each app you approve, the permissions you gave it, and when you approved it and last used it. After you revoke an app, its record stays, marked revoked, as your approval history.
Security log
Approvals, refusals, token issues and refreshes, and revocations, each with the app, your user id, a masked credential prefix and a shortened network address (the first three parts of an IPv4 address, or the first four groups of an IPv6 address). It is not deleted automatically.
Sign-in tokens
Access tokens last one hour and refresh tokens 30 days. Only a one-way hash of each is stored, and expired ones are deleted automatically.
Other services
Some tools use the same outside services as the app: AI model providers when a tool generates content, calendar invitations and email when you book a meeting, and the public website you name in a brand import.

Questions about the connector

Which Byblos AI plan do I need for the connector?

Any Byblos AI account works, Free included, and there is nothing to request or install. Some tools need a feature from your plan, or from the project owner’s plan, and say so when it is missing: workspace search and co-founder mode run only on plans that include workspace search. On the Claude side, any plan can add the connector.

Can Claude publish posts or change billing in Byblos AI?

No. First-time campaign scheduling, publishing, deletion, billing, plan changes, invitations and Secrets Manager stay in the app. Claude can draft and edit allowed content. Product Manager and Brand approvals, phase decisions, revocations and promotion over approved content require separate project, connection and operation permissions; otherwise Claude requests app confirmation. Discarding Product Manager changes never restores approval. Calls count toward your usage allowances.

Does Byblos AI see my Claude conversations?

No. Byblos AI receives only the arguments Claude sends to a tool, such as a project or the text of a draft you asked for. Each call is logged with the tool, your user id, the outcome and a masked credential prefix, never what the call read or wrote, and that log is deleted automatically after 30 days.

How do I disconnect Claude from Byblos AI?

In Byblos AI, open Account → Connected apps and choose Revoke on the app: the approval, its refresh token and every access token issued from it end, and the next call fails. You can also remove Byblos AI in Claude under Customize → Connectors, or remove the server from Claude Code with its remove command.

New to Byblos AI?

Create a free account, start a project with Product Manager research and a PRD, then connect Claude to work with it. Paid plans add the full brand and campaign workflow for Claude to read and draft in.

Start freeFree plan · No credit card required

Support, privacy and terms

Cookies, your way

Required cookies keep the platform working. Optional ones stay off unless you choose otherwise.