Tengence Search MCP

Lets an assistant push datasets to and run searches against the Tengence Search SaaS through its official APIs.

What it does

A thin MCP wrapper around the Tengence Search service. It exposes tools for pushing data to the /v1/push/data endpoint and for searching via the /v1/search endpoint, using the provider's official APIs. It runs locally over stdio and stores its runtime state, including device identity and registration credentials, in a local state file.

When to use it

Use it when you already work with Tengence Search and want an assistant to push datasets into it or query it directly from a local MCP client. It is a narrow integration, so it is only worth adding if that specific service is part of your workflow.

Requirements

Runs as a local process over stdio, installed from the npm package @tengence/search-mcp, so Node.js is needed. It uses environment variables including TENGENCE_DATASET_API_KEY, TENGENCE_SEARCH_API_KEY, TENGENCE_PUSH_BASE_URL, TENGENCE_SEARCH_BASE_URL, TENGENCE_SEARCH_HOME, TENGENCE_SITE_URL and TENGENCE_SOLUTION_BASE_URL. Network access to the Tengence endpoints is required, and the search key can be auto-provisioned and stored locally.