MCP MCP Server

MCP MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. A lightweight, configuration-driven MCP server that exposes curated GraphQL queries as modular tools, enabling intentional API interactions from your agents.

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

What the assistant can call

Once MCP is connected, these are the calls the assistant has available:

• FORGE_CONFIG — Specifies the path to the folder containing the YAML configuration files (forge.yaml and tool definitions). Used if --forgeConfig is not set
• FORGE_DEBUG — If set to true (case-insensitive), enables detailed debug logging to stderr, including the obtained token and the full HTTP request/response for
• name — The name of the MCP server
• url — The URL of the GraphQL endpoint
• token_command — The command to use to request the Bearer token for the Authorization header (optional)
• env — A map of environment variables to pass to the token command (optional)
• env_passthrough — If set to true, passes all environment variables used when invoking mcp-graphql-forge to the token command; if used in conjunction with env, the
• description — The description of the MCP tool
• query — The GraphQL query to execute
• inputs — The list of inputs defined by the MCP tool and passed into the GraphQL query as variables
• type — The parameter type; can be 'string' or 'number'
• required — Boolean value specifying if the attribute is required

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch MCP.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the mcp mcp server does with a few real requests.

Choosing this one

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. MCP's toolset — FORGE_CONFIG, FORGE_DEBUG, name and 11 more — is a fair guide to whether it matches your workflow. It is maintained by UnitVectorY-Labs; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.