Connecting the Intely MCP Server

The Intely MCP server lets an AI assistant — Claude Desktop, Claude Code, Cursor, a JetBrains IDE — work directly against your Intely organization: list and inspect integrations, mappings, data types and app instances, run them, and read execution results, without leaving the assistant.

It is a remote MCP server at https://mcp.intely.io/mcp. Nothing is installed on your machine beyond your assistant's own config file.

Before you start

You need two values:

The organization ID is passed as a query parameter, so a single assistant can be pointed at different organizations by swapping it.

Choosing the right config shape

There are only two, and which one you need depends on your client, not on your operating system:

Clients that speak remote HTTP (Cursor, Claude Code, and most recent clients) take the URL and headers directly:

{
  "mcpServers": {
    "intely": {
      "url": "https://mcp.intely.io/mcp?organizationId=[organization-id]",
      "headers": { "Authorization": "Bearer [token]" }
    }
  }
}

Clients that only speak STDIO (Claude Desktop, JetBrains) need mcp-remote as a bridge, and here the OS does matter:

Windows

{
  "mcpServers": {
    "intely": {
      "command": "npx",
      "args": ["-y", "mcp-remote",
               "https://mcp.intely.io/mcp?organizationId=[organization-id]",
               "--header", "Authorization:${AUTH_HEADER}"],
      "env": { "AUTH_HEADER": "Bearer [token]" }
    }
  }
}

macOS / Linux

{
  "mcpServers": {
    "intely": {
      "command": "sh",
      "args": ["-c",
               "npx -y mcp-remote 'https://mcp.intely.io/mcp?organizationId=[organization-id]' --header 'Authorization: ${AUTH_HEADER}'"],
      "env": { "AUTH_HEADER": "Bearer [token]" }
    }
  }
}

The macOS/Linux variant wraps the whole command in sh -c because the header value contains a space, which the direct-npx form does not quote correctly.

Per-client notes

• Claude Desktop — edit claude_desktop_config.json, then fully quit and relaunch. The app must be closed when you write the file.
• Claude Code — a .mcp.json in the project root, using the remote-HTTP shape with "type": "http". Or add it with claude mcp add.
• Cursor — remote-HTTP shape.
• JetBrains — STDIO shape for your OS.

Verifying it works

Ask the assistant to list your apps or your integrations. A successful call returns your organization's records; an auth failure surfaces as a 401 from mcp.intely.io.

Token handling

The token is a long-lived bearer credential for your organization. Treat it like a password:

• Keep it in the env block or your client's secret store, not pasted inline into shared files.
• Do not commit a populated .mcp.json to a repository.
• Rotate it by requesting a new one; issue separate tokens per machine so one can be revoked alone.