Skip to main content

MCP Server Integration

Give your AI assistants direct access to your VibeXP data through the Model Context Protocol (MCP), enabling seamless integration with Claude Code, Cursor, and VS Code.

Overview​

VibeXP's MCP server acts as a bridge between your AI development tools and your organized data ecosystem. Your AI assistants can access prompts, artifacts, and memories without manual copy-pasting.

Key Benefits​

  • Direct AI Access: Tools fetch your data automatically
  • No Manual Copying: Seamless workflow integration
  • Secure: Token-based authentication with encryption
  • Real-Time Sync: Always access latest data
  • Multi-Tool Support: Works with Claude Code, Cursor, VS Code

What is MCP?​

Model Context Protocol (MCP) is an open standard that enables AI applications to securely connect to external data sources. It provides a standardized way for AI tools to access contextual information while maintaining strict security controls.

How VibeXP Uses MCP​

VibeXP implements MCP to expose your data as resources and tools:

  • Resources: Read-only access to your prompts, artifacts, and memories
  • Tools: Actions AI can perform (create, search, update data)

Setup Guide​

Prerequisites​

  1. VibeXP Account: Sign up at app.vibexp.io
  2. API Key: Generate from Settings → API Keys
  3. Supported Tool: Claude Code CLI, Cursor IDE, or VS Code

For Claude Code CLI​

Add the VibeXP MCP server:

claude mcp add --transport http vibexp_io_common \
  https://api.vibexp.io/mcp/v1/common \
  --header "Authorization: Bearer YOUR_API_KEY"

Verify the connection:

claude mcp list

For Cursor IDE​

  1. Open Cursor Settings (Cmd/Ctrl + ,)
  2. Search for "MCP Servers"
  3. Add this configuration:
{
  "mcpServers": {
    "vibexp_io_common": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-http"],
      "env": {
        "MCP_HTTP_URL": "https://api.vibexp.io/mcp/v1/common",
        "MCP_HTTP_HEADERS": "Authorization: Bearer YOUR_API_KEY"
      }
    }
  }
}
  1. Restart Cursor

For VS Code​

  1. Install the MCP extension
  2. Open VS Code Settings (Cmd/Ctrl + ,)
  3. Configure MCP Servers:
{
  "mcp.servers": {
    "vibexp_io_common": {
      "url": "https://api.vibexp.io/mcp/v1/common",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}
  1. Reload VS Code

Available Tools​

Once connected, AI assistants can use these tools:

DateTime Tools​

  • vibexp_io_current_date_time: Get current date/time with timezone support

Prompt Management​

  • vibexp_io_search_prompts: Search your prompt library
  • vibexp_io_get_prompt: Retrieve specific prompt by ID

Artifact Management​

  • vibexp_io_create_artifact: Create new artifacts
  • vibexp_io_search_artifacts: Search artifacts by project/content
  • vibexp_io_get_artifact: Retrieve specific artifact
  • vibexp_io_update_artifact: Modify existing artifacts

Memory Operations​

  • vibexp_io_create_memory: Store new memories
  • vibexp_io_search_memories: Search memory library
  • vibexp_io_get_memory: Retrieve specific memory
  • vibexp_io_update_memory: Update existing memories

Usage Examples​

Accessing Prompts​

You: "Use my blog post template to write about AI"

AI: *Automatically searches your prompts for "blog post template"*
    *Retrieves the template using vibexp_io_get_prompt*
    *Applies template with your topic*

Creating Artifacts​

You: "Save this code snippet for later"

AI: *Creates artifact using vibexp_io_create_artifact*
    *Stores in your specified project*
    *Confirms: "Saved to artifacts/code-snippets"*

Using Memories​

You: "Write a function following my coding standards"

AI: *Searches memories using vibexp_io_search_memories*
    *Finds your TypeScript coding preferences*
    *Applies standards automatically in code*

Searching Content​

You: "Show me all my React components"

AI: *Searches artifacts using vibexp_io_search_artifacts*
    *Filters by project and content*
    *Lists matching artifacts with previews*

Common Workflows​

Code Review with Context​

1. AI reads your coding standards (from Memories)
2. Reviews code against standards
3. Saves review as Artifact
4. References previous reviews for consistency

Documentation Generation​

1. AI accesses project specs (from Memories)
2. Reviews existing code (from Artifacts)
3. Generates documentation following template (from Prompts)
4. Saves as new Artifact

Template-Based Content Creation​

1. You request content using a template name
2. AI searches and retrieves template (from Prompts)
3. Fills template with your specific requirements
4. Optionally saves result (to Artifacts)

Security and Privacy​

Authentication​

  • API Key Required: All requests must include valid API key
  • User Isolation: Access only your data, never other users'
  • Secure Storage: Keys stored as SHA-256 hashes

Data Transfer​

  • HTTPS Encryption: All data encrypted in transit (TLS 1.3)
  • No Data Sharing: Your data never shared with third parties
  • Audit Logs: Complete logging of all access

Access Control​

  • Revocable Keys: Delete keys instantly from dashboard
  • Usage Tracking: Monitor when/where keys are used
  • Scope Limiting: Keys access only your VibeXP data

Monitoring and Management​

Usage Dashboard​

Track MCP usage in your VibeXP dashboard:

  • Sessions: View AI tool sessions
  • Tool Calls: Monitor which tools are used
  • Data Access: See accessed prompts/artifacts/memories
  • Performance: Response times and errors

Session Tracking​

For Claude Code CLI specifically:

  1. Navigate to MCP Server → Claude Code Sessions
  2. View all sessions with:
    • Duration and timing
    • Tool usage statistics
    • Hooks triggered
    • Errors and warnings

API Key Management​

  • View Usage: See last used timestamp per key
  • Revoke Access: Delete compromised keys immediately
  • Create Multiple Keys: Separate keys for different tools

Troubleshooting​

Connection Issues​

Problem: "Failed to connect to MCP server"

Solutions:

  • Verify API key is correct and not revoked
  • Check internet connection
  • Ensure tool is properly configured
  • Try regenerating API key

Permission Errors​

Problem: "Unauthorized" or "Invalid API key"

Solutions:

  • Confirm API key in configuration matches dashboard
  • Check for extra spaces or quotes in key
  • Verify key hasn't been revoked
  • Generate new key if necessary

Tool Not Available​

Problem: AI says "I don't have access to that tool"

Solutions:

  • Verify MCP server is properly configured
  • Restart your AI tool
  • Check MCP server is listed in tool settings
  • Confirm API key has necessary permissions

Slow Response Times​

Problem: Queries take too long

Solutions:

  • Check internet connection speed
  • Verify VibeXP service status
  • Try during off-peak hours
  • Contact support if persistent

Best Practices​

API Key Security​

  • Never commit API keys to version control
  • Use environment variables for keys
  • Create separate keys for different environments
  • Rotate keys periodically
  • Revoke unused keys immediately

Data Organization​

  • Keep prompts, artifacts, and memories well-organized
  • Use consistent naming conventions
  • Add descriptive metadata and tags
  • Regular cleanup of outdated content

Tool Usage​

  • Let AI search first before manually specifying
  • Use descriptive project names for better filtering
  • Leverage metadata for enhanced searchability
  • Create artifacts during conversations for future reference

Frequently Asked Questions​

Do I need separate API keys for each tool?​

No, but it's recommended. Use one key per tool/environment for better security and usage tracking.

Can I use MCP offline?​

No. MCP requires internet connection to access your VibeXP data securely.

Is there a rate limit?​

Yes, reasonable rate limits prevent abuse. Contact support if you need higher limits for your use case.

Can I use MCP with other AI models?​

Any tool implementing the MCP protocol can connect. Currently tested with Claude Code, Cursor, and VS Code.

What happens if I revoke an API key?​

All tools using that key immediately lose access. Create and configure a new key to restore access.

Is my data cached by AI tools?​

AI tools may temporarily cache data during sessions, but it's not persisted. Your canonical data always lives in VibeXP.

Support and Resources​