Tengence Search MCP
Thin MCP wrapper for the Tengence Search SaaS: push data and search via official APIs.
Power your agent
Add this server
The publisher's own command. Not a PlugMCP endpoint.
Local command
npx -y @tengence/[email protected]
Credentials from the publisher
- TENGENCE_SOLUTION_BASE_URL — solution-service base URL used for startup auto-registration. Defaults to https://console.tengence.com.
- TENGENCE_SEARCH_API_KEY — Search API key (app-level, sk-) for the /v1/search endpoint. Optional: search_init auto-provisions and stores it locally (state.json).
- TENGENCE_DATASET_API_KEY — Dataset API key (sk-) for the /v1/push/data endpoint.
- TENGENCE_SITE_URL — siteUrl used as the idempotency match key during registration. Defaults to https://tengence-mcp.local/<deviceId>.
- TENGENCE_SEARCH_BASE_URL — Override for the search API base. Defaults to https://api.tengence.com.
- TENGENCE_PUSH_BASE_URL — Override for the push API base. Defaults to https://api.mossego.com.
- TENGENCE_SEARCH_HOME — Internal runtime data directory holding state.json (device identity + registration credentials). Defaults to ~/.tengence/search-mcp.
Provider
Claude Code
TENGENCE_SOLUTION_BASE_URL=<value> TENGENCE_SEARCH_API_KEY=<value> TENGENCE_DATASET_API_KEY=<value> TENGENCE_SITE_URL=<value> TENGENCE_SEARCH_BASE_URL=<value> TENGENCE_PUSH_BASE_URL=<value> TENGENCE_SEARCH_HOME=<value> claude mcp add com.tengence-search -- npx -y @tengence/[email protected]
Run in a terminal.
Claude Desktop
{
"mcpServers": {
"com.tengence-search": {
"command": "npx",
"args": [
"-y",
"@tengence/[email protected]"
],
"env": {
"TENGENCE_SOLUTION_BASE_URL": "<value>",
"TENGENCE_SEARCH_API_KEY": "<value>",
"TENGENCE_DATASET_API_KEY": "<value>",
"TENGENCE_SITE_URL": "<value>",
"TENGENCE_SEARCH_BASE_URL": "<value>",
"TENGENCE_PUSH_BASE_URL": "<value>",
"TENGENCE_SEARCH_HOME": "<value>"
}
}
}
}claude_desktop_config.json
Remote URL or a command on your machine? How the two installs differ
Run on PlugMCP
Host a copy with our keys and logs.
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
LaunchRelated MCP
View more- Firecrawl🔥 Official Firecrawl MCP Server - Adds powerful web scraping and search to Cursor, Claude and any other LLM clients.
- NNotionToken-auth Notion MCP: pages, databases, blocks, comments, files. Runs headless in CI and agents.
- Context7Context7 Platform -- Up-to-date code documentation for LLMs and AI code editors
Related skills
View all- reaReverse engineer anything with agents, from app behavior down to native binaries.
- rea-changelog-updatePrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization.
- rea-tool-designDesign or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.
Thin MCP wrapper for the Tengence Search SaaS: push data and search via official APIs.
README is not crawled yet. Open the repository
- How do I install Tengence Search MCP?
- Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.
- Does Tengence Search MCP need an API key?
- The publisher lists these environment variables: TENGENCE_SOLUTION_BASE_URL, TENGENCE_SEARCH_API_KEY, TENGENCE_DATASET_API_KEY, TENGENCE_SITE_URL, TENGENCE_SEARCH_BASE_URL, TENGENCE_PUSH_BASE_URL, TENGENCE_SEARCH_HOME.
- What transport does Tengence Search MCP use?
- Tengence Search MCP runs locally over stdio.
- When was Tengence Search MCP last checked?
- Last checked 2026-10-16. Thin MCP wrapper for the Tengence Search SaaS: push data and search via official APIs.
No tool list yet. Remote servers get one after the first health check.