Source profile for Weik.io Integration Expert: MCP Server. Its purpose and connection details need verification against the maintainer’s documentation.
This Weik.io Integration Expert: MCP Server source profile is awaiting review. The previous overview contained a logo or badge fragment rather than a usable description. Check the linked maintainer documentation for the server’s purpose and connection details.
The project provides a local client configuration using docker. Follow the repository’s build and installation steps before copying it, and replace example paths with the paths on your own computer.
Project documentation · Repository · Discovery listing. This profile records the public documentation checked on 2026-10-08.
Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.
| Tool | What it does |
|---|---|
| get_supported_integration_types | Get information about supported integration types (implemented) |
| analyze_integration_requirements | Determine optimal approach and technology (planned) |
| suggest_integration_pattern | Recommend appropriate pattern for requirements (planned) |
| get_best_practices | Retrieve relevant best practices for specific integration type (planned) |
| initialize_integration | Initialize a new integration flow with the specified name (implemented) |
| generate_camel_integration | Generate Camel YAML flow (planned) |
| generate_mft_configuration | Generate MFT config for file operations (planned) |
| create_data_transformation | Build JQ or other transformations based on sample data (planned) |
| validate_implementation | Check implementation against best practices (planned) |
| apply_best_practices | Analyze and enhance existing integration with best practices (planned) |
| get_best_practice | Retrieve detailed information about specific best practices (planned) |
| check_compliance | Validate integration against best practice standards (planned) |
| identify_test_parameters | Determine required parameters for testing (planned) |
| generate_test_configuration | Create test setup files (planned) |
| create_test_data | Generate mock data for testing (planned) |
| debug_transformation | Interactive JQ/transformation debugging (planned) |
| analyze_payload | Examine message structure at any point (planned) |
| trace_message_flow | Visualize message path through integration (planned) |
| diagnose_error | Analyze errors and suggest solutions (planned) |
| setup_ngrok_tunnel | Configure and start an ngrok tunnel for local endpoints (planned) |
| get_ngrok_url | Retrieve current ngrok public URL for use in integrations (planned) |
| create_webhook_endpoint | Generate new webhook.site endpoints for testing (planned) |
| retrieve_webhook_requests | Get received webhook payloads for analysis (planned) |
| run_camel_jbang | Execute Camel scripts for quick testing (planned) |
| get_docker_compose | Get a Docker Compose file for setting up a local Weik.io instance (implemented) |
| start_local_weikio | Start local Weik.io using Docker Compose (planned) |
| stop_local_weikio | Stop the running environment (planned) |
| restart_local_weikio | Restart for quick refresh (planned) |
| get_weikio_status | Simple health check and status reporting (planned) |
| reset_local_weikio | Return environment to clean state (planned) |
| list_profiles | List all Weik.io profiles (implemented) |
| add_profile | Add a new Weik.io profile with name, URL, and API key (implemented) |
| push_integration | Push an integration to a Weik.io instance (implemented) |
| generate_push_commands | Create commands to push to Weik.io (planned) |
| create_deployment_checklist | Generate pre-deployment verification steps (planned) |
{
"mcpServers": {
"weikio": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"--network=host",
"ghcr.io/weikio/mcp-server:latest"
],
"disabled": false,
"autoApprove": []
}
}
}From the project documentation. Replace placeholders and example paths before connecting.
Read, search and edit files inside allowed directories with the Model Context Protocol reference Filesystem server.
Retrieve version-aware library documentation and code examples with Context7 MCP, using resolve-library-id and query-docs.
Use Microsoft’s Playwright MCP server to navigate pages, inspect accessibility snapshots, fill forms and capture browser screenshots.
Connect GitHub MCP to repositories, issues and pull requests with GitHub’s hosted service or a locally run server.
Use the Supabase MCP server to inspect database schemas, query project data and retrieve docs through a project-scoped connection.
Search Linear issues and projects, inspect work context and manage updates through Linear’s hosted MCP server with OAuth.