You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/source/deploy.mdx
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,12 +19,12 @@ For most production deployments, use the all-in-one [Apollo Runtime Container](/
19
19
20
20
### Deploy the Apollo Runtime Container
21
21
22
-
The Apollo Runtime Container includes all services necessary to serve GraphQL and MCP requests, including Apollo Router and Apollo MCP Server. Both port `4000` (GraphQL) and `5000` (MCP) are exposed.
22
+
The Apollo Runtime Container includes all services necessary to serve GraphQL and MCP requests, including Apollo Router and Apollo MCP Server. Both port `4000` (GraphQL) and `8000` (MCP) are exposed.
Copy file name to clipboardExpand all lines: docs/source/guides/auth-auth0.mdx
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -31,7 +31,7 @@ This guide uses [Auth0](https://auth0.com/) as the Identity Provider.
31
31
1. In your dashboard, navigate to **Applications** -> **APIs**.
32
32
1. Click **Create API**.
33
33
1. Give it a friendly name like `MCP Auth API`.
34
-
1. For the **Identifier** field, Auth0 recommends using a URL. This identifier is used in the MCP server configuration later as the `audience` property. For this guide, use `http://localhost:5000/mcp-example`.
34
+
1. For the **Identifier** field, Auth0 recommends using a URL. This identifier is used in the MCP server configuration later as the `audience` property. For this guide, use `http://localhost:8000/mcp-example`.
35
35
1. Leave the defaults for the rest of the fields and click **Create**.
36
36
1. Navigate to your dashboard **Settings**.
37
37
1. Under **General** -> **API Authorization Settings**, set the **Default Audience** to the `Identifier` you chose.
@@ -89,14 +89,14 @@ Configure the MCP server to use the Auth0 instance for authentication.
89
89
- https://<AUTH0 DOMAIN> # Fill in your Auth0 domain
90
90
audiences:
91
91
- <AUTH0 DEFAULT AUDIENCE> # Fill in your Auth0 Identifier
92
-
resource: http://127.0.0.1:5000/mcp
92
+
resource: http://127.0.0.1:8000/mcp
93
93
scopes:
94
94
- read:users # Adjust scopes as needed
95
95
```
96
96
97
97
1. Replace the `<AUTH0 DOMAIN>` with your own Auth0 domain from earlier.
98
98
99
-
1. Replace the `<AUTH0 DEFAULT AUDIENCE>` with the matching `Identifier` you set when creating the Auth0 API. In this guide, you used `http://localhost:5000/mcp-example`.
99
+
1. Replace the `<AUTH0 DEFAULT AUDIENCE>` with the matching `Identifier` you set when creating the Auth0 API. In this guide, you used `http://localhost:8000/mcp-example`.
100
100
101
101
Your MCP server is now configured to use Auth0 for authentication.
102
102
@@ -188,7 +188,7 @@ You need a graph's credentials and a valid GraphOS plan to use the router's auth
188
188
189
189
The browser should open automatically with a proxy auth token.
190
190
191
-
1. In the MCP Inspector, select `Streamable HTTP` as the Transport Type and enter `http://127.0.0.1:5000/mcp` as the URL.
191
+
1. In the MCP Inspector, select `Streamable HTTP` as the Transport Type and enter `http://127.0.0.1:8000/mcp` as the URL.
192
192
1. Click **Connect**. This triggers the OAuth flow, and you are redirected to the Auth0 login page.
193
193
1. Log in with the credentials you set up in the Auth0 connection and allow MCP Inspector access.
194
194
1. After you connect, the browser redirects back to MCP Inspector.
@@ -241,7 +241,7 @@ Then, continue with the following steps:
241
241
| "What would you like to configure?" | "Add Extension" |
242
242
| "What type of extension would you like to add?" | "Command Line Extension" |
243
243
| "What's the name of this extension?" | "mcp-auth-quickstart" |
244
-
| "What command should be run?" | `npx mcp-remote http://127.0.0.1:5000/mcp` |
244
+
| "What command should be run?" | `npx mcp-remote http://127.0.0.1:8000/mcp` |
245
245
| Other prompts (timeout, description, environment variables) | Use the default values |
246
246
247
247
1. To start Goose, type `goose`. This will open a browser window and send you through the auth flow.
@@ -255,8 +255,8 @@ Then, continue with the following steps:
255
255
256
256
#### MCP Server Won't Start
257
257
258
-
- **Error**: "Port 5000 is already in use"
259
-
- Solution: Kill any existing processes using port 5000 or specify a different port with the `transport.port` option or `APOLLO_MCP_TRANSPORT__PORT` env variable
258
+
- **Error**: "Port 8000 is already in use"
259
+
- Solution: Kill any existing processes using port 8000 or specify a different port with the `transport.port` option or `APOLLO_MCP_TRANSPORT__PORT` env variable
260
260
- **Error**: "Failed to load supergraph configuration"
261
261
- Solution: Verify you're running the command from the repo root directory
262
262
- Solution: Check that the path to `supergraph.yaml` is correct
@@ -269,7 +269,7 @@ Then, continue with the following steps:
269
269
270
270
- **Error**: "Failed to connect to server"
271
271
- Solution: Ensure the MCP server is running (check terminal output)
272
-
- Solution: Verify you're using the correct URL (`http://127.0.0.1:5000/mcp`)
272
+
- Solution: Verify you're using the correct URL (`http://127.0.0.1:8000/mcp`)
273
273
- Solution: Check if your firewall is blocking the connection
@@ -120,7 +120,7 @@ You can run the MCP Server using the Rover CLI or Docker.
120
120
This command:
121
121
- Starts an MCP Server in a Docker container
122
122
- Maps configuration files into the proper place for the Apollo MCP Server container
123
-
- Forwards port 5000 for accessing the MCP Server
123
+
- Forwards port 8000 for accessing the MCP Server
124
124
125
125
## Step 3: Verify the MCP Server with MCP Inspector
126
126
@@ -134,7 +134,7 @@ You can run the MCP Server using the Rover CLI or Docker.
134
134
135
135
1. In Inspector:
136
136
- Select `Streamable HTTP` as the Transport Type
137
-
- Enter `http://127.0.0.1:5000/mcp` as the URL
137
+
- Enter `http://127.0.0.1:8000/mcp` as the URL
138
138
- Click **Connect**, then **List Tools**
139
139
140
140
You should see the tools from your server listed.
@@ -159,7 +159,7 @@ Then add the following configuration
159
159
"command": "npx",
160
160
"args": [
161
161
"mcp-remote",
162
-
"http://127.0.0.1:5000/mcp"
162
+
"http://127.0.0.1:8000/mcp"
163
163
]
164
164
}
165
165
}
@@ -194,16 +194,16 @@ Let's verify everything is working:
194
194
### Common Issues
195
195
196
196
#### MCP Server Won't Start
197
-
-**Error**: "Port 5000 is already in use"
198
-
- Solution: Kill any existing processes using port 5000 or specify a different port with the `transport.port` option or `APOLLO_MCP_TRANSPORT__PORT` env variable
197
+
-**Error**: "Port 8000 is already in use"
198
+
- Solution: Kill any existing processes using port 8000 or specify a different port with the `transport.port` option or `APOLLO_MCP_TRANSPORT__PORT` env variable
199
199
-**Error**: "Failed to load supergraph configuration"
200
200
- Solution: Verify you're running the command from the repo root directory
201
201
- Solution: Check that the path to `supergraph.yaml` is correct
202
202
203
203
#### MCP Inspector Connection Issues
204
204
-**Error**: "Failed to connect to server"
205
205
- Solution: Ensure the MCP server is running (check terminal output)
206
-
- Solution: Verify you're using the correct URL (`http://127.0.0.1:5000/mcp`)
206
+
- Solution: Verify you're using the correct URL (`http://127.0.0.1:8000/mcp`)
207
207
- Solution: Check if your firewall is blocking the connection
Copy file name to clipboardExpand all lines: docs/source/run.mdx
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -105,7 +105,7 @@ The container sets a few defaults for ease of use:
105
105
106
106
-**Working Directory is `/data`**: Make sure to mount static schemas / operations to this location
107
107
using the volume flag when running [(`-v` / `--volume`)](https://docs.docker.com/reference/cli/docker/container/run/#volume).
108
-
-**HTTP Streamable Transport on port 5000**: Make sure to export container port 5000 for HTTP Streamable connections to
108
+
-**HTTP Streamable Transport on port 8000**: Make sure to export container port 8000 for HTTP Streamable connections to
109
109
the MCP server using the port flag when running [(`-p` / `--port`)](https://docs.docker.com/reference/cli/docker/container/run/#publish)
110
110
111
111
</Note>
@@ -116,7 +116,7 @@ Run the following Docker command to start the MCP Server, replacing the values f
116
116
docker run \
117
117
-it --rm \
118
118
--name apollo-mcp-server \
119
-
-p 5000:5000 \
119
+
-p 8000:8000 \
120
120
-v <PATH/TO/CONFIG/FILE>:/config.yaml \
121
121
-v <PATH/TO/PROJECT/ROOT>:/data \
122
122
--pull always \
@@ -127,7 +127,7 @@ This command:
127
127
128
128
- Starts an MCP Server in a Docker container
129
129
- Maps configuration files into the proper place for the Apollo MCP Server container
130
-
- Forwards port 5000 for accessing the MCP Server
130
+
- Forwards port 8000 for accessing the MCP Server
131
131
132
132
## With the Rover CLI
133
133
@@ -147,12 +147,12 @@ The Apollo Runtime Container runs both the MCP Server and the [Apollo Router](ht
147
147
148
148
The Apollo Runtime container includes all services necessary to serve GraphQL and MCP requests, including the Router and MCP Server. It is the easiest way to operate a GraphQL API with MCP support.
149
149
150
-
To serve both MCP and GraphQL requests, both port `4000` and `5000` will need to be exposed. An example command which retrieves the schema from Uplink is:
150
+
To serve both MCP and GraphQL requests, both port `4000` and `8000` will need to be exposed. An example command which retrieves the schema from Uplink is:
2. Add the MCP SSE port to your MCP Server configuration for the client appliction you are running. If you are running locally, the server link will be `http://127.0.0.1:5000/sse`.
81
+
2. Add the MCP SSE port to your MCP Server configuration for the client appliction you are running. If you are running locally, the server link will be `http://127.0.0.1:8000/sse`.
82
82
83
83
_Note: Claude Desktop currently doesn't support SSE_
84
84
@@ -87,7 +87,7 @@ _Note: Claude Desktop currently doesn't support SSE_
0 commit comments