Skip to content

Commit 9282902

Browse files
committed
extract out troubleshooting steps
1 parent 9d20265 commit 9282902

File tree

1 file changed

+2
-11
lines changed

1 file changed

+2
-11
lines changed

docs/source/quickstart.mdx

Lines changed: 2 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -248,32 +248,23 @@ See [Define MCP Tools](/apollo-mcp-server/define-tools) for other ways to define
248248

249249
## Troubleshooting
250250

251-
<details>
252-
<summary>Common Issues</summary>
253-
254251
**Client doesn't see tools:**
255252
- Ensure you restarted your MCP client after configuration
256253
- Verify the Apollo MCP Server is running (`rover dev` command)
257254
- Check port numbers match between server and client config
258255

259256
**Connection refused errors:**
260-
- Confirm the server is running on the correct port (default: 5050)
257+
- Confirm the server is running on the correct port
261258
- Verify firewall settings allow connections to localhost:5050
262259
- For remote connections, ensure the host is set to `0.0.0.0` in your config
263260

264-
**GraphQL operation errors:**
265-
- Verify your operations files exist in the specified paths
266-
- Check that operation names match your GraphQL schema
267-
- Ensure your GraphQL endpoint is accessible
268261

269262
**Authentication issues:**
270263
- Verify environment variables are properly set
271264
- Check that your GraphQL endpoint accepts the provided headers
272-
- When using `rover dev` you can test your GraphQL endpoint using GraphOS Sandbox at [http://localhost:4000](http://localhost:4000)
273-
</details>
265+
- When using `rover dev` you can test your GraphQL endpoint using Sandbox at [http://localhost:4000](http://localhost:4000)
274266

275267
## Step 4: Working with MCP Tools
276-
277268
Now that your MCP server is connected, learn how to customize and create tools.
278269

279270
### Understanding Tools

0 commit comments

Comments
 (0)