Guard Core MCP

What the guard-core-mcp MCP server does

guard-core-mcp MCP server connects MCP clients with the Guard ecosystem's configuration, documentation, security-pattern, and integration information. It is intended for agents and developers working with Guard Core, its framework adapters, and its telemetry agents.

The server covers the ecosystem around Guard Core rather than a single application framework. The documented registry includes engines and adapters for Python, Go, PHP, TypeScript/JavaScript, and Rust, along with telemetry agents and the related conformance and SaaS contract information.

How it works

An MCP client calls focused tools and receives answers about Guard libraries, settings, documentation, payload evaluation, or integration setup. Configuration validation is designed to catch misspelled keys that a Pydantic-based configuration model might otherwise ignore. Documentation access is split between locating relevant pages and retrieving the complete content of a selected page.

Payload checks answer whether a request would be blocked and identify the matching pattern when one applies. Setup-oriented tools provide instructions for a selected adapter or language, including a minimal verified adapter integration or the ingestion contract used by a telemetry agent.

Tools and capabilities

The available tools include:

• versions: Lists installed Guard libraries and their versions in the current environment.
• validate_config: Checks a Guard configuration and highlights invalid or misspelled settings.
• config_fields: Explains a setting, its default, and whether a requested setting exists.
• search_docs: Locates documentation relevant to a query.
• get_doc: Returns the full text of one documentation page.
• check_payload: Tests a request against Guard blocking patterns and reports the matching pattern.
• ecosystem: Returns the registry matrix covering languages, engines, adapters, agents, conformance, and the SaaS contract.
• adapter_setup: Gives installation and minimal integration guidance for one adapter, such as Go with Gin.
• wire_agent: Explains telemetry-agent setup for a language and describes the ingestion contract.

The guard-core-mcp MCP server is therefore useful for both exploratory questions, such as finding the right adapter, and concrete checks, such as validating configuration or testing a payload.

The ecosystem data identifies Guard Core as the Python engine and describes parallel engine implementations for Go, PHP, TypeScript, and Rust. It also lists framework-specific adapters such as FastAPI, Flask, Django, Tornado, Gin, Echo, Fiber, Laravel, Symfony, Express, NestJS, Fastify, and Hono.

Limitations and notes

The provided material describes the exposed tools and Guard ecosystem, but does not specify installation commands, transport details, required environment variables, or client-specific configuration. It also does not establish that payload checks replace runtime enforcement; the documented capability is an evaluation of whether a request would be blocked and which pattern would match.

The setup tools are scoped to the integrations represented in the Guard registry. Their output may differ by language or adapter because the ecosystem uses separate engine, framework-wrapper, and telemetry-agent packages. The guard-core-mcp MCP server should be evaluated alongside the relevant Guard package when planning a production integration.