Skip to main content

Documentation Index

Fetch the complete documentation index at: https://help.loopiq.com/llms.txt

Use this file to discover all available pages before exploring further.

​
Use LoopIQ MCP Tools

​
What this does

This article explains how LoopIQ MCP tools can be used with compatible AI clients to access governed LoopIQ context and actions. MCP stands for Model Context Protocol. It allows AI clients to discover and call tools exposed by LoopIQ, such as reading records, creating records, searching data, or retrieving operational context.

​
Important safety model

MCP access should follow the same principles as the main LoopIQ application:
  • organization context must be respected
  • user identity should determine allowed access
  • tools should not leak data across organizations
  • actions should be auditable
  • high-impact actions should be reviewed or permission-gated

​
MCP URL

Your administrator will provide the correct MCP server URL and authentication method. For LoopIQ production:
  • https://ai.loopiq.com is the LoopIQ AI domain.
  • https://ai.loopiq.com/mcp is the MCP endpoint when your AI client requires the MCP server path.
Use the exact URL your administrator provides. Some clients ask for the base server URL, while others require the full MCP endpoint.

​
Dynamic organization context

LoopIQ MCP should operate in dynamic tenant mode. The organization should be determined from the authenticated user and selected organization, not from a fixed tenant setting. If a user belongs to more than one organization, be explicit about the intended organization before listing, creating, or updating records.

​
Before you begin

Make sure:
  • your organization has MCP enabled
  • you have a valid access token or supported authentication method
  • your AI client supports MCP
  • your role has permission to access the data or actions you plan to use
  • the organization context is clear if you belong to more than one organization

​
How to use MCP tools safely

  1. Connect your compatible AI client to the LoopIQ MCP server.
  2. Authenticate with the identity or token provided by your organization.
  3. List available tools.
  4. Start with read-only tools such as search, list, or retrieve actions.
  5. Confirm that returned data belongs to the expected organization.
  6. Use create or update tools only when you understand the effect.
  7. Review generated changes in LoopIQ.
  8. Disconnect or rotate credentials if access is no longer needed.

​
Good use cases

MCP tools are useful for:
  • searching LoopIQ records from an AI workspace
  • summarizing related work items
  • preparing release readiness context
  • finding compliance evidence
  • reviewing service request or incident context
  • drafting follow-up actions from existing records
  • connecting AI assistance to governed LoopIQ workflows

​
Avoid these patterns

Do not use MCP tools to:
  • bypass LoopIQ permissions
  • expose customer or organization data to unauthorized AI clients
  • create production-affecting changes without review
  • use stale or shared bearer tokens
  • mix data from multiple organizations in one prompt unless explicitly authorized

​
Troubleshooting

​
No tools are listed

Confirm the MCP URL, authentication token, and organization access.

​
Tools return no data

Check organization context, permissions, filters, and whether the relevant records exist in LoopIQ.

​
A tool returns access denied

Your role may not include the required permission. Contact an organization administrator.