For the complete documentation index, see llms.txt. This page is also available as Markdown.

Connecting to an MCP Server

The Control Tower MCP server speaks the standard Model Context Protocol, so any compliant client can connect to it (Claude Desktop, Claude Code, Cursor, VS Code, or your own agent built on an MCP SDK).

Before you start

  • At least one connector onboarded and scanned. The server reports on data Control Tower has already collected; it does not scan anything itself. See the Connector Onboarding Guide.

  • A Control Tower credential. The agent inherits that credential's connector scope and it sees exactly what the credential is entitled to see, and nothing else.

  • Admin access to Claude. You need to be able to add new connectors to Claude.

Create your OAuth Client

In Datalogz Control Tower:

  1. Go to Settings > OAuth Clients.

  2. Click New OAuth Client.

  3. Fill out the following fields:

Value
Description

Name

The name you choose for the Client.

Type

You can create two types of OAuth clients. For the MCP oAuth client, you select the Interactive PKCE type.

Redirect URIs

Select or fill out the callback URIs. If you want to add the MCP server to Claude or Copilot, you can select the predefined URIs.

Advanced - Connector access

Limit the scope of the MCP server by linking it to a specific connector. Leave this part blank to allow the tool to search every connector your credential can reach; pass one and the tool answers for that connector alone.

  1. Click Create.

  2. Copy the Client ID.

In Claude:

  1. Go to Organization Settings.

  2. Click Connectors > + Add

  3. Select Custom and then Web.

  4. Fill out the following fields:

Value
Description

Name

The name you choose for the MCP server.

Remote MCP server URL

Type https://app.datalogz.io/mcp

Troubleshooting

  • Every call returns an authorization error. The token is missing, expired, or was issued for a different environment. Reissue it in Settings > OAuth Clients.

  • A tool returns nothing at all. Your credential may have no access to the connector in question.

  • A platform-specific tool refuses your asset. Usage, viewer, workspace-access and capacity tools are Power BI only. Similarity is Power BI and Tableau. Downstream impact is Power BI, Tableau and Sigma. See the Tool reference.

  • Numbers look stale. The server reads what the last connector scan wrote. Check scan status in the app rather than retrying the query.

Last updated