Connect your tools.
Check the connection.

Connect Claude Code to Larridin Router

Sign in to your Larridin organization and open Router setup. The documented installer configures Claude Code. Use the current command and credentials shown for your organization; support for other coding agents should be checked in the app.

1. Review your organization’s enabled models and routing policy.
2. Get your Router credential and installation instructions from the application.
3. Review the installer’s configuration changes, then run the command in your development environment.
4. Start a coding session and confirm that its requests appear in Router analytics.

The installer is served at https://app.larridin.com/api/router-connect/install. Credentials belong in your local setup; do not share them in tickets or documents. If you need to undo setup, use the uninstall instructions shown alongside the installer.

Before a wider rollout, review fallback behavior, provider access, and how your policy handles cache reuse. Pricing and enabled capabilities depend on your organization’s configuration.

Connect the Larridin MCP server

Beta. The connector must be enabled for your organization. You need a Larridin account and an MCP client with remote HTTP and OAuth support. Available tools depend on your role and organization configuration.

Server URL: https://app.larridin.com/mcp/larridin

Claude Code

claude mcp add --transport http larridin https://app.larridin.com/mcp/larridin

Run /mcp in Claude Code and complete the browser sign-in. Then call whoami and confirm that the returned organization is the one you intended to connect.

Other documented clients

Claude Desktop, Cursor, and VS Code are documented remote-MCP clients. Use a version that supports remote HTTP and OAuth. Clients that need a bridge can connect through mcp-remote:

{
  "mcpServers": {
    "larridin": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://app.larridin.com/mcp/larridin"]
    }
  }
}

Add the server using the configuration format supported by your client, restart it, and complete OAuth sign-in. Native remote-server configuration varies by client. The bridge example above is for clients that accept the mcpServers format.

A successful whoami response confirms the user and organization. List the available tools before trying a query; an enabled connector can expose different tools to different roles.

Available tools and data handling

• whoami confirms your authenticated user and organization.
• ask_question asks an organization-scoped question and can continue an existing Ask conversation.
• query_larridin_analytics queries enabled analytics domains, including velocity, quality, AI coding cost, effectiveness, and readiness.

The analytics tools read data rather than editing source systems. Asking a question saves a conversation under your organization’s retention terms. Tool calls are logged. Review the enabled tools and access scopes with your administrator before rollout.

To revoke access, ask your administrator to revoke the OAuth grant or deactivate the user. Removing a server from one client stops local use but is not the same as revoking the grant.

If the connection fails

• 401: complete OAuth sign-in or authenticate again.
• 404 after sign-in: confirm that the MCP server is enabled for your organization.
• A tool is missing: check organization enablement and role access.
• An analytics result is empty: check connected sources, data coverage, and the requested time period.