beginner⏱️ 10-20 minutes📅 Updated June 2026

Step-by-step guide to integrate ai-Bible MCP server with OpenSumi. Includes get_verse and search_verses.

ai-Bible + OpenSumi: Complete MCP Integration

ai-Bible is a MCP server that Search the bible reliably and repeatably ai-Bible Labs.

When integrated with OpenSumi, you can:

  • Retrieve specific Bible verses by reference
  • Search for Bible verses containing specific keywords
  • Retrieve an entire chapter

This guide provides step-by-step instructions to set up ai-Bible in OpenSumi, including configuration, examples, and troubleshooting.

What You'll Achieve

After completing this setup:

  • ai-Bible will be fully integrated and operational
  • You can use ai-Bible tools directly in OpenSumi
  • All ai-Bible capabilities will be available for your workflows
  • Access to 4 different tools

Prerequisites

Before starting, ensure you have:

  • OpenSumi installed and configured
  • Compatible operating system (Web (Browser-based), Electron Desktop, Container (Docker/K8s), Framework Integration)

Installation

Step 1: Install ai-Bible

Configuration

Step 2: Configure OpenSumi

  1. Open OpenSumi settings
  2. Navigate to MCP server configuration
  3. Add ai-Bible server with appropriate settings
  4. Save and restart if needed

Examples

Once configured, you can use ai-Bible in OpenSumi:

Verse Lookup for Study

undefined

Ask OpenSumi: "Get Matthew 5:3-12 (Beatitudes)"

Expected Result: undefined

Thematic Bible Search

undefined

Ask OpenSumi: "Find all verses about faith in Hebrews"

Expected Result: undefined

Comparative Study

undefined

Ask OpenSumi: "Compare creation accounts in Genesis 1 and Psalm 104"

Expected Result: undefined

Testing Your Setup

  1. Launch OpenSumi
  2. Verify ai-Bible is available in the tools list
  3. Test basic ai-Bible functionality

Troubleshooting

Common Issues

Dependency Installation Failures

Symptoms: Yarn/npm install errors, Missing packages, Version conflicts

Cause: Incompatible Node.js version or network issues

Solution:

  • Ensure Node.js 16+ is installed
  • Use yarn for standard installation, npm for lite version
  • Clear package cache: yarn cache clean or npm cache clean --force
  • Check network connectivity and proxy settings

Workspace Not Loading

Symptoms: Empty workspace, Files not showing, Permission errors

Cause: Incorrect workspace path or permissions

Solution:

  • Verify MY_WORKSPACE environment variable is set correctly
  • Check file system permissions for workspace directory
  • Use absolute path for workspace location
  • Default workspace is tools/workspace in repository

VSCode Extension Compatibility

Symptoms: Extension not loading, Extension errors, Missing features

Cause: Extension API incompatibility or missing dependencies

Solution:

  • Verify extension is compatible with VSCode extension API used by OpenSumi
  • Check extension documentation for known issues
  • Try downloading extensions via yarn run download-extension
  • Some extensions may require OpenSumi-specific adaptation

WebWorker Compilation Errors (Lite Version)

Symptoms: Compile-worker fails, Language service not working, Syntax highlighting broken

Cause: WebWorker build configuration issues

Solution:

  • Run npm run compile-worker before starting
  • Ensure all dependencies are installed correctly
  • Check browser console for WebWorker loading errors
  • Clear browser cache and rebuild

MCP Client Connection Failures

Symptoms: Cannot connect to MCP server, Tool discovery fails, MCP errors in console

Cause: MCP server not running or incorrect configuration

Solution:

  • Verify MCP server is running and accessible
  • Check MCP server URL in OpenSumi configuration
  • Review MCP client integration code for errors
  • Check browser/Electron console for detailed error messages

Electron App Not Starting

Symptoms: Electron window not opening, White screen, App crashes on launch

Cause: Electron build issues or IPC communication errors

Solution:

  • Ensure Electron dependencies are installed correctly
  • Check Electron version compatibility (15+)
  • Review IPC communication setup in configuration
  • Check Electron dev tools console for errors

ai-Bible not appearing in OpenSumi

Symptoms: Server not listed, Tools not available

Cause: Configuration or installation issue

Solution:

  • Verify configuration syntax
  • Check ai-Bible installation
  • Restart OpenSumi
  • Check logs for error messages

Next Steps

Now that ai-Bible is integrated with OpenSumi:

  • Explore all ai-Bible capabilities through OpenSumi
  • Check out other MCP servers that work with OpenSumi
  • Join the MCP community for tips and support
  • Consider contributing to ai-Bible development

Need Help?

Related Resources

More Integrations

Explore other MCP servers that work with OpenSumi

Need Help?

Join the MCP community for support and discussions

ai-Bible + OpenSumi: MCP Setup Guide (2026)