Repository navigation
Fix ER MCP docs: Use API token instead of submission token - #3712
Merged
Merged
Conversation
karansharmasauce
requested review from
adamcronin42,
anupam-sl,
neerav-mittal and
sararasmussen
as code owners
October 8, 2026 13:21
|
Deploy preview ready for 3712! |
neerav-mittal
approved these changes
Oct 9, 2026
|
Deploy preview ready for 3712! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Updates the ER MCP setup doc to create an API token (Project > API tokens) instead of a submission token, adjusts the steps and token wording to match, and replaces the token screenshots.
Motivation and Context
The doc told users to create a submission token, but the MCP access-token connection needs an API token.
Types of Changes