Connect your AI
Connect Encodr to Claude, ChatGPT, or any assistant that supports MCP, and it can read your real progress, spot what you keep failing, and write new cards straight into your account.
https://mcp.encodr.app/mcp
Works the same in the browser and the desktop app - they share one connector list, so you only ever do this once.
On the web, click your name in the bottom-left, choose Settings, then Connectors. In the desktop app, open Settings from the menu and go to the same place.
Click Add custom connector. Paste the URL above into the connector URL field. You can name it anything - "Encodr" works.
A sign-in page opens. Use the same @handle and password you use in Encodr - there is no separate account to make.
Claude will show what it is allowed to do. Approve it, and the connector appears in your list. Ask Claude something from the list below to check it works.
Custom connectors are behind a flag. Open Settings, go to Connectors, and enable Developer mode. On a Business or Enterprise workspace an admin may need to allow it first.
In Connectors, choose to add one, then paste the URL above as the MCP server URL. Name it "Encodr" and give it a short description so the model knows when to reach for it.
Sign in with your Encodr @handle and approve the access screen. Encodr uses OAuth, so ChatGPT never asks you for an API key.
Reading works on any paid plan. Creating decks and cards needs a Business, Enterprise, or Edu workspace - on an individual Plus or Pro account, custom connectors are read-only, so Encodr can tell you what you're weak on but cannot write new cards for you.
Encodr uses the Model Context Protocol, so any assistant that supports remote MCP servers can connect. The setting is usually called MCP servers, connectors, or integrations. Gemini CLI, Cursor, and Zed all work this way - you add the URL to a config file rather than a settings screen.
Paste the URL above. Encodr uses OAuth, so the assistant will send you to an Encodr sign-in page rather than asking for an API key. If a client asks for a key, it does not support OAuth-based MCP servers.
Sign in with your Encodr @handle and approve access.
Make sure the URL ends in /mcp. A URL without that path is the sign-in site, not the connector endpoint, and clients will fail to discover it.
That usually means the connector was added twice. Open Encodr, go to You, and check Connected AIs - disconnect the duplicates, then reconnect once.
In Encodr, open the You tab and find Connected AIs. Disconnecting there revokes access immediately, even if the assistant still lists the connector.
No. The connection acts as you, with exactly the permissions your own account has. Decks shared with you are readable; nothing else is.