MCP server · Kubeshop

testkube

Testkube's hosted MCP server lets AI assistants list and run test workflows, inspect executions, fetch logs and artifacts, and query results. The endpoint is scoped per organization and environment; organization and environment IDs come from the Testkube dashboard.

Open endpoint → Kubeshop provider profile

One-click install for Cursor, VS Code, Claude, and 20+ other MCP clients, powered by API Commons MCP Install — visit install.apicommons.org for more information.

Provider: Kubeshop Type: Hosted endpoint Transport: http Host: api.testkube.io

Endpoint

https://api.testkube.io/organizations/{organization_id}/environments/{environment_id}/mcp

Hosted endpoint · transport http

Connect

This is a remote MCP server — point an MCP client at the endpoint URL. Clients with native remote support (Claude, Cursor, VS Code, …):

# mcp client config (e.g. .mcp.json / mcp settings) { "mcpServers": { "kubeshop": { "url": "https://api.testkube.io/organizations/{organization_id}/environments/{environment_id}/mcp" } } }

For stdio-only clients (older Claude Desktop, etc.), bridge with mcp-remote:

# Add to claude_desktop_config.json { "mcpServers": { "kubeshop": { "command": "npx", "args": ["-y", "mcp-remote", "https://api.testkube.io/organizations/{organization_id}/environments/{environment_id}/mcp"] } } }

If the server requires authentication, add the provider's token/header (e.g. an X-API-Key) per its docs. A quick reachability check:

curl -i -X POST https://api.testkube.io/organizations/{organization_id}/environments/{environment_id}/mcp \ -H "Content-Type: application/json" -H "Accept: application/json, text/event-stream" \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Tools

list_workflows — List workflows with filtering
get_workflow — Get workflow details
get_workflow_definition — Get workflow YAML
get_workflow_metrics — Get workflow performance metrics
create_workflow — Create new workflow
update_workflow — Update existing workflow
run_workflow — Execute workflow
list_workflowtemplates — List templates with optional label filtering
get_workflowtemplate_definition — Get template YAML
create_workflowtemplate — Create new template
update_workflowtemplate — Update existing template
list_agents — List available agents for targeting
list_executions — List workflow executions
get_execution_info — Get execution details
get_workflow_execution_metrics — Get resource consumption metrics
get_workflow_resource_history — Analyze resource patterns
fetch_execution_logs — Get execution logs
lookup_execution_id — Resolve execution name to ID
wait_for_executions — Wait for completion
abort_workflow_execution — Cancel running execution
update_execution_tags — Update execution tags
list_artifacts — List execution artifacts
read_artifact — Read artifact content
query_workflows — Query definitions via JSONPath
query_executions — Query execution records via JSONPath
get_workflow_schema — Get TestWorkflow YAML schema
get_execution_schema — Get TestWorkflowExecution schema
build_dashboard_url — Generate dashboard URLs
list_labels — List available labels
list_resource_groups — List resource groups

About MCP

The Model Context Protocol (MCP) is an open protocol Anthropic introduced for connecting LLM-based agents to external tools and data sources. Providers publish MCP servers that expose their API surface as structured, discoverable tools — an MCP-compatible client (Claude Desktop, Cursor, Cline, Continue, etc.) can connect to the server and call its tools without any per-provider integration code.

Browse every MCP server on the APIs.io network or compare with the broader Agent Skill surfaces of the same providers.