CTnP MCP Server

io.github.jitsmasterPublished by GitHub account jitsmasterv0.7.7Updated Oct 24, 2026

Ingeniux CTnP MCP server for personalization, A/B testing, and audience management.

VerifiedSTDIODesktop onlyBusiness & Commerce

Overview

AI-generated overview

Local MCP server for Ingeniux CTnP that lets an assistant work with personalization, A/B testing and audience management through the CTnP REST API.

What you can do
Connect an assistant to an Ingeniux CTnP instance for personalization and A/B testing work, using the configured REST API base URL and bearer token. Work with audience management through the same API. Pass CMS group IDs as permission context and optionally a CMS user ID and display name for personalization context. Support multi-tenant setups through an optional connection ID. The manifest lists no individual tools, so the exact operations are not documented here.
When to use it
Use it when you run Ingeniux CTnP and want an assistant to help with personalization, A/B testing or audience management against your own instance, including multi-tenant setups.
Requirements
Runs locally as an npm package via npx, so Node.js is needed. Requires CTNP_API_URL and CTNP_BEARER_TOKEN; CTNP_CMS_URL and CTNP_CMS_GROUP_IDS are also expected. Optional: CTNP_CMS_USER_ID, CTNP_CMS_USER_NAME, CTNP_CONNECTION_ID and CTNP_TIMEOUT_MS. Network access to your CTnP instance is required.
Before you install
Requires a bearer token for the CTnP API, which grants access to your instance; keep it out of shared configuration. The server can change personalization, test and audience data in your CMS, so review actions before they run. It sends requests to the CTnP API and CMS URLs you configure.

Installation

In SourceWeft

  1. Open CTnP MCP Server in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.7.7LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.