This guide provides the steps to set up the Tempo Content Intelligence (CI) MCP Server locally.
This guide provides the steps to set up the Tempo Content Intelligence (CI) MCP Server locally.
Clone the repository and install the project dependencies:
The server requires specific environment variables to function, depending on whether you are connecting to a remote content-intelligence backend or running in embedded mode.
Copy the example configuration (if applicable) or export the following variables in your .env or .env.local file:
| Variable | Description |
|---|---|
PORT | The port for the server (defaults to 3000). |
CI_NEXUS_DB_SECRET_ARN | Required for embedded mode. The AWS Secret ARN containing your Nexus Postgres credentials. |
CONTENT_INTELLIGENCE_BASE_URL | Set to http://127.0.0.1:$PORT for embedded mode, or a remote URL for production-style deployments. |
MCP_BEARER_TOKEN | An optional token for securing the /mcp surface. |
CI_LLM_MODE | Set to stub for deterministic testing or anthropic for production LLM assessments. |
Once configured, start the development server using Bun's hot-reloading capability:
For production-like execution, use the start script:
Verify your setup by running the repository's internal quality gates:
bun run typecheckbun run lint and bun run formatbun run backtest:model-validation to generate performance artifacts against your historical Nexus data.For architectural deep-dives, see the Overview and the documentation files in the docs/ folder of the repository.