Skip to main content
Entelligence supports Model Context Protocol (MCP) access for compatible clients. The current connection details can vary by deployment and client.

​
Before you begin

You need:
  • An Entelligence workspace
  • Access to Settings → API
  • Permission to create or use an API key
  • An MCP-compatible client
  • Approval for the repositories and connected sources the client can access

​
Create a credential

Open Settings → API and select Create Key when that action is available. The current screen can show a masked key, created date, and Copy, Rotate Key, and Delete Key actions.
Treat the key as a secret. Rotating or deleting it can stop every CLI or MCP client that uses it. Store it in a secret manager or the client’s secure credential store—never in a repository.

​
Use the current configuration

Use the MCP URL, transport, authentication format, and client snippet displayed by Entelligence or supplied for the deployment. Do not construct a URL or authorization header from an example in this guide. Copy the current value from the app and follow the installed client’s configuration format. For Cursor, Claude, Codex, VS Code, or another client:
  1. Open the client’s MCP settings.
  2. Add a server named Entelligence.
  3. Paste or translate the deployment-provided configuration without exposing the key.
  4. Reload the client.
  5. Confirm the server connects.
If the app supplies only a key and no MCP endpoint or snippet, contact the workspace administrator or Entelligence support rather than guessing the endpoint.

​
Manage MCP from the CLI

The CLI provides three MCP commands:
Run entelligence mcp <subcommand> --help to confirm supported clients and required arguments. Inspect status before uninstalling or replacing a working configuration.

​
Verify the connection

  1. Open the client’s MCP tools or server view.
  2. Confirm the Entelligence server is connected.
  3. Ask the client to list the Entelligence capabilities it can currently discover.
  4. Run one read-only query against a known pilot repository.
  5. Compare the answer and source references with Entelligence.
  6. Confirm an out-of-scope repository is unavailable.
  7. Keep write confirmation enabled until a separate write test is approved.

​
Use MCP safely

  • Start with read-only tasks.
  • Keep client confirmation enabled for write tools.
  • Review repository, ticket, channel, document, or automation destinations.
  • Use one key per named owner or workload where supported.
  • Rotate under change control.
  • Revoke immediately after suspected exposure.
  • Keep client logs free of credentials and sensitive tool payloads.

​
Common problems

​
Rotate or revoke

  1. Inventory clients using the key.
  2. Rotate in Settings → API.
  3. Update each client’s secure configuration.
  4. Verify a read-only call.
  5. Remove the old secret from local and CI stores.
  6. Use Delete Key only when no client depends on it.

​
Next step

Review API keys and MCP administration or enterprise network requirements.