Skip to content

Cursor

Add Tindre as a remote HTTP MCP server in Cursor without placing credentials in a deep link.

Cursor can install the Tindre server from a deep link or ordinary MCP settings. Share only the server address; add the personal credential after installation so it does not remain in chat, browser, or shell history.

  1. 1

    Open Cursor MCP settings

    Use Settings → MCP or an approved deep link that contains only the server configuration.

  2. 2

    Add an HTTP server

    Name it Tindre and use the MCP address shown in Tindre settings.

  3. 3

    Add authorization

    Set Authorization to Bearer followed by your personal access token.

  4. 4

    Verify tools

    Confirm search and call appear, and query appears only when your permissions allow it.

A deep link is still a URL. Credentials embedded in it can survive in messages and history. Let the link prefill the address, then add the header in the configuration Cursor opens.

Team distribution

A team can distribute the server entry through a project configuration or install link. Each developer supplies their own credential and reaches only their own Tindre access.

Troubleshoot permission-shaped differences

If one person sees fewer capabilities than another, compare their Tindre access before changing the MCP configuration. The catalog is filtered before names or schemas are disclosed.

See Credentials for token lifecycle and revocation.