Skip to main content

LLM Labs (Upcoming): Analyze and optimize token utilization across models with deep insights and cost visibility. →

BY NIFE · OPEN SOURCE · MIT LICENSE

Talk to any API through Claude.
Zero configuration.

Point it at any GraphQL or REST API — the server auto-introspects the schema and exposes every query, mutation, and endpoint as an MCP tool. Two packages. MIT licensed. Claude Desktop ready.

graphql-mcp-server  ·  nife-restapi-mcp-server

How it works

Three steps to a working MCP server

01

Point at your API

Provide your GraphQL or REST API endpoint URL — local or remote, authenticated or public.

02

Schema auto-discovered

Server auto-discovers every query, mutation, and REST endpoint from the live schema or OpenAPI spec.

03

Ask in plain English

Claude (or any MCP client) instantly talks to your API using natural language — no boilerplate.

Two packages. One pip install.

GraphQL or REST — both ship in seconds.

GRAPHQL

GraphQL MCP Server

Auto-introspects any GraphQL schema via introspection query and generates typed MCP tools for every query and mutation.

bash — install
Copy
pip install graphql-mcp-server
bash — run
Copy
graphql-mcp-server --endpoint https://api.example.com/graphql --token mytoken
Auto-introspects schema
Dual mode: stdio + HTTP
CLI / env / .env / Claude Desktop
Docker, K8s, ECS ready
View on GitHub
REST API

REST API MCP Server

Parses any OpenAPI/Swagger spec and dynamically generates MCP tools for every endpoint — GET, POST, PUT, DELETE.

bash — install
Copy
pip install nife-restapi-mcp-server
bash — run
Copy
restapi-mcp-server --base-url https://api.example.com \
  --spec-url https://api.example.com/openapi.json
OpenAPI 3.x + Swagger 2.0
Bearer, API Key, Basic, None auth
Dual mode: stdio + HTTP
CLI / env / .env / Claude Desktop
View on GitHub

Claude Desktop Integration

Claude talks directly to your API

Both MCP servers support Claude Desktop out of the box. Drop in the config and Claude can immediately query, explore, and act on your API.

claude_desktop_config.json
Copy
{
  "mcpServers": {
    "graphql": {
      "command": "graphql-mcp-server",
      "env": {
        "GRAPHQL_ENDPOINT": "https://api.example.com/graphql",
        "API_ACCESS_TOKEN": "your_token_here",
        "MCP_MODE": "stdio",
        "ENABLE_HTTP_ENDPOINT": "false"
      }
    }
  }
}

Claude Desktop injects env block values directly into the process — standard MCP pattern.

AI ASSISTANTClaude
MCP Active

List all available queries from my GraphQL API

TOOL: list_available_queries
→ Found 12 queries: getUser, listApplications, getDeployments, listRegions, getOrganization, listSites, getDatabaseDeployments, getMetrics, listTeamMembers, getAuditLog, getSecrets, listWebhooks
Claude

I found 12 available queries in your GraphQL API. Here they are:

• getUser, listApplications, getDeployments

• listRegions, getOrganization, listSites

• getDatabaseDeployments, getMetrics, listTeamMembers

• getAuditLog, getSecrets, listWebhooks

Want me to run any of these?

Run getDeployments for org-id abc123

TOOL: getDeployments
→ { "deployments": [{ "id": "dep-001", "name": "api-server", "status": "running", "region": "us-east-1" }, { "id": "dep-002", "name": "worker", "status": "running", "region": "eu-west-1" }] }
Claude

Here are the deployments for org abc123:

Name
Status
Region
api-server
🟢 running
us-east-1
worker
🟢 running
eu-west-1

Both deployments are healthy.

Ask Claude about your API…

Documentation & Setup

Up and running in under 2 minutes

Install & Run

bash — pip install
Copy
pip install graphql-mcp-server
bash — CLI run
Copy
graphql-mcp-server --endpoint https://api.example.com/graphql --token mytoken

Docker

bash — docker run
Copy
docker run -p 8080:8080 \
  -e GRAPHQL_ENDPOINT=https://api.example.com/graphql \
  -e API_ACCESS_TOKEN=your_token \
  -e MCP_MODE=http \
  graphql-mcp-server

Configuration Methods

1
1. CLI Args
One-off runs, testing
2
2. Env Vars
Docker, CI/CD, shell scripts
3
3. .env File
Local development
4
4. Claude Desktop
Standard MCP pattern

Core capabilities

Built for production from day one

Zero Config

Auto-introspects any GraphQL schema or OpenAPI spec. No manual tool definitions, no boilerplate.

Dual Mode

stdio for Claude Desktop & MCP clients, HTTP mode for Docker and Kubernetes deployments.

Claude Native

First-class Claude Desktop support via the standard env block config — drop in and go.

Multi-Auth

Bearer token, API key, Basic auth, or no auth — all authentication methods supported out of the box.

Production Ready

Docker, Kubernetes, AWS ECS, and Google Cloud Run compatible. Battle-tested for real workloads.

Self-Documenting

Built-in tools: list_available_queries, get_schema_info, list_available_endpoints, and more.

Nife MCP Server

The Nife MCP Server connects Claude to your entire Nife infrastructure.

Deploy, scale, and manage apps through any LLM — pre-wired to your Nife account, zero configuration.

See Nife MCP Server →

This website uses cookies to improve your experience. By clicking "I Agree," you consent to our use of cookies.