Model Context Protocol (MCP) Server for GraphQL Policies API

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is Model Context Protocol (MCP) Server for GraphQL Policies API?

This project provides an implementation of a Model Context Protocol (MCP) server, designed to facilitate a GraphQL API that grants access to various policies.

how to use the MCP Server?

To use the MCP server, clone the repository from GitHub, install the required dependencies, set up your environment variables, and configure it with your GraphQL API details.

key features of the MCP Server?

  • Implementation of Model Context Protocol for easy interaction with policies.
  • Utilizes the Python SDK and GQL library for GraphQL operations.
  • Customizable configurations through environment variables.

use cases of the MCP Server?

  1. Integrating GraphQL policies within existing applications.
  2. Simplifying access to policy management via the MCP architecture.
  3. Enhancing communication between different components of software ecosystems.

FAQ from the MCP Server?

  • What is the purpose of the MCP?

The MCP allows for structured access to policies, ensuring they can be managed and queried efficiently.

  • Is there a specific platform to run the MCP Server?

The server is designed to work on various platforms, provided the necessary prerequisites are met.

  • Can I customize the server settings?

Yes, you can define server configurations through environment variables as per your application needs.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
-
Language
-
License
-

Recommend Servers

View All
Crevio

a day ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

19 hours ago