# Has Apollo Server MCP Limited GraphQL's Core Query Capabilities?

**URL:** <https://community.apollographql.com/t/has-apollo-server-mcp-limited-graphqls-core-query-capabilities/9201>\
**Category:** MCP Server\
**Tags:** mcp\
**Created:** [June 14, 2025, 3:01am UTC](https://community.apollographql.com/t/has-apollo-server-mcp-limited-graphqls-core-query-capabilities/9201 "2025-06-14T03:01:22Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![esrever10](https://sea1.discourse-cdn.com/flex019/user_avatar/community.apollographql.com/esrever10/32/5709_2.png) [@esrever10](https://community.apollographql.com/u/esrever10)\
**Post date:** [June 14, 2025, 3:01am UTC](https://community.apollographql.com/t/has-apollo-server-mcp-limited-graphqls-core-query-capabilities/9201/1 "2025-06-14T03:01:22Z")

</div>

I’ve noticed that when using **Apollo Server MCP** , the parameters passed to the **MCP tool** don’t seem to follow the **GraphQL query format**. How can I specify which fields the tool should return?

If one cannot use the query syntax of GraphQL, such as specifying the fields to be returned, then wouldn’t it be as if the use of GraphQL has lost its significance? After using Apollo Server MCP, the original capabilities of GraphQL have been lost.