Export & Integration Guide

Seamlessly export your specifications to any AI builder platform

Export Overview

Xpec specifications are designed to work perfectly with all major AI development platforms. Each export format includes the specific context and structure that platform needs to generate accurate, production-ready code.

Available Export Methods

Direct Integration

Real-time access via APIs and protocols

• Claude Code (MCP): Specifications appear in Claude's context
• v0 Platform: Direct push to v0 with one click
• API Access: RESTful API for custom integrations
• Webhooks: Real-time updates when specs change

Copy & Paste

Formatted exports for manual use

• Markdown: Universal format for any AI builder
• Structured Text: Optimized for Lovable and Bolt
• JSON: Machine-readable format for automation
• PDF: Human-readable documentation

Platform-Specific Exports

Claude Code Integration (MCP)

Direct access via Model Context Protocol

How It Works

Your specifications automatically appear in Claude Code's context through our MCP server. No manual copying needed - Claude can see and reference your specs in real-time.

Setup Steps

Generate an API key in your Xpec workspace settings
Install and configure the Xpec MCP server
Your specifications are now available in Claude Code's context

# Install MCP server
npm install -g @xpec/mcp-server
# Configure in claude_desktop_config.json
{
"mcpServers": {
  "xpec": {
    "command": "xpec-mcp-server",
    "args": ["--api-key", "your-api-key", "--workspace", "workspace-id"]
  }
}
}

What Claude Code Can Do

• Access all your specifications and project context
• Generate code that matches your established patterns
• Reference your technical stack and constraints
• Understand your business logic and requirements

Custom Integration Options

REST API Access

Build custom integrations using our REST API. Perfect for internal tools, CI/CD pipelines, or custom AI workflows.

GET /api/mcp/{workspaceId}/specs
GET /api/mcp/{workspaceId}/specs/{specId}
POST /api/mcp/{workspaceId}/validate
Authorization: Bearer {api-key}

Webhook Notifications

Get real-time notifications when specifications are created, updated, or published. Ideal for automated workflows and team notifications.

{
"event": "spec.updated",
"spec": {
  "id": "spec_123",
  "title": "User Authentication",
  "status": "ready"
},
"timestamp": "2024-01-15T10:30:00Z"
}

Export Best Practices

Before Export

• Review specification completeness
• Verify technical stack details
• Check acceptance criteria
• Validate data models
• Test with personas if available

Choose Right Platform

• v0: UI/UX focused projects
• Claude Code: Complex logic and architecture
• Lovable: Full-stack applications
• Bolt: Complete development environments

After Generation

• Review generated code quality
• Test all specified functionality
• Verify edge case handling
• Check accessibility compliance
• Validate performance requirements

Troubleshooting Common Issues

AI Generated Unexpected Code

Possible causes:

Specification lacks technical stack context
Business logic is ambiguous or incomplete
Edge cases and error handling not specified
Missing validation rules and constraints

Solution:

Return to Xpec, add missing context using our best practices guide, then re-export.

MCP Integration Not Working

Common fixes:

Verify API key is correctly configured
Check workspace ID in configuration
Restart Claude Code after configuration changes
Ensure MCP server is latest version

Export & Integration