mcp-remote bridge. Authorize with OAuth (browser sign-in) or an API key.
mcp-remote runs via npx, so you need Node.js installed. No global install
is required.Option A — OAuth (sign in)
1
Add the server
Edit
.kiro/settings/mcp.json (workspace) or ~/.kiro/settings/mcp.json
(user):2
Authorize
Kiro reloads MCP servers automatically. On first connect,
mcp-remote opens
your browser to sign in to Keupera and Allow access.Option B — API key
Verify and use
Confirmkeupera is connected in Kiro’s MCP view, then ask, for example:
“Show my top keyword opportunities and outline an article for the best one.”
Kiro MCP docs →
Troubleshooting
Server won't start
Server won't start
Confirm Node.js is installed (
node --version) and the JSON is valid. Kiro
reloads automatically, but you can restart it to force a reload.Browser sign-in doesn't open
Browser sign-in doesn't open
Clear the cached auth and retry: delete the
mcp-remote cache in
~/.mcp-auth (or the path printed on startup), then reload the server.