Databricks MCP MCP Server Pricing 2026

Integrate DeepSeek API for cost-effective reasoning and code generation — access DeepSeek-V3 and DeepSeek-R1 models for complex problem solving, mathematical reasoning, and code synthesis.

Access Alibaba Cloud Qwen LLM family via API — long-context processing with Qwen-Long, multimodal with Qwen-VL, and code generation with Qwen-Coder for multilingual AI workflows.

Connect to Moonshot AI Kimi API for long-context document analysis up to 200K tokens, Chinese-English bilingual processing, web search-augmented generation, and multimodal understanding.

a Python MCP server for Jenkins (lanbaoshen/mcp-jenkins, published to PyPI as mcp-jenkins) and the alternative to the official Jenkins MCP plugin: where the plugin has to be installed into the controller from the update centre, this one runs beside Jenkins and talks to it over the ordinary REST API, so you can point it at a Jenkins you do not administer. Install it with uvx mcp-jenkins, pip install mcp-jenkins, or the ghcr.io/lanbaoshen/mcp-jenkins container. Credentials go in as --jenkins-url, --jenkins-username and --jenkins-password (an API token works in place of the password), and on the HTTP transport the same three can be supplied per-connection as the x-jenkins-url, x-jenkins-username and x-jenkins-password headers, which is what lets one running instance serve several Jenkins controllers. Three transports are available via --transport: stdio (the default), sse, and streamable-http, which listens on 0.0.0.0:9887 unless --host and --port say otherwise. The tool set is wider than most Jenkins integrations. Jobs and pipelines: get_item, get_item_config, get_item_parameters, get_all_items, query_items for pattern search, and build_item to trigger. Builds: get_build, get_build_console_output, get_build_parameters, get_build_test_report, get_build_scripts, get_running_builds and stop_build, plus get_all_build_artifacts, get_build_artifact and get_build_artifact_url for pulling artifacts out of a finished run. Queue: get_all_queue_items, get_queue_item, cancel_queue_item. Agents: get_all_nodes, get_node, get_node_config. The plugin tools are the part with no equivalent elsewhere — get_all_plugins, get_plugin, get_plugins_with_updates, get_plugins_with_backup, get_plugin_dependency_graph (Graphviz output), and get_plugins_with_problems, which reports missing dependencies and version mismatches and turns a plugin upgrade audit into one question. Two flags matter for safety. run_groovy_script executes arbitrary Groovy on the controller, which is full remote code execution against your CI; --read-only disables it along with every other mutating tool and is the right default for an agent that only needs to read build state. --jenkins-timeout defaults to 5 seconds, which is often too short for a large get_all_items on a busy controller.

Connect to JetBrains TeamCity CI/CD via REST API — trigger build configurations, monitor build queues, inspect test results, manage agents, and query build artifacts for developer workflow automation.

Manage Atlassian Bamboo CI/CD pipelines via API — run plans, inspect build results, manage deployment environments, track releases, and integrate with Jira and Bitbucket for full DevOps workflows.