Quick Start
Get started with VibeXP in 5 minutes. This guide will walk you through signing in, setting up your first prompt, and connecting your AI tools.
Step 1: Sign In
Section titled “Step 1: Sign In”- Open your VibeXP instance (the deployed VibeXP app at your own domain)
- On the login page, pick one of the sign-in providers your instance has configured — Google, GitHub, or your organization’s own identity provider (OpenID Connect)
- Complete the provider’s sign-in flow — your VibeXP account is created automatically the first time you sign in
There is no separate signup form, no password to set, and no email verification step — your identity provider handles authentication.
Step 2: Create Your First Prompt
Section titled “Step 2: Create Your First Prompt”Prompts are reusable AI templates that save you time and ensure consistent results.
- Navigate to Prompts in the sidebar
- Click Create New Prompt
- Give your prompt a descriptive title
- Write your prompt template using
{{variable}}syntax for placeholders - Save as Draft or Published
Example Prompt
Section titled “Example Prompt”Write a {{content_type}} about {{topic}} for {{audience}}.
The tone should be {{tone}} and approximately {{word_count}} words.When you use this prompt, you’ll fill in the variables with specific values.
Step 3: Generate an API Key
Section titled “Step 3: Generate an API Key”API keys authenticate the VibeXP CLI and the REST API for programmatic access.
- Go to Settings → API Keys
- Click Create New API Key
- Give it a descriptive name (e.g., “Work Laptop - CLI”)
- Copy and save your API key immediately (it’s only shown once)
Step 4: Connect Your Tools (Optional)
Section titled “Step 4: Connect Your Tools (Optional)”Connect an MCP-OAuth-capable client (such as Claude Code) to access your VibeXP data directly. The MCP endpoint uses OAuth 2.1 — you paste only the URL, and your client runs a one-time browser login. No API key is passed to the MCP endpoint (the API key from Step 3 is for the CLI and REST API, not MCP).
For Claude Code CLI
Section titled “For Claude Code CLI”Add the server with just the URL — Claude Code runs the OAuth login on first use:
claude mcp add --transport http vibexp_io_common \ https://<your-mcp-host>/mcp/v1/commonThe first time the server is used, Claude Code opens VibeXP’s consent page in your browser — if you’re not already signed in to VibeXP, you’ll sign in first and be returned to the consent screen. Approve it once, and Claude Code reconnects automatically afterward.
For Other Clients
Section titled “For Other Clients”Paste only the connection URL into your MCP client:
https://<your-mcp-host>/mcp/v1/commonIf your client supports the MCP OAuth 2.1 flow, it will send you to VibeXP’s login and consent screen and then connect. If it does not support MCP OAuth, it cannot currently connect — the endpoint rejects API-key authentication with 401. See MCP Server Integration for how the connect flow works.
Step 5: Start Creating
Section titled “Step 5: Start Creating”You’re all set! Here’s what you can do next:
- Create More Prompts: Build your personal prompt library
- Store Artifacts: Save AI-generated code, docs, and reports
- Add Memories: Store project context and preferences
- Connect Agents: Integrate A2A-compatible AI agents
Working with a team? Members can comment on artifacts, memories, prompts, and blueprints, and team access is governed by roles and permissions.
Core Concepts
Section titled “Core Concepts”Prompts
Section titled “Prompts”Reusable templates with variable placeholders that save time and ensure consistency.
Artifacts
Section titled “Artifacts”Substantial AI-generated content (code, docs, reports) organized by project with powerful search.
Memories
Section titled “Memories”Context snippets that AI tools automatically reference in conversations, eliminating repetition.
MCP Integration
Section titled “MCP Integration”Direct connection between AI tools and your VibeXP data for seamless workflows.