Weik.io Integration Expert MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_agentsB | List all Weik.io agents |
| apply_configC | Apply a Weik.io configuration file |
| get_supported_integration_typesB | Get information about supported integration types in Weik.io |
| search_componentsA | Search for Apache Camel components by name, description, or label |
| get_component_detailsB | Get detailed information about a specific Apache Camel component |
| search_kameletsB | Search for Apache Camel Kamelets by name, title, or description |
| get_kamelet_detailsB | Get detailed information about a specific Apache Camel Kamelet |
| get_docker_composeA | Get a Docker Compose file for setting up a local Weik.io instance |
| list_profilesB | List all Weik.io profiles |
| add_profileC | Add a new Weik.io profile |
| initialize_integrationB | Initialize a new integration flow with the specified name in the specified directory |
| push_integrationC | Push an integration to a Weik.io instance |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
Each tool targets a distinct operation: profile management (add, list), component/kamelet details and search, integration initialization and push, config application, agent listing, docker compose retrieval, and supported types. No two tools have overlapping purposes; descriptions clearly differentiate them.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., add_profile, get_component_details, search_components). The convention is uniform across all 12 tools, making the set predictable and easy to navigate.
With 12 tools, the scope is well-balanced. It covers multiple aspects of Weik.io integration (profiles, components, kamelets, integrations, config, agents, Docker support) without being overwhelming or sparse.
The tool set covers core operations: profile CRUD (add/list), component/kamelet retrieval and search, integration initialization and push, config application, and agent listing. Minor gaps exist (e.g., no update/delete for profiles, no integration deletion), but the core workflow for setting up and pushing integrations is complete.