CTnP MCP Server
LocalAbout CTnP MCP Server
Ingeniux CTnP MCP server for personalization, A/B testing, and audience management.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
npx -y @ingeniux/ctnp-mcpCTNP_API_URLBase URL of the CTnP REST API (e.g. https://yoursite.com/api)CTNP_CMS_URLBase URL of the CTnP CMS (e.g. https://yoursite.com)CTNP_BEARER_TOKENSecretBearer token for CTnP API authenticationCTNP_CMS_USER_IDCMS user ID (optional, for personalization context)CTNP_CMS_USER_NAMECMS user display name (optional)CTNP_CMS_GROUP_IDSComma-separated CMS group IDs for permission context (default: UserGroup/1)CTNP_CONNECTION_IDCTnP connection ID for multi-tenant setups (optional)CTNP_TIMEOUT_MSRequest timeout in milliseconds (default: 30000)Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
The maintainer has not added details yet. Check the README in the repository.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.