Sign in from Cursor (or another IDE) with OAuth, then call curated Maktby tools. Tokens stay on your machine.
Recommended — use the snippet
1.Copy the snippet for your IDE
Open IDE config and copy the JSON. It already points npx at the hosted .tgz — you usually do not open the file yourself.
2.Paste into MCP settings
Cursor: Settings → MCP (or .cursor/mcp.json). VS Code: .vscode/mcp.json. Windsurf / Claude: use the path shown on each IDE tab.
3.Sign in with maktby_login
Ask the agent to run maktby_login, approve in the browser, then you’re connected. Tokens stay on your machine.
Using the .tgz file
1.Download the .tgz
Use Download MCP package from this dialog. Official Maktby host only — never a random archive.
2.Extract the archive
Open the package folder (package.json, dist/, assets/logo.png, .cursor-plugin/).
3.Cursor: install local plugin (not Add from folder)
Do not use Plugins → Add from folder on Downloads — Cursor runs git and fails. In the package folder run: node scripts/install-cursor-local.mjs then Reload Window. Or just paste the MCP snippet (easier).
4.Defaults to production
Plugin default API base is app.maktby.com. Switch to app-dev only if you used Install for development. Unlock production in Profile when using production.
Stay safe
1.Only use Maktby’s package
Download from this page or the official app / app-dev host. Never put access tokens or passwords in mcp.json.
2.Tokens stay in your IDE
This page never shows access tokens. Remove a connection anytime under Active connections.
3.Production needs an unlock
Development works without the switch. Production install needs Allow production API access first.
{
"mcpServers": {
"maktby": {
"command": "npx",
"args": ["-y", "https://app-dev.maktby.com/downloads/maktby-mcp-server.tgz"],
"env": {
"MAKTBY_API_BASE": "https://app-dev.maktby.com"
}
}
}
}For production, set MAKTBY_API_BASE to https://app.maktby.com and MAKTBY_DEVELOPER=1, and enable developer access on your profile.