CTnP MCP Server
Manage Ingeniux CTnP audiences, personalization rules, and A/B tests from an MCP-aware agent during site optimization.
Overview
CTnP MCP Server is a MCP server for the Grow phase that connects agents to Ingeniux CTnP for personalization, A/B testing, and audience management over the CTnP APIs.
What is this MCP server?
- npm @ingeniux/ctnp-mcp v0.7.7 stdio server via npx
- CTnP REST API and CMS URL configuration with bearer token auth
- Personalization, A/B testing, and audience management tool surface
- Optional CMS user and group IDs for permission-aware personalization context
- Enterprise Ingeniux stack integration—not a generic analytics MCP
- Package @ingeniux/ctnp-mcp version 0.7.7
- Stdio transport with runtimeHint npx
- Core env vars: CTNP_API_URL, CTNP_CMS_URL, CTNP_BEARER_TOKEN
What problem does it solve?
Tweaking audiences and experiments in Ingeniux CTnP means constant context switching between the CMS, API docs, and your coding agent.
Who is it for?
Builders on Ingeniux CTnP who want MCP-driven changes to audiences and A/B tests while shipping landing or content updates.
Skip if: Static sites, non-Ingeniux stacks, or teams without CTnP API credentials and CMS access.
What do I get? / Deliverables
With API and CMS URLs plus a bearer token configured, your agent can query and adjust CTnP personalization and test assets from stdio MCP sessions.
- MCP access to CTnP personalization, audiences, and A/B testing operations
- Stdio MCP server config bound to your CTnP environment variables
Recommended MCP Servers
Journey fit
Growing content sites need experimentation and segmentation without logging into the CMS for every audience or test tweak. Lifecycle covers personalization and experimentation workflows that CTnP exposes—audiences, variants, and test configuration.
How it compares
Ingeniux CTnP-specific MCP integration, not a general-purpose A/B testing skill or web analytics connector.
Common Questions / FAQ
Who is CTnP MCP Server for?
Developers and growth-minded solo builders maintaining Ingeniux sites who use CTnP for personalization and experiments and want agent access to those APIs.
When should I use CTnP MCP Server?
Use it when you are adjusting audience segments, personalization rules, or A/B tests and want the agent to read CTnP state or propose API-aligned changes.
How do I add CTnP MCP Server to my agent?
Install or npx @ingeniux/ctnp-mcp, set CTNP_API_URL, CTNP_CMS_URL, and CTNP_BEARER_TOKEN, optionally CTNP_CMS_USER_ID and CTNP_CMS_GROUP_IDS, then register the stdio server in your MCP client.