Remote Id
Remote proxy for Model Context Protocol, allowing local-only clients to connect to remote servers using oAuth
Ask AI about Remote Id
Powered by Claude · Grounded in docs
I know everything about Remote Id. Ask me about installation, configuration, usage, or troubleshooting.
0/500
Reviews
Documentation
mcp-remote-id
A fork of mcp-remote that adds support for using id_tokens as Bearer tokens when authenticating with remote MCP servers.
Why this fork?
The upstream mcp-remote always sends the OAuth access_token as the Bearer token. However, some OAuth providers do not include identity claims (email, groups, etc.) in access tokens by default, making them insufficient for authorization decisions on the server side. The id_token contains these claims and is what remote MCP servers need to identify and authorize users.
This fork adds a --token-type flag that lets you send the id_token instead.
What changed
- Added
--token-typeCLI argument (access_token|id_token, defaults toaccess_token) - When
--token-type id_tokenis set, theid_tokenfrom the OAuth token response is swapped into the Bearer header - No behavior change when the flag is omitted — fully backwards compatible with upstream
Usage
{
"mcpServers": {
"remote-example": {
"command": "npx",
"args": [
"-y",
"mcp-remote-id",
"https://remote.mcp.server/sse",
"--token-type", "id_token"
]
}
}
}
To use the default access_token behavior, simply omit --token-type:
{
"mcpServers": {
"remote-example": {
"command": "npx",
"args": [
"-y",
"mcp-remote-id",
"https://remote.mcp.server/sse"
]
}
}
}
