Skip to main content
Glama
k-edge

mcp-graphql-bridge

by k-edge

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
GRAPHQL_TOKENNoBearer token for GraphQL authentication (used for query/mutation execution). Omit for public APIs.
MCP_AUTH_TOKENNoBearer token required by the hosted /mcp HTTP endpoint when MCP_TRANSPORT=http.
GRAPHQL_API_URLNoEndpoint used for queries and mutations. Defaults to a public demo API (https://countries.trevorblades.com/graphql) if unset — replace with your own for real use.https://countries.trevorblades.com/graphql
GRAPHQL_MAX_TOOLSNoMaximum number of query/mutation tools to register. Queries are prioritized over mutations when truncating. Default 128.128
GRAPHQL_MAX_RETRIESNoRetries (0–5) for 429/502/503/504 responses, honoring Retry-After when present. Default 0 (disabled).0
GRAPHQL_INCLUDE_MUTATIONSNoSet to false to exclude every mutation field entirely, for a read-only deployment. Default true.true
GRAPHQL_INTROSPECTION_URLNoEndpoint used for schema introspection. Defaults to GRAPHQL_API_URL if unset.
GRAPHQL_INTROSPECTION_TOKENNoBearer token for schema introspection, if it requires different credentials than execution (e.g. a separate schema registry). Defaults to GRAPHQL_TOKEN if unset.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
query__continentD

[QUERY] continent

query__continentsC

[QUERY] continents

query__countriesD

[QUERY] countries

query__countryC

[QUERY] country

query__languageD

[QUERY] language

query__languagesC

[QUERY] languages

execute_graphqlA

Execute any GraphQL query or mutation against the API. Use this when no specific tool exists for your operation.

get_type_detailsA

Get fields of a specific GraphQL type to know what to put in __fields

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

C2.8/5.0

Scored across 8 tools

Disambiguation4/5

The query__* tools are clearly separated by resource and singular/plural variant, and get_type_details serves a distinct introspection role. execute_graphql overlaps with the specific query tools by design, but its fallback purpose is clearly stated, so misselection is unlikely.

Naming Consistency4/5

The six query tools follow a consistent query__<resource> pattern, and the singular/plural distinction is predictable. The generic tools get_type_details and execute_graphql use a different verb_noun style, which is a minor deviation but not confusing.

Tool Count5/5

Eight tools is a lean, focused set for a GraphQL bridge: six common resource queries plus two generic utilities for schema inspection and arbitrary operations. Each tool has a clear purpose and the count feels appropriate.

Completeness5/5

The generic execute_graphql tool ensures any query or mutation can be run, covering coverage gaps beyond the named resources. get_type_details supports the workflow of discovering types and fields, so the surface has no obvious dead ends.

Maintenance

ActivityMaintained
ResponsivenessSyncing