-
Notifications
You must be signed in to change notification settings - Fork 38
docs: Add instructions for Claude on Auth guide #275
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
base: develop
Are you sure you want to change the base?
Conversation
Using Claude's support documentation and the methods we've been demonstrating on live streams and webinars, this change gives instructions for adding an MCP server to Claude through their Custom Connectors feature.
✅ Docs preview readyThe preview is ready to be viewed. View the preview File Changes 0 new, 5 changed, 0 removed
Build ID: 818eff9e4097c4d6a965fc5d URL: https://www.apollographql.com/docs/deploy-preview/818eff9e4097c4d6a965fc5d |
|
||
In order to get the full experience of using and MCP server authorization, you'll want to use an LLM of some sort. Anthropic's Claude provides an accessible method of connecting to an MCP server, through [their Custom Connector feature](https://support.anthropic.com/en/articles/11175166-getting-started-with-custom-connectors-using-remote-mcp). | ||
|
||
If you'd like to connect your MCP server with Claude, the first thing you need to do is deploy your server behind HTTPS. This is because Claude requires all custom connectors to have URLs that begin with `https`. Whether you do this by providing a local SSL certificate, or deploying to a staging or production environment, is up to you. |
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.
Let's try to be a bit more helpful here. For example we can link to our deployment docs.
And find another one for "providing a local SSL certificate".
@@ -243,6 +243,23 @@ Before continuing, you need to set up the Auth0 client to accept an additional c | |||
|
|||
</ExpansionPanel> | |||
|
|||
### Optional: Connecting to Apollo MCP Server from Claude |
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.
### Optional: Connecting to Apollo MCP Server from Claude | |
## Step 5: Make requests with an MCP Client (Claude) |
This heading is more in line with the rest of the guide.
|
||
If you'd like to connect your MCP server with Claude, the first thing you need to do is deploy your server behind HTTPS. This is because Claude requires all custom connectors to have URLs that begin with `https`. Whether you do this by providing a local SSL certificate, or deploying to a staging or production environment, is up to you. | ||
|
||
To get your MCP server connected to Claude with a Pro or Max plan, follow these steps: |
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.
This should be farther up in the section since it's a pre-requisite to have their Pro
or Max
plan.
@@ -243,6 +243,23 @@ Before continuing, you need to set up the Auth0 client to accept an additional c | |||
|
|||
</ExpansionPanel> | |||
|
|||
### Optional: Connecting to Apollo MCP Server from Claude | |||
|
|||
In order to get the full experience of using and MCP server authorization, you'll want to use an LLM of some sort. Anthropic's Claude provides an accessible method of connecting to an MCP server, through [their Custom Connector feature](https://support.anthropic.com/en/articles/11175166-getting-started-with-custom-connectors-using-remote-mcp). |
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.
Are we not able to use the local dev config to point to the deployed server? We have to use this paid feature?
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.
We could use local dev config, but that requires using the Claude Desktop app and Watson has been demoing this method on live streams. I can rework this section to recommend that method if we want to use it in our docs.
1. Click **Add**. | ||
1. Find your new custom connector and click the **Connect** button. | ||
1. You will be taken to your IdP to log in. Once you log in, you will be redirected back to Claude. | ||
1. Claude will now display the MCP operations available to it under the name you provided and if you give a prompt that would invoke your operations, it should ask permission to access your MCP server. |
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.
Recommend giving a prompt/question they can use that reflects the example project they cloned.
Using Claude's support documentation and the methods we've been demonstrating on live streams and webinars, this change gives instructions for adding an MCP server to Claude through their Custom Connectors feature.