MCP remote server with Adobe IMS/Okta authentication wrapper
MCP Remote With Okta MCP server exists for a simple reason — assistants are far more useful when they can act on MCP Remote With Okta directly instead of describing what you should do. MCP remote server with Adobe IMS/Okta authentication wrapper.
A wrapper for mcp-remote that handles Adobe IMS or Okta authentication using OAuth implicit flow, providing seamless authentication for protected MCP servers.
The server ships on npm as mcp-remote-with-okta, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
You will need 8 environment variables: AUTH_PROVIDER, ADOBE_CLIENT_ID, ADOBE_IMS_ENV, OKTA_CLIENT_ID, OKTA_DOMAIN, DEBUG_MODE, AUTO_REFRESH, NVM_DIR. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
This sits in the file and storage access group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. It is maintained by adobe-rnd; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against MCP Remote With Okta's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
{
"mcpServers": {
"my-mcp-server": {
"command": "npx",
"args": [
"mcp-remote-with-okta",
"https://your-mcp-server.com/mcp"
],
"env": {
"AUTH_PROVIDER": "adobe",
"ADOBE_CLIENT_ID": "your_client_id_here",
"ADOBE_IMS_ENV": "prod"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| AUTH_PROVIDER | Configuration value read at startup. | Optional |
| ADOBE_CLIENT_ID | Configuration value read at startup. | Optional |
| ADOBE_IMS_ENV | Configuration value read at startup. | Optional |
| OKTA_CLIENT_ID | Configuration value read at startup. | Optional |
| OKTA_DOMAIN | Configuration value read at startup. | Optional |
| DEBUG_MODE | Configuration value read at startup. | Optional |
| AUTO_REFRESH | Configuration value read at startup. | Optional |
| NVM_DIR | Filesystem location the server is allowed to use. | Optional |
Scoped local file access — read, write, search and reorganise files in directories you explicitly allow.
Search and read your Drive — Docs, Sheets and files become context your assistant can actually use.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Build a programmable telecommunications stack for connecting telephony services with the Internet via a cloud-based utility.
Chat with your second brain — search, read and write vault notes through the Local REST API.
Connects AI models to an Obsidian knowledge base for direct access and manipulation of notes and folders.