Skip to main content
Lerix exposes a remote MCP server so an AI coding agent can work with your real Lerix data instead of you copying IDs and SDK keys back and forth by hand. The agent authenticates as you, through a normal browser login — it never sees or stores a password or API key, and it can only see and change what your own account already has permission to.
Every write action (creating a project, resolving an issue, and so on) requires the agent to pass an explicit confirmation flag, which a well-behaved agent will only do after asking you. Read actions (listing orgs, projects, issues) don’t require confirmation.

​
Connect Claude Code

Then, in a Claude Code session, run:
Pick lerix — your browser opens to the Lerix consent screen, where you log in (or reuse an existing session) and approve the connection. Claude Code stores and refreshes the resulting token itself; you only do this once per machine. If you’d rather install it as a full plugin (bundles a skill that sequences the tools for common workflows, like connecting a project end-to-end):

​
Connect Replit

In Replit Agent: Integrations → MCP Servers → + Add MCP server, then paste:
Replit discovers the OAuth configuration automatically and walks you through the same browser sign-in.

​
Other MCP clients

Any client that supports a remote MCP server over HTTP with OAuth 2.1 (dynamic client registration + PKCE) can connect the same way — point it at https://mcp.lerix.dev/mcp and complete the sign-in when prompted. There’s no API key to generate or paste in.

​
What it can do

Read (no confirmation needed): Create / connect (requires confirmation): Write (requires confirmation):

​
Security notes

  • All access is scoped by your existing organization/project permissions — the agent can’t see or change anything your account couldn’t already.
  • Nothing the agent connects to can read your password. Sign-in happens on app.lerix.dev itself, the same login you already use.
  • To disconnect a client, remove the server from it directly (e.g. claude mcp remove lerix). If you believe a specific token was compromised, contact support@lerix.dev.
  • configure_android_push and configure_ios_push ask you to paste a real push-provider credential (a Firebase service-account key, or an APNs .p8 key) into the chat. That text passes through your AI tool the same way any other message does — only paste it into a client and session you trust.