Skip to content

Commit 004c339

Browse files
authored
Remove extra deploy step at the end of GitHub instructions
You don't have to re-deploy after adding secrets. But we should tell you to connect to your remote MCP server
1 parent 2ed9c64 commit 004c339

File tree

1 file changed

+2
-8
lines changed

1 file changed

+2
-8
lines changed

src/content/docs/agents/model-context-protocol/getting-started.mdx

Lines changed: 2 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -216,15 +216,9 @@ wrangler secret put GITHUB_CLIENT_ID
216216
wrangler secret put GITHUB_CLIENT_SECRET
217217
```
218218

219-
#### Finally, deploy your MCP server
219+
#### Finally, connect to your MCP server
220220

221-
Run the following command to deploy your MCP server:
222-
223-
```sh
224-
npm run deploy
225-
```
226-
227-
You should now be able to connect to your MCP server using the MCP inspector, and authenticate with GitHub.
221+
Now that you've added the ID and secret of your production OAuth app, you should now be able to connect to your MCP server running at `worker-name.account-name.workers.dev/sse` using the MCP inspector, and authenticate with GitHub.
228222

229223
## Next steps
230224

0 commit comments

Comments
 (0)