Reference Context
SolutionsProductDevelopersGet StartedPricing
Sign inStart free trial

Applications built on Reference Context

Use a single Reference Context MCP server URL to power every user-facing experience. Fetch contextual data at request time and tune the interface, pricing, and messaging for each audience automatically.
Connect your dataExplore Reference Context

The technical approach

Every application you build consumes the same trusted MCP server URL. Your frontend or backend clients call the Reference Context endpoints to pull the latest entities, features, and pricing metadata, then render experiences that stay perfectly in sync with the source of truth.Because the context is normalized and permissioned, you can extend it into AI agents, dashboards, or mobile surfaces without duplicating business logic. The result: one canonical context powering every workflow.

How it comes together

  1. Register the Reference Context MCP server URL inside your application configuration or agent runtime.
  2. Fetch the structured context payload (entities, feature flags, pricing, policies) on each request or session.
  3. Use that data to personalize UI copy, unlock capabilities, and feed AI assistants with the exact context you just retrieved.
You stay in control of what the app can see, and any update to the context instantly flows to every consumer.

Example applications to ship next

Teams are already layering Reference Context into revenue, product, and support experiences. Start with these patterns and evolve them with your own domain data.

Personalized landing pages

Serve visitors tailored hero copy, feature highlights, and pricing pulled from your Reference Context for their account segment.

Adaptive onboarding

Change setup flows on the fly based on the integrations, compliance policies, or assets stored in the MCP data for each customer.

Revenue intelligence copilots

Let reps ask natural-language questions while the app cross-references deals, playbooks, and enablement content housed in Reference Context.

Dynamic support consoles

Bring together docs, runbooks, and environment details from the MCP server so agents always respond with current, contextual answers.