For the complete documentation index, see llms.txt.
Skip to main content

Configuration Plan & Exposition

Before being turned into an MCP Server endpoint, a reShapr Service must have a Configuration Plan defined. A Configuration Plan will allow you to define how your Service will be consumed by MCP Clients. You’ll define the backend endpoint the reShapr proxy will target as well as the security options you want to apply to future expositions.

In a nutshell, a Configuration Plan will allow you to define:

  • The backend endpoint URL of the existing service or API implementation you’re targeting,
  • The list of the Service operations you’d like to expose - you can choose, for example, to restrict access to read-only operations only, or to hide non-relevant operations,
  • The attached Prompts, Resources, Custom Tools, and output filters to include. When no artifact is selected, all artifacts attached to the Service are included,
  • The client cache policy for MCP 2026-07-28, when clients support the corresponding modern response dialect,
  • Whether the proxy emits audit events for calls made through the Plan,
  • The security options you’d like to enable for securing the access of the MCP endpoints - you can choose to secure access with an API key or using an OAuth Authorization Server,
  • The OAuth scopes required to access an Exposition. These scopes protect the Exposition as a whole; reShapr does not apply different OAuth scopes or claims to individual tools, Resources, or Prompts,
  • The accepted OAuth token audiences. By default, the requested Exposition URL is required; static audiences can be added, or validation can be disabled explicitly for compatibility,
  • The request headers forwarded to HTTP backends or converted to gRPC call metadata, using allow, deny, and rename rules. Hop-by-hop, reShapr authentication, and MCP transport headers are always removed,
  • The credentials Secret the MCP Server will present to authorize access to the backend endpoint.

The headerPolicy.response shape is present in the API and Kubernetes CRD but is reserved in 1.0.0; only request headers are filtered or renamed. An absent request policy passes ordinary headers while removing Authorization and Cookie by default. Use explicit rules when a backend requires either header, and treat forwarding Authorization as a deliberate trust-boundary decision.

A reShapr Service can have multiple Configuration Plans that match different environments or lifecycle stages. A Configuration Plan is always associated with a specific version of a Service and has to be replicated for other versions.

Creating a Configuration Plan is not enough for your MCP Server to be ready and usable by your MCP Client. To do so, you must expose - ie create an Exposition - of your Configuration Plan. This last step before consuming a reShapr MCP Server endpoint is a simple declaration that allows you to target a Gateway Group.

Creating an exposition is a simple operation that associates a Configuration Plan to a Gateway Group. Running proxies register logical Gateways, whose labels determine which groups and Expositions they match. See Gateway Groups, Gateways, and Proxies for that distinction.

Use Attach and Select reShapr Artifacts to create two Plans for one Service and verify how includedArtifacts changes their MCP capability surfaces.

Agent View