Wso2 Docs Mcp Server

io.github.iamvirulPublished by GitHub account iamvirulv1.3.14Updated Oct 31, 2026

Semantic search over WSO2 docs (APIM, IS, MI, Choreo, Ballerina) via RAG and pgvector.

VerifiedSTDIODesktop onlyDatabasesKnowledge & Memory

Overview

AI-generated overview

Local MCP server that gives an assistant semantic search over WSO2 documentation (APIM, MI, BI, Choreo, IS, Ballerina) using RAG with pgvector.

What you can do
  • Search WSO2 documentation semantically across all indexed products, with optional product and result-count filters
  • Search within one product's guides for APIM, MI, BI, Choreo, IS, Ballerina or the WSO2 Library
  • Look up broad concepts across all products and get the top matching passages
  • List the supported products with their IDs and base documentation URLs
  • Return results with title, snippet, source URL, product, section and relevance score
When to use it
Useful when you work with WSO2 middleware and want an assistant to answer questions or draft guidance grounded in official WSO2 docs instead of guessing. It fits local desktop clients such as Claude Desktop, Claude Code, Cursor or VS Code.
Requirements
Runs locally over stdio as an npm package (Node.js 20 or newer). Needs a PostgreSQL database with pgvector, typically started via the provided Docker Compose file, and the DATABASE_URL connection string. Documentation must be indexed first with the bundled crawl and migrate commands. Embeddings default to local Ollama, falling back to an in-process HuggingFace ONNX model; cloud providers need GEMINI_API_KEY, OPENAI_API_KEY or VOYAGE_API_KEY.
Before you install
The project is unofficial and not affiliated with or endorsed by WSO2. DATABASE_URL is a connection string that may embed database credentials, so keep it out of shared configs. Choosing a cloud embedding provider sends documentation text to that provider and requires the matching API key. The crawl and migrate commands write to and can re-index the database, and the first run downloads an embedding model.

Installation

In SourceWeft

  1. Open Wso2 Docs Mcp Server in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

WSO2 Docs MCP Server

[npm version] [License]

"This is an unofficial community project. Not affiliated with or endorsed by WSO2."

A production-ready Model Context Protocol (MCP) server that provides AI assistants (Claude Desktop, Claude Code, Cursor, VS Code) with semantic search over WSO2 documentation via Retrieval-Augmented Generation (RAG).

Under the hood, it uses a blazing-fast dual-ingestion engine:

  • GitHub Native: Fetches raw Markdown directly from WSO2's public GitHub repositories via the Git Trees API (avoids web-scraping noise and rate limits)
  • Web Crawl Fallback: For products without dedicated GitHub docs repos (like the WSO2 Library)

Architecture

[System Architecture]

Documentation Sources

ProductIDURL
API Managerapimhttps://apim.docs.wso2.com
Micro Integratormihttps://mi.docs.wso2.com/en/4.4.0
Ballerina Integratorbihttps://bi.docs.wso2.com
Choreochoreohttps://wso2.com/choreo/docs
Identity Serverishttps://is.docs.wso2.com/en/latest
Ballerinaballerinahttps://ballerina.io/learn
WSO2 Librarylibraryhttps://wso2.com/library

Prerequisites

  • Node.js ≥ 20
  • Docker (for pgvector)
  • Embeddings - no API key required by default:
    • Ollama (recommended) - runs locally, model auto-downloaded on first run
    • If Ollama is not running, the server automatically falls back to HuggingFace ONNX (in-process, also downloads automatically)
    • Cloud providers are also supported: OpenAI, Google Gemini, Voyage AI

Quick Start

Choose the setup path that fits your use case:


Install from npm

Install the package globally to get the wso2-docs-mcp-server, wso2-docs-crawl, and wso2-docs-migrate commands available system-wide:

bash
npm install -g wso2-docs-mcp-server

Prefer no global install? You can use npx wso2-docs-mcp-server, npx wso2-docs-crawl, and npx wso2-docs-migrate in every step below - just replace the bare command with its npx equivalent.

1. Start pgvector

Download the docker-compose.yml and start the database:

bash
curl -O https://raw.githubusercontent.com/iamvirul/wso2-docs-mcp-server/main/docker-compose.ymldocker compose up -d
2. Start Ollama (optional but recommended)

Install Ollama and pull the default embedding model:

bash
ollama pull nomic-embed-textollama serve

No Ollama? Skip this step. The server automatically falls back to HuggingFace ONNX - model downloads on first use with no extra setup.

3. Run database migration
bash
DATABASE_URL="postgresql://wso2mcp:wso2mcp@localhost:5432/wso2docs" \  wso2-docs-migrate

Run migration again whenever you change EMBEDDING_DIMENSIONS (i.e. switch embedding provider). The script detects and handles dimension changes automatically.

4. Index WSO2 documentation
bash
# Index all products (first run downloads the embedding model automatically)DATABASE_URL="postgresql://wso2mcp:wso2mcp@localhost:5432/wso2docs" \  wso2-docs-crawl
# Index a single product (faster, great for testing)DATABASE_URL="postgresql://wso2mcp:wso2mcp@localhost:5432/wso2docs" \  wso2-docs-crawl --product ballerina --limit 20
# Force re-index even unchanged pagesDATABASE_URL="postgresql://wso2mcp:wso2mcp@localhost:5432/wso2docs" \  wso2-docs-crawl --force

Available product IDs: apim, mi, bi, choreo, is, ballerina, library

5. Configure your AI client

The MCP server is launched on demand by your AI client - no background process needed.

Claude Desktop - edit ~/Library/Application Support/Claude/claude_desktop_config.json:

json
{  "mcpServers": {    "wso2-docs": {      "command": "wso2-docs-mcp-server",      "env": {        "DATABASE_URL": "postgresql://wso2mcp:wso2mcp@localhost:5432/wso2docs",        "EMBEDDING_PROVIDER": "ollama"      }    }  }}

Claude Code - run once in your terminal:

bash
claude mcp add wso2-docs \  --transport stdio \  -e DATABASE_URL="postgresql://wso2mcp:wso2mcp@localhost:5432/wso2docs" \  -e EMBEDDING_PROVIDER="ollama" \  -- wso2-docs-mcp-server
# Verifyclaude mcp list

Cursor - create .cursor/mcp.json in your project root:

json
{  "mcpServers": {    "wso2-docs": {      "command": "wso2-docs-mcp-server",      "env": {        "DATABASE_URL": "postgresql://wso2mcp:wso2mcp@localhost:5432/wso2docs",        "EMBEDDING_PROVIDER": "ollama"      }    }  }}

VS Code - create .vscode/mcp.json:

json
{  "servers": {    "wso2-docs": {      "type": "stdio",      "command": "wso2-docs-mcp-server",      "env": {        "DATABASE_URL": "postgresql://wso2mcp:wso2mcp@localhost:5432/wso2docs",        "EMBEDDING_PROVIDER": "ollama"      }    }  }}

Using npx instead of global install? Replace "command": "wso2-docs-mcp-server" with "command": "npx" and add "args": ["-y", "wso2-docs-mcp-server"].

Cloud embedding provider? Add the key to env, e.g. "EMBEDDING_PROVIDER": "openai", "OPENAI_API_KEY": "sk-...".


Clone and build

1. Clone and install
bash
git clone https://github.com/iamvirul/wso2-docs-mcp-server.gitcd wso2-docs-mcp-servernpm install
2. Start Ollama (optional but recommended)

Install Ollama and start it:

bash
ollama serve

No Ollama? Skip this step. The server detects Ollama is not running and automatically falls back to HuggingFace ONNX inference - the model downloads on first use with no extra setup.

3. Configure environment
bash
cp .env.example .env# Defaults work out of the box with Ollama.# Only edit if using a cloud provider (OpenAI / Gemini / Voyage).
4. Start pgvector
bash
docker compose up -d# pgAdmin available at http://localhost:5050 ([email protected] / admin)
5. Run database migration
bash
npm run db:migrate

Note: Run migration again whenever you change EMBEDDING_DIMENSIONS (i.e. switch embedding provider). The script detects and handles dimension changes automatically.

6. Index documentation
bash
# Index all products# On first run the embedding model is downloaded automatically (Ollama or HuggingFace)npm run crawl
# Index a single product (faster, great for testing)npm run crawl -- --product ballerina --limit 20
# Force re-index even unchanged pagesnpm run crawl -- --force
7. Build and start the MCP server
bash
npm run buildnpm start

For development (no build step):

bash
npm run dev
8. Configure your AI client

Replace /ABSOLUTE/PATH/TO/wso2-docs-mcp-server with your actual clone path.

Claude Desktop - edit ~/Library/Application Support/Claude/claude_desktop_config.json:

json
{  "mcpServers": {    "wso2-docs": {      "command": "node",      "args": ["/ABSOLUTE/PATH/TO/wso2-docs-mcp-server/dist/src/index.js"],      "env": {        "DATABASE_URL": "postgresql://wso2mcp:wso2mcp@localhost:5432/wso2docs",        "EMBEDDING_PROVIDER": "ollama"      }    }  }}

Claude Code:

bash
claude mcp add wso2-docs \  --transport stdio \  -e DATABASE_URL="postgresql://wso2mcp:wso2mcp@localhost:5432/wso2docs" \  -e EMBEDDING_PROVIDER="ollama" \  -- node "/ABSOLUTE/PATH/TO/wso2-docs-mcp-server/dist/src/index.js"
# Verifyclaude mcp list

See config-examples/claude_code.sh for a convenience script.

Cursor - create .cursor/mcp.json - see config-examples/cursor_mcp.json.

VS Code - create .vscode/mcp.json - see config-examples/vscode_mcp.json.


MCP Tools

ToolDescription
search_wso2_docsSemantic search across all products. Optional product and limit filters.
get_wso2_guideSearch within a specific product (apim, mi, bi, choreo, is, ballerina, library).
explain_wso2_conceptBroad concept search across all products, returns 8 top results.
list_wso2_productsReturns all supported products with IDs and base URLs.

Example response

json
[  {    "title": "Deploying WSO2 API Manager",    "snippet": "WSO2 API Manager can be deployed in various topologies…",    "source_url": "https://apim.docs.wso2.com/en/latest/install-and-setup/...",    "product": "apim",    "section": "Deployment Patterns",    "score": 0.8712  }]

Local Embeddings

The default EMBEDDING_PROVIDER=ollama runs entirely on your machine with no API key. The startup sequence is:

Is Ollama running?├── Yes → Is model present?│         ├── Yes → Ready (instant)│         └── No  → Pull via Ollama (streamed, runs once)└── No  → Download ONNX model from HuggingFace Hub (~250 MB, cached after first run)           and run inference in-process via @huggingface/transformers

Both paths use nomic-embed-text / Xenova/nomic-embed-text-v1 by default and produce identical 768-dim vectors, so you can switch between them without re-indexing.

Hardware acceleration (HuggingFace ONNX fallback)

When Ollama is not available, the server auto-detects the best compute backend:

MachineDetectionONNX dtypeBatch sizeThroughput
Apple Silicon (M1/M2/M3/M4)process.arch === 'arm64'q8 INT832~9 ms/chunk
NVIDIA GPUnvidia-smi probefp3264GPU-dependent
All othersfallbackq8 INT816~10 ms/chunk

Why q8 on Apple Silicon instead of CoreML/Metal? CoreML compiles Metal shaders on first use (~20 min cold-start). For the typical chunk sizes produced by this server (6–20 chunks per page), the CPU↔GPU transfer overhead eliminates any inference gain. INT8 quantized inference on ARM NEON SIMD is consistently ~100× faster than fp32 CPU with zero cold-start cost.

Benchmark (Apple M-chip, Xenova/nomic-embed-text-v1):

fp32 CPU (before): ~1,000 ms/chunk   (68 chunks ≈ 68 s of embedding)q8  ARM NEON:          ~9 ms/chunk   (68 chunks ≈  0.6 s of embedding)  ← ~100× speedup

Note: For small crawls (≤ 10 pages) total wall-clock time is dominated by network I/O (HTTPS fetches to docs sites), so the end-to-end improvement is modest. The embedding speedup becomes significant at scale - crawling 500+ pages where embedding previously accounted for hours of runtime. For best crawl performance, run Ollama (ollama serve) which parallelises inference natively and has no per-chunk overhead.


Environment Variables

Core

VariableDefaultDescription
DATABASE_URL-PostgreSQL connection string (required)
EMBEDDING_PROVIDERollamaollama | openai | gemini | voyage
EMBEDDING_DIMENSIONS768Must match model output dimensions
CRAWL_CONCURRENCY5Concurrent HTTP requests during crawl
CHUNK_SIZE800Approximate tokens per chunk
CHUNK_OVERLAP100Overlap tokens between chunks
CACHE_TTL_SECONDS3600In-memory query cache TTL
TOP_K_RESULTS10Default search result count

Ollama (default)

VariableDefaultDescription
OLLAMA_BASE_URLhttp://localhost:11434Ollama server URL
OLLAMA_EMBEDDING_MODELnomic-embed-textModel pulled and used via Ollama
HUGGINGFACE_EMBEDDING_MODELXenova/nomic-embed-text-v1ONNX fallback when Ollama is not running

Cloud providers

VariableDefaultDescription
OPENAI_API_KEY-Required if EMBEDDING_PROVIDER=openai
OPENAI_EMBEDDING_MODELtext-embedding-3-smallOpenAI model
GEMINI_API_KEY-Required if EMBEDDING_PROVIDER=gemini
GEMINI_EMBEDDING_MODELtext-embedding-004Gemini model
VOYAGE_API_KEY-Required if EMBEDDING_PROVIDER=voyage
VOYAGE_EMBEDDING_MODELvoyage-3Voyage model

Embedding dimension reference

ProviderModelDimensions
Ollama / HuggingFacenomic-embed-text / Xenova/nomic-embed-text-v1768 (default)
Ollama / HuggingFacemxbai-embed-large / Xenova/mxbai-embed-large-v11024
Ollama / HuggingFaceall-minilm / Xenova/all-MiniLM-L6-v2384
OpenAItext-embedding-3-small1536
OpenAItext-embedding-3-large3072
Geminitext-embedding-004768
Voyagevoyage-31024
Voyagevoyage-3-lite512

Scheduled Re-indexing

bash
# Run a one-off re-index (checks hashes, skips unchanged pages)npm run reindex
# Or from the project directory using node-cron (runs daily at 2 AM)DATABASE_URL=... node -e "  const { ReindexJob } = require('./dist/jobs/reindexDocs');  const job = new ReindexJob();  job.initialize().then(() => job.scheduleDaily());"

Project Structure

src/  config/          env.ts · constants.ts  vectorstore/     pgvector.ts · schema.sql  ingestion/       crawler.ts · parser.ts · githubFetcher.ts · markdownParser.ts · chunker.ts · embedder.ts  server/          mcpServer.ts · toolRegistry.ts  jobs/            reindexDocs.ts  index.tsscripts/  crawl.ts         CLI ingestion pipeline  migrate.ts       Dynamic schema migrationconfig-examples/   claude_desktop.json · claude_code.sh · cursor_mcp.json · vscode_mcp.jsondocker-compose.yml.env.example

Development

bash
# Type-checknpx tsc --noEmit
# Run crawl with tsx (no build needed)npm run crawl -- --product ballerina --limit 5
# Run server in dev modenpm run dev

Source: README.md at commit 92337d2

Tools

0
SourceWeft started this package once in an isolated sandbox, without credentials, to list its tools. That failed: the server did not start.

Version history

3
  1. v1.3.14LatestOct 31, 2026
  2. v1.3.13Oct 16, 2026
  3. v1.2.0Sep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts