Connect an AI client to CTK with read-only MCP

01

1. Prepare the projects and account

Connect the repositories you want to inspect and collect observations with their watches. Sign in with Developer or Team access. Open Settings, then Integrations.

MCP returns recorded service states, history, alarm evidence and relation evidence within the approved scope. It does not run a new connector probe just because the client asks a question. An old snapshot must still be described as old.

02

2. Give narrow, explicit consent

Enter a recognizable client name and select only the projects needed for this client. Review the sharing disclosure and the remembered-connection acknowledgement before granting permission.

Your AI provider can receive the selected projects’ approved observations and relationship evidence. The MCP responses exclude source code, raw logs, endpoints and raw correlation keys, but project names and operational observations are still information you are choosing to share.

03

3. Install the connection for the intended client

Select the intended client after creating its consent. For Cursor, use CTK’s native installation action and confirm adding the server in Cursor. For clients offering an exported installation package, follow the instructions included with that local export.

The package or link is specific to this Mac and permission, not a generic public marketplace installer. Replacing an installation replaces that permission’s transport key. Use separate consents for separate clients instead of repeatedly replacing one shared setup.

04

4. Verify an actual read

Keep CTK open and ask a short question such as “What is happening with orders-engine?” Replace that example with the name of an approved project. The client must actually use the CTK tools; a fluent answer alone is not proof of a connection.

Return to Integrations and check for a verified data request. Opening an install link or saving an archive is a setup step, not proof that evidence was read. If the client cannot connect, check its enablement, the selected scope and CTK’s access status before changing the project.

05

5. Understand restart and revocation

Remembered permissions can survive an app restart under the same login, subject to fresh entitlement and scope checks. Closing CTK suspends availability. Signing out, switching accounts or starting a fresh login invalidates those bindings.

Revoke a client in Integrations when it no longer needs access. Existing watches continue independently. A revoked permission blocks future reads; it cannot retract evidence the AI client already received. If CTK reports that a revocation could not be saved, retry rather than treating it as complete.

06

What this connection cannot do

The five CTK tools list approved repositories and read snapshots, history, alarms and relations. They cannot execute commands, start or stop services, edit files, create commits or open pull requests. Your client uses its own AI account and provider; CTK does not supply the inference budget.