Stop Fighting Documentation Context Switches While Coding

Your AI assistant gives you generic answers because it doesn't know your product. You're constantly alt-tabbing between your IDE and docs, breaking flow every time you need to check an API endpoint or integration pattern.

The Biel MCP Server connects your AI coding tools directly to your product documentation, turning generic assistants into product-aware coding partners.

Your AI Tools Get Smarter, Not Just Faster

Instead of generating boilerplate code that might work, your AI assistant now references your actual API specs, authentication patterns, and integration examples. Ask "What are the required headers for the /users endpoint?" and get your exact API documentation, not a best guess.

This isn't about adding another tool to your stack—it's about making the tools you already use significantly more useful.

Real Productivity Gains

Skip the documentation hunt: Your AI assistant knows your product's authentication flow, error codes, and edge cases. No more digging through docs to understand why your integration isn't working.

Accurate code completions: When Cursor or VS Code suggests code, it's based on your actual API patterns and naming conventions, not generic examples from training data.

Onboarding acceleration: New team members get context-aware help instead of generic Stack Overflow answers. The AI can walk them through your specific setup patterns and configuration requirements.

Works Where You Already Code

Drop a single JSON configuration into Claude Desktop, Cursor, or VS Code. Your AI assistant immediately gains access to your documentation without changing your existing workflow.

{
  "mcpServers": {
    "biel-ai": {
      "description": "Query your product's documentation, APIs, and knowledge base.",
      "command": "npx",
      "args": [
        "mcp-remote", 
        "https://mcp.biel.ai/sse?project_slug=YOUR_PROJECT_SLUG&domain=https://your-docs-domain.com"
      ]
    }
  }
}

Then ask questions like:

• "Show me the authentication headers for our payment API"
• "What's the retry logic for failed webhook deliveries?"
• "How do I configure rate limiting for the analytics endpoint?"

Your AI assistant pulls answers directly from your documentation instead of hallucinating.

Use Cases That Actually Matter

API Integration: Building against your own APIs becomes straightforward when your AI knows the exact request/response formats, required headers, and error handling patterns.

Configuration Management: Instead of memorizing environment variables and config options, ask your AI assistant about deployment settings, feature flags, or service configurations.

Troubleshooting: When something breaks, your AI can reference your troubleshooting guides, known issues, and resolution patterns instead of suggesting generic debugging steps.

Code Reviews: Reference your style guides, architectural decisions, and best practices during reviews without manually looking them up.

Self-Host or Use the Hosted Service

Start with the hosted Biel.ai service for immediate setup, or run your own instance if you need complete control over your documentation access.

The self-hosted option includes Docker deployment and can integrate with your existing documentation infrastructure without sending data to external services.

Quick Integration

1. Point to your docs: Configure your documentation URLs in Biel.ai or run the server locally
2. Add MCP config: Drop the JSON configuration into your AI tool
3. Start asking questions: Your AI assistant now knows your product

No SDK integrations, no workflow changes, no learning curve. Your existing AI tools just get better at their job.

The difference between generic AI assistance and product-aware AI assistance is the difference between Stack Overflow and your internal wiki. Both have value, but only one knows your specific context.