SAMO MCP Server
The SAMO MCP Server is a Model Context Protocol (MCP) server that exposes SAMO project management, documentation search, and schema lookup capabilities to AI-powered tools. It uses stdio transport — the AI client launches it as a local process and communicates via standard input/output.
The MCP server is bundled with SAMO Pilot and launched automatically by Claude Code. It can also be used standalone with other MCP-compatible clients.
When used with SAMO Pilot, the MCP server is fetched automatically via npx @samo/mcp-server. This requires the @samo npm scope to be configured — see the npm setup guide.
For standalone installation and client configuration, see the RDT Installation Guide.
Screenshot needed
VS Code MCP panel or Claude Desktop showing the SAMO MCP server connected with available tools listed
Tools
SAMO Project Tools
| Tool | Description |
|---|---|
check_gitlab_token | Validates the SAMO_GITLAB_TOKEN environment variable |
create_samo_project | Clones GitLab init repos, replaces template placeholders, and generates a complete project structure |
GIF needed
create_samo_project tool in action — AI client scaffolding a new SAMO project with template substitution
Documentation Search Tools
| Tool | Description |
|---|---|
search_docs | Full-text search across SAMO documentation (TF-IDF scoring, fuzzy + prefix matching) |
grep_docs | Literal or regex pattern search with context lines |
glob_docs | List documentation files by glob pattern |
read_doc | Read file content with line range support |
list_sections | List top-level documentation folders with file counts |
Content indexed: The Cookbook & Tutorials and Implementation Guide from SAMO Lighthouse. The full index is built in-memory on startup.
Screenshot needed
search_docs tool returning SAMO documentation results with relevance scores and excerpts
Scripting API Tools
| Tool | Description |
|---|---|
list_scripting_api_namespaces | Lists all available scripting API namespaces (e.g., api.business(), api.features()) |
search_scripting_api | Full-text search across scripting API builders, methods, and parameters |
get_scripting_api_builder | Fetches a specific builder's full schema with methods and parameters |
get_scripting_api_examples | Fetches usage examples for a specific scripting API builder |
Content indexed: The LIDS Scripting API — all namespaces (e.g., api.business(), api.features(), api.http()), their builder methods, parameters, and ready-made usage examples.
Screenshot needed
search_scripting_api returning matching API methods with parameter signatures and descriptions
DynApp Module Catalog Tools
| Tool | Description |
|---|---|
list_modules | Lists all available DynApp module schemas |
search_modules | Full-text search across DynApp module schemas |
get_module_schema | Fetches a specific module's JSON schema with inlined references |
search_module_properties | Searches properties within DynApp module schemas |
Content indexed: The full DynApp module catalog — all available UI components (page modules, application modules, etc.) with their JSON schemas, properties, and configuration options.
DynApp Configuration Tools
| Tool | Description |
|---|---|
list_dynapp_configuration_schemas | Lists available DynApp configuration schemas (application, app-part, app-module, etc.) |
search_dynapp_configuration_schemas | Full-text search across DynApp configuration schemas |
get_dynapp_configuration_schema | Fetches a specific configuration schema with inlined $ref references |
search_dynapp_configuration_schema_properties | Searches properties within DynApp configuration schemas |
Content indexed: DynApp configuration schemas — application, app-part, app-module, page-modules, entity-metadata, and intent definitions with inlined $ref references.
Business Server Tools
| Tool | Description |
|---|---|
list_business_server_schemas | Lists available business server configuration schemas |
search_business_server_schemas | Full-text search across business server schemas |
get_business_server_schema | Fetches a specific business server schema with inlined references |
search_business_server_schema_properties | Searches properties within business server schemas |
Content indexed: Business server configuration schemas — entities, services, triggers, workflows, actions, conditions, and all related JSON config structures with ready-made examples.
Supported Clients
The MCP server works with any MCP-compatible client:
| Client | Configuration |
|---|---|
| Claude Code (via SAMO Pilot) | Automatic — configured in .mcp.json |
| VS Code — GitHub Copilot | .vscode/mcp.json |
| Claude Desktop | claude_desktop_config.json |
Screenshot needed
Example .vscode/mcp.json configuration for connecting the MCP server to VS Code GitHub Copilot
Environment Variables
Only SAMO_GITLAB_TOKEN is required — it is configured automatically by SAMO Pilot. The optional variables are not set by the plugin; set them in your shell environment only if you need non-default values.
| Variable | Default | Purpose |
|---|---|---|
SAMO_GITLAB_TOKEN | — | GitLab access token for project scaffolding. Contact the RDT team or email simon.misak@asseco-ce.com to obtain it. |
DOCS_URL | https://lighthouse.samo-asseco.com/raw-docs.json.gz | URL to gzipped documentation JSON |
BUSINESS_SERVER_VERSION | 10.0.5-228005 | Override the business-server schema version |
DYNAPP_VERSION | Latest from catalog/versions.json | Override the Dynamic App version (module catalog + configuration schemas) |
SCRIPTING_API_URL | ...scriptingApi_v10.0.4.json | Override the scripting API schema URL |
SCRIPTING_API_EXAMPLES_URL | ...scriptingApiExamples_v10.0.4.json | Override the scripting API examples URL |