Skip to main content

What This Does

This catalog explains the tools and actions exposed by the LoopIQ MCP server. The MCP server exposes four kinds of tools:
  • fixed governance and workflow tools
  • Analytics Platform tools
  • AI/ML agent runner tools
  • generated resource and route tools from the guarded LoopIQ API catalog
Because part of the surface is generated from the backend route catalog, the exact live list can vary by deployment, tenant policy, role, and server configuration. Use loopiq_list_routes, loopiq_list_resources, loopiq_list_ai_ml_agents, and the MCP client’s tools/list command to discover the authoritative live list.

Current Catalog Snapshot

The checked-in MCP catalog generated on August 30, 2026 contains:
  • 551 unique MCP tools
  • 922 guarded LoopIQ API routes
  • 128 callable AI/ML agents
  • 399 GET, 234 POST, 153 PATCH, and 136 PUT routes
These figures describe the current source catalog, not an entitlement guarantee. The server filters the tools a caller can use through authentication, tenant membership, scopes, route policy, role permissions, and deployment configuration.

Authentication and Tenant Resolution

LoopIQ MCP supports two authentication modes without weakening the tenant boundary: The protected MCP resource is https://ai.loopiq.com/mcp. Human access tokens must carry the dedicated MCP OIDC audience. Bot tokens use the MCP resource as their audience and cannot select or switch tenants through tool arguments. Bot tokens normally receive mcp:tools:read. A bot needs both mcp:tools:write and the applicable LoopIQ authorization to invoke mutations. Approval requirements, dry-run behavior, tenant checks, idempotency, and audit recording continue to apply to bot calls. MCP never forwards a resource-bound bot token to the LoopIQ backend. After validating the bot, it creates a separate 60-second API-delegation token. The backend validates that token against the registered bot, its owner, tenant, scopes, and credential version.

Core Safety and Reliability Tools

Release Governance Tools

Test Automation Execution and Evidence Tools

Automated test runs are first-class MCP tools. They are not available only through generic route invocation. Dry runs remain diagnostic and are not treated as governed release-readiness evidence. Requirement-aware assertion validation and evidence retrieval expose the governed result separately from diagnostic output.

Test Migration, Data, and Portfolio Tools

Manual Test Governance and Execution Tools

Additional list, get, create, and update tools for tests, suites, plans, baselines, snapshots, folders, shared steps, execution queues, defects, and time entries are generated from the semantic resource catalog.

Generated Package and Runtime Governance Tools

Atlassian and Provider-Neutral External Resource Tools

Generated semantic tools also expose providers, connections, containers, accounts, identities, work items, attachments, relationships, mapping profiles, synchronization cursors, governed actions, and outbound-action history. The canonical model supports Jira, JSM, Confluence, Compass, Bitbucket, Assets, and future providers without requiring separate MCP schemas.

Remediation and Governed Work Creation

Required or common fields:
  • tenantId
  • story
  • tasks
  • approvalId
  • idempotencyKey
  • dryRun
Use dryRun: true before executing a real write. Approve only when the story and tasks reference the correct release, certification, team, provider blockers, failed controls, and evidence records.

Incident and Change Governance Tools

Team, User, Role, and Onboarding Tools

Analytics Platform Tools

Dashboard Tools

Forms, Custom Fields, Automation, Sla, and Approval Policy Tools

AI/ML Agent Tools

The server exposes loopiq_list_ai_ml_agents plus one first-class tool for each AI/ML platform agent. Each loopiq_run_*_agent tool calls the LoopIQ AI proxy with the agent’s use_case. Common input fields:
  • tenantId
  • payload
  • prompt
  • action
  • dryRun
Either payload or prompt is required. Agent tool IDs are generated directly from the runtime agent_id; they do not use a universal _agent suffix. Representative current tools are: Some agents are write-capable and require approval, including the current automation runner, backlog generator, deployment, planner, response drafter, rollback, runbook generator, test-case generator, and work-breakdown agents. Inspect approvalRequirement and writeCapability returned by loopiq_list_ai_ml_agents instead of inferring safety from a tool name. Use loopiq_list_ai_ml_agents or tools/list for all 128 current IDs, input/output schemas, workflow packs, grounding sources, engines, and approval requirements.

Generated Semantic Resource Tools

The MCP server promotes common backend resources into semantic tools with predictable names:
  • loopiq_list_<resource>
  • loopiq_get_<resource>
  • loopiq_create_<resource>
  • loopiq_update_<resource>
  • loopiq_execute_<resource_action> when a resource has a supported action route
Examples include:
  • loopiq_list_ideas, loopiq_get_idea, loopiq_create_idea, loopiq_update_idea
  • loopiq_list_stories, loopiq_get_story, loopiq_create_story, loopiq_update_story
  • loopiq_list_tasks, loopiq_get_task, loopiq_create_task, loopiq_update_task
  • loopiq_list_features, loopiq_get_feature, loopiq_create_feature, loopiq_update_feature
  • loopiq_list_applications, loopiq_get_application, loopiq_create_application, loopiq_update_application
  • loopiq_list_modules, loopiq_get_module, loopiq_create_module, loopiq_update_module
  • loopiq_list_test_cases, loopiq_get_test_case, loopiq_create_test_case, loopiq_update_test_case
  • loopiq_list_evidence_dossiers, loopiq_get_evidence_dossier, loopiq_create_evidence_dossier, loopiq_update_evidence_dossier
The generated semantic tool list is capped by the server’s semantic resource limit, which currently defaults to 250. The server prioritizes external integrations, release governance, delivery work, compliance, testing, automation, and operational workflows. Named promoted tools do not depend on the semantic-resource selection order.

Generated Route Catalog Actions

The current checked-in route catalog contains 922 tenant-safe route definitions. Current catalog coverage includes:
  • 399 GET routes
  • 234 POST routes
  • 153 PATCH routes
  • 136 PUT routes
High-coverage route families include:
  • automation
  • release certifications
  • applications and modules
  • ideas, features, stories, tasks, and issues
  • incidents, service requests, change requests, and enhancement requests
  • compliance objectives, key results, evidence dossiers, approvals, exceptions, and deviations
  • test plans, suites, cases, executions, and runs
  • integrations, provider evidence, GitHub metrics, and security operations
  • notifications, forms, custom fields, workgraph, and integrated documents
Use loopiq_list_routes to inspect the current route catalog. Use loopiq_invoke_route only when no semantic tool exists for the workflow.

Blocked or Excluded Actions

The MCP server intentionally excludes or blocks:
  • DELETE operations
  • platform administration routes
  • permission override routes
  • super-admin routes
  • password reset and invitation flows
  • schema and documentation routes
  • API key management routes
  • routes that are not tenant scoped
  1. Use a named semantic tool when one exists.
  2. Use the release governance tools for certification and evidence graph workflows.
  3. Use loopiq_list_resources and generic record tools for normal CRUD.
  4. Use loopiq_list_routes and loopiq_invoke_route only for long-tail routes.
  5. Use dryRun: true before write actions.
  6. Require explicit approval for high-impact actions.
  7. Store request ID, trace ID, approval ID, and idempotency key in your custom agent audit trail.
For a bot, also retain the bot ID and credential version in the audit context. Never store a bot client secret or short-lived access token in logs, prompts, tool arguments, or evidence records.