# Using apollo-mcp-server without GraphOS / Apollo account

**URL:** <https://community.apollographql.com/t/using-apollo-mcp-server-without-graphos-apollo-account/9330>\
**Category:** MCP Server\
**Created:** [August 2, 2025, 5:01pm UTC](https://community.apollographql.com/t/using-apollo-mcp-server-without-graphos-apollo-account/9330 "2025-08-02T17:01:46Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![chriss](https://sea1.discourse-cdn.com/flex019/user_avatar/community.apollographql.com/chriss/32/6293_2.png) [@chriss](https://community.apollographql.com/u/chriss)\
**Post date:** [August 2, 2025, 5:01pm UTC](https://community.apollographql.com/t/using-apollo-mcp-server-without-graphos-apollo-account/9330/1 "2025-08-02T17:01:46Z")

</div>

Hi! In your docs it says that one can use the apollo-mcp-server with any API server, however when attempting to boot it without the graphos config it says:  
```  
`Error: Missing environment variable: APOLLO_GRAPH_REF`  
```

Adding empty strings as those values in the config yields:

`uplink error, the request will not be retried: code=AUTHENTICATION_FAILED message= did not parse to a valid key format`

Thoughts?

---

<div class="post-metadata">

**Author:** ![DaleSeo](https://sea1.discourse-cdn.com/flex019/user_avatar/community.apollographql.com/daleseo/32/5385_2.png) [@DaleSeo](https://community.apollographql.com/u/DaleSeo)\
**Post date:** [August 4, 2025, 5:31pm UTC](https://community.apollographql.com/t/using-apollo-mcp-server-without-graphos-apollo-account/9330/2 "2025-08-04T17:31:22Z")

</div>

@chriss It should work with any GraphQL APIs. Could you let me know which version of apollo-mcp-server you’re using? Also, please share your config file, run the server with debug logging enabled, and provide the terminal output.

---

<div class="post-metadata">

**Author:** ![chriss](https://sea1.discourse-cdn.com/flex019/user_avatar/community.apollographql.com/chriss/32/6293_2.png) [@chriss](https://community.apollographql.com/u/chriss)\
**Post date:** [August 4, 2025, 7:18pm UTC](https://community.apollographql.com/t/using-apollo-mcp-server-without-graphos-apollo-account/9330/3 "2025-08-04T19:18:11Z")

</div>

Hi Dale! Returning to this, I was able to figure it out!

Would be great if the ‘quickstart’ doc didn’t link to the tutorial with all of its steps and complexity, but rather something more bare bones, with a full config easily readable.

For example, a config something like the below would be enough for most devs to get started within a locally-running GraphQL server:

```  
endpoint: [http://localhost:5001](http://localhost:5001)  
transport:  
type: streamable\_http  
operations:  
source: local  
paths:  
- ./mcp/operations  
schema:  
source: local  
path: ./schema.graphql  
introspection:  
execute:  
enabled: true  
introspect:  
enabled: true  
search:  
enabled: true

Then then docs would be a little less confusing.

Thank you though for this great tool!

---

<div class="post-metadata">

**Author:** ![chriss](https://sea1.discourse-cdn.com/flex019/user_avatar/community.apollographql.com/chriss/32/6293_2.png) [@chriss](https://community.apollographql.com/u/chriss)\
**Post date:** [August 4, 2025, 8:45pm UTC](https://community.apollographql.com/t/using-apollo-mcp-server-without-graphos-apollo-account/9330/4 "2025-08-04T20:45:27Z")

</div>

Ok y’all, this tool is very, very powerful! Up and running in our schema and am amazed. So much potential here. Great work (ty).

---

<div class="post-metadata">

**Author:** ![DaleSeo](https://sea1.discourse-cdn.com/flex019/user_avatar/community.apollographql.com/daleseo/32/5385_2.png) [@DaleSeo](https://community.apollographql.com/u/DaleSeo)\
**Post date:** [August 5, 2025, 3:57am UTC](https://community.apollographql.com/t/using-apollo-mcp-server-without-graphos-apollo-account/9330/5 "2025-08-05T03:57:52Z")

</div>

Really glad to hear you got it working @chriss! Appreciate the feedback. I’ll pass it along to the team so we can make the quickstart experience clearer.

---

<div class="post-metadata">

**Author:** ![bwkiwi](https://sea1.discourse-cdn.com/flex019/user_avatar/community.apollographql.com/bwkiwi/32/4921_2.png) [@bwkiwi](https://community.apollographql.com/u/bwkiwi)\
**Post date:** [August 6, 2025, 4:09pm UTC](https://community.apollographql.com/t/using-apollo-mcp-server-without-graphos-apollo-account/9330/6 "2025-08-06T16:09:22Z")

</div>

Hi chriss - could you share how you resolved this issue?  
Using 0.6.1 I get the error “Missing environment variable: APOLLO\_GRAPH\_REF” using a basic config setup.  
If I set these env vars to dummy values, it will fail the validation: “ERROR uplink error, the request will not be retried: code=UNKNOWN\_REF message=No valid graph configuration for …”

The new features in 0.6 look interesting, but without using federation this seems to be broken.

Thanks,  
Brian

---

<div class="post-metadata">

**Author:** ![chriss](https://sea1.discourse-cdn.com/flex019/user_avatar/community.apollographql.com/chriss/32/6293_2.png) [@chriss](https://community.apollographql.com/u/chriss)\
**Post date:** [August 6, 2025, 5:08pm UTC](https://community.apollographql.com/t/using-apollo-mcp-server-without-graphos-apollo-account/9330/7 "2025-08-06T17:08:31Z")

</div>

Sure thing! A config as simple as this will do it, assuming you’ve booted your graphql server on port 5001, and started the MCP server. Note the bit about `schema: source: local`, which then points at the concrete artifact of your schema; once this is set the error will go away. We’ve also tested this on remotely deployed graphql servers and likewise, works great.

endpoint: [http://localhost:5001](http://localhost:5001)  
transport:  
type: streamable\_http  
operations:  
source: local  
paths:  
./mcp/operations/analytics  
schema:  
source: local  
path: ./schema.graphql  
overrides:  
mutation\_mode: “all” # enable mutations?  
introspection:  
execute:  
enabled: true  
introspect:  
enabled: true  
search:  
enabled: true  
headers:  
“x-access-token”: “fill-in”  
“x-user-id”: “fill-in”

(Code formatting doesn’t work so good on this forum, apologies)

---

<div class="post-metadata">

**Author:** ![DaleSeo](https://sea1.discourse-cdn.com/flex019/user_avatar/community.apollographql.com/daleseo/32/5385_2.png) [@DaleSeo](https://community.apollographql.com/u/DaleSeo)\
**Post date:** [August 7, 2025, 3:35am UTC](https://community.apollographql.com/t/using-apollo-mcp-server-without-graphos-apollo-account/9330/8 "2025-08-07T03:35:08Z")

</div>

Hi @bwkiwi , as @chriss mentioned, Apollo MCP Server tries to fetch the schema from Uplink by default, which requires an Apollo key and a graph reference. This default behavior is documented here:

> **[Command Reference](https://www.apollographql.com/docs/apollo-mcp-server/command-reference#schema-source-configuration)**
>
> Reference guide of options for running Apollo MCP Server.

You can configure the MCP server to use your local schema file as follows:

```yaml
schema:
  source: local
  path: /schema.graphql

```

Once you make this change, you should be able to start the server without needing Apollo-specific environment variables.

---

<div class="post-metadata">

**Author:** ![Carlos\_Andres](https://sea1.discourse-cdn.com/flex019/user_avatar/community.apollographql.com/carlos_andres/32/6372_2.png) [@Carlos\_Andres](https://community.apollographql.com/u/Carlos_Andres)\
**Post date:** [September 27, 2025, 5:24am UTC](https://community.apollographql.com/t/using-apollo-mcp-server-without-graphos-apollo-account/9330/10 "2025-09-27T05:24:31Z")

</div>

Hi Chriss, no matter what I do I keep getting this same error. could you please tell me how did you run the mcp server, via rover or docker?

---

<div class="post-metadata">

**Author:** ![chriss](https://sea1.discourse-cdn.com/flex019/user_avatar/community.apollographql.com/chriss/32/6293_2.png) [@chriss](https://community.apollographql.com/u/chriss)\
**Post date:** [October 2, 2025, 5:21pm UTC](https://community.apollographql.com/t/using-apollo-mcp-server-without-graphos-apollo-account/9330/11 "2025-10-02T17:21:10Z")

</div>

hi @Carlos_Andres - we run it via the docker container! We don’t have an apollo account and everything works great.
