-
Notifications
You must be signed in to change notification settings - Fork 6
BYOC MCP Prompts #281
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BYOC MCP Prompts #281
Changes from 4 commits
4a378d6
bd41be2
5cdf77b
6152603
465901e
bf2d49f
bbec805
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -14,13 +14,19 @@ This tutorial will show you how to deploy your services to your own AWS account | |
* [The Defang CLI](/docs/getting-started#install-the-defang-cli) | ||
* [AWS Account Credentials](https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-authentication.html) | ||
|
||
## Step 1 - Navigate to your project directory | ||
:::warning["MCP Pre-requisite"] | ||
If you would like to deploy using [MCP](https://modelcontextprotocol.io/), you like need to setup the [Defang MCP Server](../concepts/mcp.md) with the IDE of your choice. | ||
::: | ||
|
||
## CLI | ||
|
||
### Step 1 - Navigate to your project directory | ||
Head to the folder where your project is located. | ||
```bash | ||
$ cd path/to/your/project | ||
``` | ||
|
||
## Step 2 - Authenticate Defang to use your AWS Account | ||
### Step 2 - Authenticate Defang to use your AWS Account | ||
|
||
There are many ways to authenticate your [AWS account](https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-authentication.html). | ||
|
||
Once you've done that, Defang will look for your AWS credentials in your shell environment and expect to find one of the following credential sets: | ||
|
@@ -31,7 +37,7 @@ Once you've done that, Defang will look for your AWS credentials in your shell e | |
If you have the AWS CLI installed (which is not required in order to use the Defang CLI), you can verify that you've authenticated to AWS by running `aws sts get-caller-identity` and see your account ID. | ||
::: | ||
|
||
## Step 3 - Deploy | ||
### Step 3 - Deploy | ||
|
||
Invoke the `defang compose up` CLI command with the `--provider=aws` flag or set the `DEFANG_PROVIDER=aws` environment variable. | ||
|
||
|
@@ -41,10 +47,38 @@ For example: | |
$ defang compose up --provider=aws | ||
``` | ||
|
||
## Step 4 - Inspect your deployment | ||
### Step 4 - Inspect your deployment | ||
|
||
Defang will provision resources in your AWS account and deploy your services. You can inspect the resources created in your AWS Dashboard. | ||
|
||
--- | ||
|
||
## MCP | ||
|
||
### Step 1 - Navigate to your project directory with your IDE | ||
Navigate to your project directory and open it in an IDE that has the [Defang MCP Server](../concepts/mcp.md) installed. | ||
|
||
:::tip | ||
If the Defang MCP server doesn’t start automatically, try starting or restarting it from your IDE settings. | ||
 | ||
::: | ||
|
||
### Step 2 - Setting your provider | ||
In your chat window, type `/mcp.defang.AWS_Setup` or select the corresponding prompt from your IDE’s options. | ||
|
||
 | ||
|
||
The [MCP prompt](https://modelcontextprotocol.io/specification/2025-06-18/server/prompts) accepts two types of credentials: | ||
* the AWS Profile arguement (skip the rest of the prompts after entering the AWS Profile) | ||
* or, the AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, and AWS_REGION arguments | ||
|
||
### Step 3 - Deploy | ||
Once the prompt completes without errors, your chat input will be automatically populated with the deployment command for the LLM to execute. | ||
|
||
|
||
### Step 4 - Inspect your deployment | ||
You can check the status of your depolyment by using the [Defang Services tool](../concepts/mcp#services) or you can inspect the resources created in your AWS Dashboard. | ||
|
||
|
||
*** | ||
|
||
For a deeper discussion of the Defang AWS Architecture, including a list of the resources we provision in your account, see our [AWS Provider docs](/docs/providers/aws). |
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -15,17 +15,23 @@ This tutorial will show you how to deploy your services to your own GCP project | |
* [gcloud CLI](https://cloud.google.com/sdk/docs/install) | ||
* [GCP Account Credentials](https://cloud.google.com/docs/authentication/set-up-adc-local-dev-environment) | ||
|
||
## Step 1 - Navigate to your project directory | ||
:::warning["MCP Pre-requisite"] | ||
If you would like to deploy using [MCP](https://modelcontextprotocol.io/), you like need to setup the [Defang MCP Server](../concepts/mcp.md) with the IDE of your choice. | ||
::: | ||
|
||
## CLI | ||
|
||
### Step 1 - Navigate to your project directory | ||
Head to the folder where your project is located. | ||
```bash | ||
$ cd path/to/your/project | ||
``` | ||
|
||
## Step 2 - Authenticate Defang to use your GCP Account | ||
### Step 2 - Authenticate Defang to use your GCP Account | ||
|
||
|
||
After signing in to your GCP account, select an existing project or [create a new project](https://developers.google.com/workspace/guides/create-project). Make sure [billing is enabled](https://cloud.google.com/billing/docs/how-to/modify-project). Then, note down the project ID and set it as environment variable `GCP_PROJECT_ID`. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Do we need a link to instructions on how to sign in to the GCP account (similar to how we have that for AWS)? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Well not really because we have a list of pre recs and they have to have all that to be able to use this feature. Unless you think we should point that out specifically here. |
||
|
||
## Step 3 - Deploy | ||
### Step 3 - Deploy | ||
|
||
Invoke the `defang compose up` CLI command with the `--provider=gcp` flag or set the `DEFANG_PROVIDER=gcp` environment variable. | ||
|
||
|
@@ -35,10 +41,39 @@ For example: | |
$ defang compose up --provider=gcp | ||
``` | ||
|
||
## Step 4 - Inspect your deployment | ||
### Step 4 - Inspect your deployment | ||
|
||
Defang will provision resources in your GCP account and deploy your services. You can inspect the resources created in your [GCP Dashboard](https://console.cloud.google.com/). | ||
|
||
--- | ||
|
||
## MCP | ||
|
||
### Step 1 - Navigate to your project directory with your IDE | ||
Navigate to your project directory and open it in an IDE that has the [Defang MCP Server](../concepts/mcp.md) installed. | ||
|
||
:::tip | ||
If the Defang MCP server doesn’t start automatically, try starting or restarting it from your IDE settings. | ||
 | ||
::: | ||
|
||
### Step 2 - Authenticate Defang to use your GCP Account | ||
|
||
|
||
After signing in to your GCP account, select an existing project or [create a new project](https://developers.google.com/workspace/guides/create-project). Make sure [billing is enabled](https://cloud.google.com/billing/docs/how-to/modify-project). Then, note down the project ID for the next step. | ||
|
||
### Step 2 - Setting your provider | ||
In your chat window, type `/mcp.defang.GCP_Setup` or select the corresponding prompt from your IDE’s options. | ||
|
||
 | ||
|
||
The [MCP prompt](https://modelcontextprotocol.io/specification/2025-06-18/server/prompts) will require your GCP project ID you created in [Step 2](#step-2---authenticate-defang-to-use-your-gcp-account-1). | ||
|
||
### Step 3 - Deploy | ||
Once the prompt completes without errors, your chat input will be automatically populated with the deployment command for the LLM to execute. | ||
|
||
### Step 4 - Inspect your deployment | ||
You can check the status of your depolyment by using the [Defang Services tool](../concepts/mcp#services) or you can inspect the resources created in your GCP Dashboard. | ||
|
||
*** | ||
|
||
For a deeper discussion of the Defang GCP Architecture, see our [GCP docs](/docs/providers/gcp). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure about this "Authenticate Defang " terminology - should it be something like "Allow Defang to use your AWS Account"? (similar for other cloud providers)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm, the word “Authenticate” was already there before, so I thought I’d just leave it. But in this case, we’re not really authenticating with Defang—we’re authenticating into AWS so that Defang can use your credentials.
I think this wording works better: “Allow Defang to use your AWS Account.” It’s simpler and easier to understand for readers at all levels.