Skip to content

Change default port from 5000 to 8000 #417

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.

Sign up for GitHub

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

Merged
merged 6 commits into from
Oct 9, 2025
Merged

Change default port from 5000 to 8000 #417

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
1899899
feat: change default port from 5000 to 8000
DaleSeo Oct 3, 2025
47c1367
docs: change default port from 5000 to 8000
DaleSeo Oct 3, 2025
4bd07ba
chore: add changelog
DaleSeo Oct 3, 2025
373b34d
docs: change default port from 5000 to 8000
DaleSeo Oct 3, 2025
93e607b
chore: update space devs readme
DaleSeo Oct 9, 2025
bf4cba2
docs: add container path
DaleSeo Oct 9, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
0 .changesets/defalut_port_8000.md → .changesets/breaking_defalut_port_8000.md
View file
Open in desktop
File renamed without changes.
109 changes: 16 additions & 93 deletions graphql/TheSpaceDevs/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -38,28 +38,22 @@ Here is an example configuration you can use _(Note: you must provide your fill
"thespacedevs": {
"command": "/Users/michaelwatson/Documents/GitHub/apollographql/apollo-mcp-server/target/debug/apollo-mcp-server",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I also didn't realize this path was hardcoded to /Users/michaelwatson

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It really shows how long ago this README.md was written. We should probably delete it and just use the official docs instead.

"args": [
"--directory",
"/Users/michaelwatson/Documents/GitHub/apollographql/apollo-mcp-server/graphql/TheSpaceDevs",
"--schema",
"api.graphql",
"--operations",
"operations",
"--endpoint",
"https://thespacedevs-production.up.railway.app/",
"--introspection"
"graphql/TheSpaceDevs/config.yaml"
]
}
}
}
```

## Using Server-Side-Events (SSE) with Apollo MCP server
## Using Streamable HTTP with Apollo MCP server

There are operations located at `./operations/*.graphql` for you to use in your configuration. You can provide a set of operations in your MCP configuration along with the `--introspection` option that enables the LLM to generate a dynamic operation along with the ability to execute it.
There are operations located at `./operations/*.graphql` for you to use in your configuration. You can provide a set of operations in your MCP configuration that enables the LLM to generate a dynamic operation along with the ability to execute it.

### Running SSE with `rover dev`
### Running with `rover dev`

**_Coming soon_**
```BASH
rover dev --supergraph-config supergraph.yaml --mcp config.yaml
```

### Running Apollo MCP server Docker image

Expand All @@ -70,24 +64,24 @@ docker run \
-it --rm \
--name apollo-mcp-server \
-p 8000:8000 \
-v $PWD/graphql/TheSpaceDevs/config.yaml \
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
-v $PWD/graphql/TheSpaceDevs/config.yaml \
-v $PWD/graphql/TheSpaceDevs/config.yaml:/config.yaml \

I forget, does this need the path on the other side to tell docker where to mount the file?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You're right and I copied that from our deploy docs! 😂 Will fix it in both places.

apollo-mcp-server/docs/source/deploy.mdx

Line 75 in 93e607b

-v <path/to>/mcp_config.yaml \

-v $PWD/graphql/TheSpaceDevs:/data \
ghcr.io/apollographql/apollo-mcp-server:latest \
--http-port 8000 \
--schema api.graphql \
--operations operations \
--endpoint https://thespacedevs-production.up.railway.app/
ghcr.io/apollographql/apollo-mcp-server:latest /config.yaml
```

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`.
2. Add the MCP port to your MCP Server configuration for the client application you are running. If you are running locally, the server link will be `http://127.0.0.1:8000/mcp`.

_Note: Claude Desktop currently doesn't support SSE_

```
{
"mcpServers": {
"thespacedevs": {
"type": "sse",
"url": "http://127.0.0.1:8000/sse>"
"command": "npx",
"args": [
"mcp-remote",
"http://127.0.0.1:8000/mcp"
]
}
}
}
Expand All @@ -103,80 +97,9 @@ Here is an example configuration you can use _(Note: you must provide your fill
"thespacedevs": {
"command": "/Users/michaelwatson/Documents/GitHub/apollographql/apollo-mcp-server/target/debug/apollo-mcp-server",
"args": [
"--directory",
"/Users/michaelwatson/Documents/GitHub/apollographql/apollo-mcp-server/graphql/TheSpaceDevs",
"--schema",
"api.graphql",
"--operations",
"operations",
"--endpoint",
"https://thespacedevs-production.up.railway.app/",
"--introspection"
"graphql/TheSpaceDevs/config.yaml"
]
}
}
}
```

## Using Persisted Queries - GraphOS Scale and Enterprise tiers only

You can configure the Apollo MCP server to use [Persisted Queries with GraphOS](https://www.apollographql.com/docs/graphos/routing/security/persisted-queries). In order to do this, you'll have to setup GraphOS and run a router instance configured to that persisted query list:

1. Create a new graph in [GraphOS](https://studio.apollographql.com/org)
2. Publish the `api.schema` to the graph you created, _you should see a modal pop up with the command information you need - make sure to save the API key as you'll use it again_

```
APOLLO_KEY=service:my-new-graph:V9_dIUACHIQh5VnhW21SXg \
rover subgraph publish my-new-graph@current \
--schema ./api.graphql \
--name thespacedevs \
--routing-url https://thespacedevs-production.up.railway.app/
```

3. Create a new [Persisted Queries List (PQL)](https://www.apollographql.com/docs/graphos/platform/security/persisted-queries#1-pql-creation-and-linking) for the newly created graph in GraphOS. Make sure to link it to your current variant.
4. Publish operations to PQL in GraphOS

```
rover persisted-queries publish \
--graph-id my-new-graph \
--list-id "PQL-ID" \
--manifest ./persisted_queries/apollo.json
```

_Note: If you added new operations to the operations folder, you'll need to re-generate the persisted queries manifest. There is a VS Code Task you can use in the command palette "Tasks: Run Task" that runs the following command:_

```
npx @apollo/generate-persisted-query-manifest \
generate-persisted-query-manifest \
--config persisted_queries.config.json
```

5. In the command invoking or starting up your Apollo MCP Server with SSE, you'll need to export your `APOLLO_KEY` from the second step along with `APOLLO_GRAPH_REF=my-new-graph@current`.

```bash
export APOLLO_KEY=service:my-new-graph:V9_dIUACHIQh5VnhW21SXg
export APOLLO_GRAPH_REF=my-new-graph@current
```

6. Modify your Apollo MCP Server configuration to use the manifest option instead of operations.

```json
{
"mcpServers": {
"thespacedevs": {
"command": "/Users/michaelwatson/Documents/GitHub/apollographql/apollo-mcp-server/target/debug/apollo-mcp-server",
"args": [
"--directory",
"/Users/michaelwatson/Documents/GitHub/apollographql/mcp-apollo/graphql/TheSpaceDevs",
"--schema",
"api.graphql",
"--manifest",
"persisted_queries/apollo.json",
"--endpoint",
"https://thespacedevs-production.up.railway.app/",
"--introspection"
]
}
}
}
```
Loading