Integrations›Connect WyberAi to Claude (MCP)

Connect WyberAi to Claude (MCP)

WyberAi ships a remote MCP (Model Context Protocol) server. Connect it to Claude, Claude Code, Cursor, or any MCP client, and your assistant can create WyberAi projects, build and iterate on apps, and publish them to live URLs — using your account and your credits.

What you'll need

A WyberAi account (free tier works — 50 credits included)
A WyberAi API key — created in Settings → API Keys

Server details

Endpoint: https://wyberai.com/api/mcp · Transport: Streamable HTTP (stateless, no SSE session required) · Auth: your API key, sent as either an x-api-key header or Authorization: Bearer token. Keys look like wyb_… and are stored hashed — treat them like passwords and rotate them from Settings → API Keys anytime.

Connect from Claude Code

claude mcp add --transport http wyberai https://wyberai.com/api/mcp --header "x-api-key: wyb_YOUR_KEY"

Connect from Claude.ai

1
Create an API key
In WyberAi, open Settings → API Keys and create a key. Copy it — it is shown only once.
2
Add a custom connector
In Claude, go to Settings → Connectors → Add custom connector, enter https://wyberai.com/api/mcp, and supply your API key when asked for credentials.
3
Build from chat
Ask Claude to "create a waitlist app on WyberAi and publish it". It will chain create_project → send_message → get_message_status → publish_project.

Available tools

get_accountRead-onlyYour remaining credits and plan.

list_projectsRead-onlyList the projects in your workspace.

get_projectRead-onlyDetails of one project, including file count and published URL.

list_filesRead-onlyList the file paths in a project.

read_fileRead-onlyRead the source of one file in a project.

get_message_statusRead-onlyPoll a queued build: queued → processing → done | error.

get_project_knowledgeRead-onlyRead a project’s persistent knowledge (brand, standards, patterns).

get_database_statusRead-onlyWhether the project has a Supabase database connected.

list_versionsRead-onlyList saved project versions (snapshots).

run_security_scanRead-only · securityRLS attacker-view scan of the connected database — finds tables that leak data.

list_connectorsRead-onlyBrowse 250+ connectors (Gmail, Notion, Linear, Slack…) to wire in.

create_projectWriteCreate a new project (react-vite, next, vue, or vanilla).

send_messageWrite · uses creditsQueue a build or change. Runs asynchronously; can rewrite existing project files.

set_project_knowledgeWriteSet persistent knowledge the builder applies on every future build.

rename_projectWriteRename a project.

duplicate_projectWriteCopy a project’s files into a new project.

restore_versionWriteRoll a project back to a saved version.

execute_sqlWrite · databaseRun SQL on the project’s connected Supabase (reads, writes, schema).

delete_projectWrite · destructivePermanently delete a project. Cannot be undone.

publish_projectWrite · publicPublish the project to a live public URL. Republishing replaces the live version.

Billing, limits & availability

Builds queued via send_message consume credits from the connected WyberAi account at the same rates as building in the web editor (see how credits work). Listing, reading, and status tools are free. Builds run asynchronously and typically finish in under two minutes. The service is available globally wherever WyberAi operates.

Privacy & support

The MCP server only accesses projects owned by the API key's account, and never reads your Claude conversation — it sees only the tool calls Claude makes. See our privacy policy. Questions or issues: hello@wyberai.com or the in-app support chat.

Note: Treat your API key like a password. Anyone holding it can build with your credits and publish under your account — revoke keys immediately from Settings → API Keys if one leaks.