Claude GraphOS Tools connectorWhat Claude can do with GraphOS Tools.
The Claude GraphOS Tools connector exposes 3 tools. 3 read Apollo's public documentation, 0 change anything, 0 are undocumented. Here: what Claude can look up, why no sign-in is needed, and what the directory sheet has not caught up with.
Verified Trustpilot reviews · AI, automation & growth agency
What the Claude GraphOS Tools connector changes when you build with Apollo
When you work on a GraphQL API with Apollo, the answer to a configuration question usually sits somewhere in Apollo's documentation. With this connector, Claude looks it up itself: it searches the official docs, opens the full page it needs and, for Apollo Connectors, reads the specification before it suggests anything. You get an answer grounded in Apollo's own text rather than in a half-remembered blog post.
A precise answer on router configuration. You want the option that controls health checks in the Apollo Router. ApolloDocsSearch finds the relevant guides, then ApolloDocsRead opens the full reference page so Claude can quote the exact property instead of guessing.
A REST API wrapped in GraphQL. You plan to expose an existing REST endpoint through your graph. ApolloConnectorsSpec gives Claude the official Apollo Connectors specification, the material it needs to draft the connector you will add to your schema.
Best practices before a schema review. Claude can pull Apollo's guidance on schema design or deployment and summarize it for a teammate who is new to federation.
What it does not do: as listed in the directory, the three tools read public documentation only. They do not reach your graphs, your schema history or your metrics, and none of them changes anything in a GraphOS account. Apollo's own docs describe additional tools that read an organization's graphs after sign-in, but the Claude sheet does not list them. Nothing runs by itself either: these tools only work while Claude answers you. For scheduled or event-driven jobs you would reach for an automation tool, a different line of work collected on the Integrations hub.
The vocabulary in one minute
Five terms you will see while adding GraphOS Tools.
- Connector
- The link you set up once between Claude and an outside service, so Claude can use it while it answers you.
- Tool
- One named action a connector gives Claude. Claude chooses which to call on its own; the directory lists each by its name.
- Authorization
- The service's own sign-in screen, where you grant the access Claude will use. Given once per person, and it can be withdrawn.
- Approval
- The confirmation Claude waits for before it goes through with something that changes an account, shown in the chat at that moment.
- MCP
- The shared standard connectors rely on: it is what lets an assistant like Claude exchange with an outside service such as Apollo's.
Add GraphOS Tools to Claude in three steps
- 01
Find the connector
Open Claude's settings, go to Customize and then Connectors, and look for GraphOS Tools in the list. On a Team or Enterprise workspace, an Owner or Primary Owner must enable it for the organization before members can connect.
- 02
Connect it
Click Connect on its row. The three documentation tools read public content, so Apollo says they need no credentials. If the connection ever misbehaves, Disconnect it and connect again.
- 03
Check what you grant
If a sign-in or authorization screen appears, read it before you accept. It belongs to the service, not to Claude, and it sets how far the access goes. You can withdraw that access later from the service side too.
The 3 tools, sorted by what they do
GraphOS MCP Tools gives Claude 3 tools: 3 that read your account, 0 that change something in it.
All three read Apollo's public material. Their names stay exactly as Claude displays them.
- 3 read
What Claude reads (3)
3 toolsThree tools that consult Apollo's documentation and specification without touching any account.
ApolloDocsSearch
Queries the whole of Apollo's official documentation and brings back the guides, examples and best practices that match, whether the topic is GraphQL, GraphOS, schema design or deployment. Claude uses the hits to pick which page deserves a closer look.
ApolloDocsRead
Fetches the complete Markdown text of a given Apollo documentation page, so Claude can work from the full reference rather than from a snippet in search results.
ApolloConnectorsSpec
Hands Claude the official Apollo Connectors specification, the reference that defines how connectors are built inside a schema. Claude reads it and drafts from it; nothing lands in your project unless you put it there.
What Claude asks before it acts
By default, Claude stops and asks for your go-ahead before any action it would carry out on an account for you. Apollo adds, in its own setup guide, that Claude asks your permission before running these tools.
On Team and Enterprise, workspace owners decide whether members can let some actions pass without a fresh confirmation each time, and they can restrict what a connector may do across the organization; nobody overrides that from a personal account. Claude also works with the rights of the person connected and nothing more. Here the listed tools read Apollo's public documentation, not your organization's data, so there is no private account content for them to reach.
Which plans it is available on
None of the 819 sheets in the official directory shows plan availability. Connector by connector, that answer is published nowhere: a real gap in the catalogue.
The general rule is published: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner enables a connector for the organization before members connect. For the current status of this one, the GraphOS Tools sheet in the official directory is the place to check.
Where the Claude GraphOS Tools connector stops
A connector is not an automation. Claude calls these tools while it answers you; nothing starts on its own when Apollo publishes a new page.
Only Apollo documents this connector; Claude's help center has no article on it. A sheet that shows nothing but reading is an observed floor, not a promise, since an administrator can open actions that no public sheet lists. The partner badge is not a security audit, and Anthropic says on every sheet that it neither chooses the tools a publisher exposes nor guarantees how they behave. Connect it only if you trust the publisher, here Apollo.
Need help connecting GraphOS MCP Tools to Claude?
A person reads every message.
