Connect your first project

Start in the SpecViber app and open the setup guide. It walks you through every step, so there is nothing to remember: the local client, the AI client configuration and the setup prompt.

1. Point out your projectName the workspace, choose its organization when more than one is available, and choose the folder you open in your AI coding client.
2. Install the local SpecViber clientThe client and its MCP server run on your computer and keep your files there. The guide gives you the download, and your AI helps with the local setup.
3. Connect your AI and startOne click configures your AI coding clients. A setup prompt then lets your AI finish the job inside your project.
Create the workspace first. You do not need to decide between downloading and creating a workspace. Download is step 2 of the guided journey.

1. Create the workspace

  1. Open the SpecViber app and sign in.
  2. If you have no workspaces, choose Start the setup guide.
  3. Choose new or existing project, enter a workspace name, and add your project folder.
  4. Select Create workspace and continue.

The project folder is the repo you open in VS Code, Codex, Claude Code, or another AI coding client. It is not the folder where the SpecViber client is unpacked.

2. Install or detect the local client

Your browser asks for permission first. Chrome and Edge show a prompt such as "app.specviber.com wants to access other apps and services on this device" the first time the app reaches http://localhost. Choose Allow. That permission is what lets the web app talk to the SpecViber client on your own computer, and that connection stays on your machine. If you block it, the guide cannot find the client until you allow it again in the site settings (the icon left of the address bar) and reload.

The post-create dialog checks for an existing local client. If it is missing, use the download button in that dialog, extract the ZIP under your local PHP web root, and install the MCP server dependencies:

cd specviber_saas_client/mcp-server
npm install

Start the local web server and choose Check again. The dialog also verifies Node.js and the MCP npm dependencies, and continues only when the local runtime is ready.

Make it start with Windows. So the server is up again after a reboot without you starting it by hand, let your AI install XAMPP's Apache as an auto-starting Windows service, or enable it yourself from the XAMPP Control Panel. If SpecViber later cannot reach the client, start XAMPP/Apache and choose Check again.

When you later reopen Setup, SpecViber checks the workspace's saved local URL and existing client registrations. Completed steps 1–2 stay completed, so the guide resumes at MCP activation instead of restarting foundation setup.

3. Configure supported AI clients locally

Choose Generate token & configure locally. This one action creates the workspace credential and updates SpecViber's entries in .vscode/mcp.json, .mcp.json, and .codex/config.toml while preserving other servers and settings.

No token is created merely by opening or resuming the guide. The new credential is sent directly to the loopback content API; it is never displayed, copied to the clipboard, or included in the setup prompt.

The local client verifies Node.js 18+ and writes its absolute executable path, so the server does not depend on an editor inheriting a recently changed PATH.

4. Activate and verify the MCP server

5. Run the prompt in a new chat

Confirm the MCP connection in the SpecViber dialog to unlock the prompt. Copy it into the new, otherwise empty chat where you verified the server. Do not continue the chat that prepared the web/PHP/Node foundation.

The credential-free prompt verifies the MCP connection, scans project files, installs the current SpecViber instructions and skills, and sets up classification.

5. Last step: add the VS Code extension

The setup guide and the prompt do not cover this, so remember it yourself. If you use VS Code, install the SpecViber extension from the Marketplace after the guide is done. It reads the same .vscode/mcp.json the guide wrote, so after Developer: Reload Window it shows your workspace in the sidebar without any further settings.

Joining a workspace your team already set up

If someone in your organization has already connected the project, you do not create a workspace, run a setup prompt or classify anything. The workspace, its documents and the project's SpecViber instructions already exist.

  1. Accept the invitation and open the SpecViber app. The team's workspace is in your workspace list.
  2. Choose Setup guide on the workspace, or Continue setup in the app banner.
  3. Clone the project and enter its folder. Clone the repository and pull the latest version, then enter the local folder of your clone in the guide and save it. When the workspace has a shared GitHub source, the guide shows the git clone line.
  4. Complete steps 2–4 above on your computer. Your clone does not contain the MCP configuration, because those files hold your personal workspace token, so the configure step writes your own.
  5. Check the clone and start working. No prompt is needed. The guide notices when your AI client starts SpecViber, then checks your clone on this machine: its Git state, that the project's SpecViber instructions belong to this workspace, and that a registered document opens from the folder. Then open a new chat in the project and ask, for example, Show my SpecViber tasks.

You do not need to scan a fresh clone: its documents are already registered.

Read-only on another device. If the local client or project folder is not available and the workspace has a shared Git source, SpecViber asks whether to show documents read-only from Git or configure local editing. For a private repository, install the SpecViber GitHub App and select that repository, then connect your GitHub account. If the account is connected but repository access is missing, choose Install / choose repositories and then Try again. The access-mode answer is saved only for this account, workspace and browser. A reachable local project always takes priority. Change or reset the choice under Manage workspaces → Edit.

Working across organizations

If your workspaces span multiple organizations, the workspace menu groups them by organization and workspace cards show the organization name. When you can create workspaces in more than one organization, the create form asks which organization should own the new workspace. Your latest workspace becomes the default in a new tab; a URL with workspace_id still takes priority, and a workspace you can no longer access is never restored.

Need to resume?

Open Manage workspaces and choose Setup on the workspace. If document content is disconnected, use Continue setup in the app banner.

Open SpecViber Open downloads