Semantic search over WSO2 docs (APIM, MI, Choreo, Ballerina) via RAG and pgvector.
Semantic search over WSO2 docs (APIM, MI, Choreo, Ballerina) via RAG and pgvector. Exposed over MCP by the wso2 mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.
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).
wso2-docs-mcp-server on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
Everything the assistant can do here goes through one of these:
search_wso2_docs — Semantic search across all products. Optional product and limit filtersget_wso2_guide — Search within a specific product (apim, mi, bi, choreo, is, ballerina, library)explain_wso2_concept — Broad concept search across all products, returns 8 top resultslist_wso2_products — Returns all supported products with IDs and base URLsCore — The Core tool exposed by this serverYou will need 6 environment variables: DATABASE_URL, EMBEDDING_PROVIDER, OPENAI_API_KEY, OLLAMA_BASE_URL, GEMINI_API_KEY, VOYAGE_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Plenty of AI and media services servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Wso2's toolset — search_wso2_docs, get_wso2_guide, explain_wso2_concept and 2 more — is a fair guide to whether it matches your workflow. It is maintained by iamvirul; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| search_wso2_docs | Semantic search across all products. Optional product and limit filters. |
| get_wso2_guide | Search within a specific product (apim, mi, bi, choreo, is, ballerina, library). |
| explain_wso2_concept | Broad concept search across all products, returns 8 top results. |
| list_wso2_products | Returns all supported products with IDs and base URLs. |
| Core | The Core tool exposed by this server. |
{
"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"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| DATABASE_URL | Endpoint or connection string the server talks to. | Yes |
| EMBEDDING_PROVIDER | Configuration value read at startup. | Optional |
| OPENAI_API_KEY | Credential the server authenticates with. | Yes |
| OLLAMA_BASE_URL | Endpoint or connection string the server talks to. | Yes |
| GEMINI_API_KEY | Credential the server authenticates with. | Yes |
| VOYAGE_API_KEY | Credential the server authenticates with. | Yes |
Build a programmable telecommunications stack for connecting telephony services with the Internet via a cloud-based utility.
Search built for AI, not humans — semantic web search that returns model-ready content, plus code context.
Answers, not links — delegate questions to Perplexity's search-grounded models and get cited responses back.
Give your assistant a voice — text-to-speech, voice cloning and audio tools from the ElevenLabs API.
Give your assistant a real code sandbox — isolated cloud VMs for actually running the code it writes.
The ML hub in your context window — search models, datasets, papers and run Spaces from the official server.