docs: add combined mcp docs #8477
Merged
Conversation
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
pranavosu
requested review from
a team,
ShadowCat567 and
harsh62
as code owners
sarayev
previously approved these changes
Dec 1, 2025
Simone319
reviewed
Dec 1, 2025
| import { getCustomStaticPath } from '@/utils/getCustomStaticPath'; | ||
|
|
||
| export const meta = { | ||
| title: 'Set up AWS MCP Server', |
Contributor
There was a problem hiding this comment.
Can we instead of creating our own doc for setting up AWS MCP Server, redirect to the AWS MCP Server official doc? So that we don't have to worry about keep them in sync.
|
|
||
| ## Frontend Integration workflow | ||
|
|
||
| The Frontend Integration workflow helps you connect your frontend application to Amplify backend services. It provides framework-specific patterns and best practices. |
Member
There was a problem hiding this comment.
I think that this is maybe missing that the frontend SOP can be applied to already existing frontend applications. I know that this is implied with this sentence, but maybe we should make it a bit more obvious.
src/pages/[platform]/start/mcp-server/amplify-workflows/index.mdx
Outdated
Show resolved
Hide resolved
Simone319
approved these changes
Dec 2, 2025
sarayev
approved these changes
Dec 2, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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 of changes:
Add documentation for the new MCP server workflow integrations.
Related GitHub issue #, if available:
Instructions
If this PR should not be merged upon approval for any reason, please submit as a DRAFT
Which product(s) are affected by this PR (if applicable)?
Which platform(s) are affected by this PR (if applicable)?
Please add the product(s)/platform(s) affected to the PR title
Checks
Does this PR conform to the styleguide?
Does this PR include filetypes other than markdown or images? Please add or update unit tests accordingly.
Are any files being deleted with this PR? If so, have the needed redirects been created?
Are all links in MDX files using the MDX link syntax rather than HTML link syntax?
ref: MDX:
[link](https://docs.amplify.aws/)HTML:
<a href="https://docs.amplify.aws/">link</a>When this PR is ready to merge, please check the box below
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.