tereno_evidence_reference — Tereno on Base MCP Tool
tereno_evidence_reference
(tereno evidence reference) is one of 10 tools on the
Tereno on Base
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call tereno_evidence_reference from your client
- Claude Code Tereno on Base tereno_evidence_reference run in your project directory
- Claude Desktop Tereno on Base tereno_evidence_reference ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Tereno on Base tereno_evidence_reference ~/.cursor/mcp.json
- VS Code Tereno on Base tereno_evidence_reference .vscode/mcp.json
- Zed Tereno on Base tereno_evidence_reference ~/.config/zed/settings.json
- Windsurf Tereno on Base tereno_evidence_reference ~/.codeium/windsurf/mcp_config.json
- Cline Tereno on Base tereno_evidence_reference ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Tereno on Base tereno_evidence_reference ~/.gemini/settings.json
- Grok Tereno on Base tereno_evidence_reference .mcp.json (in your project root)
- ChatGPT Tereno on Base tereno_evidence_reference Settings → Connectors → Advanced → Developer mode
- Claude.ai Tereno on Base tereno_evidence_reference Settings → Connectors → Add custom connector
- LangChain Tereno on Base tereno_evidence_reference pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http tereno https://www.tereno.xyz/api/mcp
Other tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.