TunnelMind Data API
Wire Claude Code or Cursor to TunnelMind’s Tracker, Sigil, and Cross-lens Data API from one remote MCP instead of juggling separate HTTP clients.
Overview
ai.tunnelmind/data is a MCP server for the Build phase that exposes every TunnelMind Data API operation—Tracker, Sigil, and Cross-lens—as agent-callable tools over streamable-http.
What is this MCP server?
- Single MCP surface for Tracker, Sigil, and Cross-lens TunnelMind Data API operations
- Remote streamable-http endpoint at mcp-data.tunnelmind.ai — no local npm package required
- Version 1.0.0 server with GitHub source at TunnelMind/tunnelmind-data-api
- Suited to agent workflows that need unified supply-chain and cross-lens data calls
- Pairs with TunnelMind’s broader Sigil and Scry MCPs for ad-tech and threat intel
- Server version 1.0.0
- Single remote URL: mcp-data.tunnelmind.ai/mcp
- Covers Tracker, Sigil, and Cross-lens API surfaces
What problem does it solve?
Agents and solo builders waste time copying TunnelMind REST docs and splitting calls across Tracker, Sigil, and Cross-lens when one workflow needs several API surfaces.
Who is it for?
Builders already on TunnelMind who want one MCP entry for Data API tooling during integrations and agent automation.
Skip if: Teams that only need generic SQL/Postgres access or who are not using TunnelMind’s ad-supply and cross-lens stack.
What do I get? / Deliverables
After you register the remote MCP, your agent can run unified TunnelMind Data API operations from the IDE without bespoke client code for each product line.
- Registered remote MCP pointing at TunnelMind Data API
- Agent-accessible tools for unified Data API operations
- Reduced custom HTTP glue for TunnelMind workflows
Recommended MCP Servers
Journey fit
Canonical shelf is Build because solo builders add this when connecting agents to an external data and verification backend. Integrations is the right subphase for a streamable-http MCP that exposes every Data API operation as agent-callable tools.
How it compares
TunnelMind-specific Data API MCP, not a generic database or BI connector skill.
Common Questions / FAQ
Who is ai.tunnelmind/data for?
Solo builders and small teams using TunnelMind who want Claude Code, Cursor, or similar agents to call Tracker, Sigil, and Cross-lens through one MCP server.
When should I use ai.tunnelmind/data?
Use it while building or automating integrations that need TunnelMind Data API operations, especially when agents should orchestrate cross-lens or supply data without custom HTTP wrappers.
How do I add ai.tunnelmind/data to my agent?
Add the remote MCP URL https://mcp-data.tunnelmind.ai/mcp (streamable-http) in your client’s MCP configuration per TunnelMind docs, then restart the agent session.