Provides access to InterSystems IRIS ObjectScript documentation, examples, and intelligent search tools for development with IRIS database platform
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@IRIS ObjectScript MCP Server show me examples of how to use the %Library.String class"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Model Context Protocol (MCP) server para documentación de IRIS ObjectScript. Proporciona acceso a documentación, ejemplos y herramientas de búsqueda para el desarrollo con InterSystems IRIS.
# Instalar dependencias
npm install
# Compilar TypeScript
npm run build
# Ejecutar en modo desarrollo
npm run dev
# Ejecutar con inspector MCP
npm run dev:ins# Ir al directorio de deployment
cd deploy/
# Setup completo
./docker-manage.sh build
./docker-manage.sh start
./setup-volumes.sh
# Verificar funcionamiento
./docker-manage.sh statusRelated MCP server: MCP Developer Server
iris-mcp/
├── src/ # Código fuente TypeScript
│ ├── server.ts # Servidor MCP principal
│ ├── tools/ # Herramientas MCP
│ ├── search/ # Funciones de búsqueda
│ ├── loaders/ # Cargadores de documentación
│ ├── resources/ # Recursos MCP
│ └── request/ # Manejadores de requests
├── data/ # Datos y cache
│ └── cache/ # Cache de documentación descargada
├── deploy/ # 🐳 Archivos de Docker y deployment
│ ├── Dockerfile
│ ├── docker-compose.yml
│ ├── docker-manage.sh # Script de gestión principal
│ ├── setup-volumes.sh # Configuración de volúmenes
│ ├── iris-mcp-wrapper.sh # Wrapper para mcp.json
│ └── DOCKER.md # Documentación completa de Docker
├── package.json
├── tsconfig.json
└── README.md # Este archivosmart_search - Búsqueda inteligente con descarga automática
Busca primero en caché local
Descarga documentos relevantes si es necesario
Mapeo inteligente de términos a KEYs
search_objectscript - Búsqueda rápida solo en caché local
Búsqueda instantánea en documentos descargados
Resultados con contexto y números de línea
open_by_key - Abrir documentación por KEY oficial
Acceso directo a documentación específica
Descarga y cachea automáticamente
open_class - Abrir documentación de clase
Documatic para clases (ej. %Library.String)
Navegación por jerarquía de clases
Para deployment en producción, usa Docker:
deploy/)docker-manage.sh - Script principal de gestión
setup-volumes.sh - Configuración de volúmenes bidireccionales
iris-mcp-wrapper.sh - Wrapper para usar en mcp.json
cd deploy/
# Construcción y arranque
./docker-manage.sh build # Construir imagen
./docker-manage.sh start # Iniciar contenedor
./setup-volumes.sh # Configurar permisos
# Gestión diaria
./docker-manage.sh status # Ver estado
./docker-manage.sh logs # Ver logs
./docker-manage.sh restart # Reiniciar
# Mantenimiento
./docker-manage.sh cleanup # Limpiar todo{
"mcpServers": {
"iris-objectscript-docs": {
"command": "bash",
"args": ["/ruta/completa/deploy/iris-mcp-wrapper.sh"],
"env": {
"NODE_ENV": "production"
}
}
}
}Ubicación del archivo:
macOS: ~/Library/Application Support/Claude/mcp.json
Windows: %APPDATA%\\Claude\\mcp.json
Linux: ~/.config/claude/mcp.json
npm run build # Compilar TypeScript
npm run start # Ejecutar servidor compilado
npm run dev # Desarrollo (compilar + ejecutar)
npm run dev:ins # Con inspector MCPserver.ts - Punto de entrada del servidor MCP
tools/ - Definiciones de herramientas MCP
search/ - Lógica de búsqueda (local y inteligente)
loaders/ - Descarga y procesamiento de documentación
resources/ - Recursos y templates MCP
data/ ↔ Contenedor - Sincronización completa
logs/ ↔ Contenedor - Logs compartidos
✅ Modificas archivos localmente → Se reflejan en el contenedor
✅ El MCP descarga docs → Aparecen en tu data/cache/
✅ Backup/sync de data/ funciona normalmente
cd deploy/
./docker-manage.sh build
./docker-manage.sh start
./setup-volumes.sh
Configurar mcp.json
./docker-manage.sh status (verificar)
Trabajar normalmente en el código
./docker-manage.sh restart (si cambias código)
git pull
cd deploy/
./docker-manage.sh stop
./docker-manage.sh build
./docker-manage.sh start
# Buscar información sobre clases
echo '{"jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": {"name": "smart_search", "arguments": {"q": "class methods"}}}' | ./deploy/iris-mcp-wrapper.sh
# Abrir documentación específica
echo '{"jsonrpc": "2.0", "id": 2, "method": "tools/call", "params": {"name": "open_class", "arguments": {"class": "%Library.String"}}}' | ./deploy/iris-mcp-wrapper.shDOCKER.md - Documentación completa de Docker, scripts y troubleshooting
Logs: Revisar logs/ o ./docker-manage.sh logs
Cache: Explorar data/cache/ para ver documentos descargados
Contenedor ejecuta con usuario no-root
Sin puertos expuestos (MCP usa stdio)
Volúmenes con permisos mínimos necesarios
Imágenes basadas en Alpine Linux
# Ver estado del contenedor
cd deploy/ && ./docker-manage.sh status
# Ver logs detallados
cd deploy/ && ./docker-manage.sh logs
# Reset completo
cd deploy/ && ./docker-manage.sh cleanup
cd deploy/ && ./docker-manage.sh build && ./docker-manage.sh start
# Verificar MCP manualmente
echo '{"jsonrpc": "2.0", "id": 1, "method": "initialize", "params": {"protocolVersion": "2024-11-05", "capabilities": {}, "clientInfo": {"name": "test", "version": "1.0.0"}}}' | ./deploy/iris-mcp-wrapper.shPara documentación detallada de Docker y deployment, consulta deploy/DOCKER.md.
Open a documentation page by its official KEY
Inputs: key (required).
Abre Documatic por nombre de clase (ej. %Library.String).
Inputs: class (required).
Search for ObjectScript documentation and examples (solo en caché local)
Inputs: q (required).
Búsqueda inteligente: primero en caché local, luego descarga documentos si es necesario
Inputs: q (required), keys.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 4 tools
The tools have overlapping purposes that could cause confusion, particularly between search_objectscript and smart_search, which both search documentation but differ in scope (local vs. local+download). open_by_key and open_class are more distinct but still both open documentation pages. Descriptions help clarify differences, but an agent might misselect between the search tools.
Naming is inconsistent with mixed conventions: open_by_key and search_objectscript use snake_case, while open_class and smart_search use snake_case but with Spanish names in descriptions. Verb styles vary (open vs. search vs. smart_search), and there's no predictable pattern across the set, making it harder for an agent to infer tool purposes from names alone.
With 4 tools, the count is reasonable for a documentation server focused on ObjectScript. It covers key actions like opening and searching, though it might feel slightly thin if more advanced documentation interactions are needed. The scope is well-defined, and each tool appears to earn its place without obvious bloat.
For a documentation server, the tools cover opening by key/class and searching locally or with downloads, which addresses core needs. However, there are notable gaps: no tools for browsing documentation structure, listing available classes/keys, or managing the cache. This could lead to dead ends where an agent cannot navigate documentation beyond basic searches and opens.
Versioned documentation registry and semantic search for AI tools and coding assistants.
Access and search Branch's official API documentation directly within any AI agent or client.
Provide your AI coding tools with token-efficient access to up-to-date technical documentation for…
Get up-to-date, version-specific documentation and code examples from official sources directly in…
