Mark's Reports

All reports · published 2026-04-19

MCP Server Map

Every MCP (Model Context Protocol) server that an agent in this stack can reach, plus which agents have it wired in, auth method, and what tools it exposes.

Why this map exists. Before this file, "which agent can call which MCP tool?" required reading five config files on three machines. That friction slowed every cross-agent handoff. Read this map before writing an inter-agent brief — if the target agent doesn't have the MCP you expect, the brief will silently fail.

Refresh. Hand-curated. Update whenever an MCP server is added, removed, or its auth rotates. No generator (yet — auto-discovery would need to query each agent's config file, possible future work).


1. TP3-owned MCP servers (Apex-hosted)

These are the ones we run. Everything else in this map is a third-party MCP we *consume*.

ServerTransportEndpointAuthPrimary toolsSource file
tp3-omi (memory — canonical)SSE over HTTPShttps://omi-mcp.thebarnetts.info/rpcX-TP3-MCP-TOKEN headertwin_memory_write · twin_memory_read · twin_memory_search · twin_memory_list · twin_memory_broadcast · omi_ingest_transcript · omi_get_status · omi_search_memories · omi_search_memories_unified · slack_post_messagetp3_scripts/tp3_mcp_omi_sse_server.py on port 8933
tp3-omi (stdio)stdiolocal processenv TP3_OMI_API_KEYsame as abovetp3_scripts/tp3_mcp_omi_stdio_server.py
tp3-omi-public (OAuth gateway)SSE over HTTPShttps://omi-mcp-public.thebarnetts.infoOAuth 2.1 (for claude.ai web/mobile)same as tp3-omicloudflare/tp3-omi-mcp-gateway/ Worker
tp3-biometricSSE over HTTPSport 8934 (behind Cloudflare Tunnel if wired)token headerbiometric-specific search/ingesttp3_scripts/tp3_mcp_biometric_sse_server.py
tp3-biometric (stdio)stdiolocal processenv tokensametp3_scripts/tp3_mcp_biometric_stdio_server.py

Backing store: Postgres (tp3_memories 3072-d Gemini · tp3_memories_local 768-d Ollama) + MinIO (tp3-omi-raw-events). See data_flow_map.md for upstream/downstream edges.


2. Third-party MCP servers consumed by our agents

ServerTransportWhat it doesAuthNotes
tp3-zapierZapier-hosted MCPGoogle Docs append + create documentZapier OAuthFree tier, 100 tasks/mo, 1 call = 2 tasks. Supersedes the gcloud service-account approach. See reference_zapier_mcp.md.
Gmailhosteddraft · list drafts · search threads · read thread · label opsOAuthUsed by G16 Claude for email drafting.
Google Calendarhostedlist/create/update/delete events · suggest time · list calendarsOAuthG16 Claude.
Google Docs (direct)hostedappend text · create from textOAuthRedundant with tp3-zapier but direct.
HuggingFacehostedpaper search · hub search · space search · doc fetch · dynamic spaceHF tokenFor research / model discovery.
CloudflarehostedR2 · KV · D1 · Hyperdrive · Workers · docs search · account mgmtCF API tokenMatches CLOUDFLARE_API_TOKEN in Apex .env.
Slackhostedsend message · read channel/thread · search · create canvasSlack tokenUse for DMs to Mark (user U0AK03UP9SQ). Keep messages bullet-point, max 10 bullets.
Make.comhostedscenarios · data stores · hooks · executions · blueprint validationMake API keyPresent; not currently in active use.
MCP Registryhostedsearch/suggest connectorsDiscovery layer — use to find new MCP servers.
scheduled-tasks (internal)hostedcreate · list · update scheduled tasksFor scheduling remote agent triggers.
Chrome DevTools MCPstdio via WSLbrowser automation, DOM inspect, network monitor, console, screenshotsnoneWired via Windows headless Chrome on port 9333. Autostart VBS installed. Restart Claude Code after config change. See reference_chrome_devtools_mcp.md.
Claude Previewstdiopreview start/stop · click · eval · fill · screenshot · snapshotnoneDev preview automation.
Claude in Chromestdiofull browser control · tabs · forms · uploads · shortcutsnoneRicher than Chrome DevTools MCP — can drive actual sessions.
ccd_directorystdiorequest directorySession-scoped file access grants.

3. Which agent has which MCP wired in

Blank cells = not yet wired or not confirmed. Fill in as you verify.

Agenttp3-omitp3-biometrictp3-zapierGmailCalendarSlackChrome DevToolsCloudflare
G16 Claude Code (this session)✅ (HTTPS)
Apex Claude Code✅ (HTTPS or stdio)????✅ (via script)— (no Chrome on Apex headless)?
claude.ai (web / mobile)✅ via omi-mcp-public.thebarnetts.info (OAuth)
Cursor??
Antigravity✅ registered at C:\Users\Breez\.gemini\antigravity\mcp_config.json (HTTP enable UI broken — stdio proxy workaround pending)
Gemini CLI (Apex)✅ in ~/.gemini/settings.json (--approval-mode yolo for scripts)
Jules (GitHub)N/A — Jules only sees GitHub PRs/issues

4. Known gaps / TODOs


5. Fast onboarding checklist for a new agent

When a new agent (new Cursor install, new machine, new headless session) needs TP3 memory:

1. Write access → tp3-omi HTTPS (section 1 row 1). Header X-TP3-MCP-TOKEN: <token> from .env.

2. Read-only / OAuth flow (claude.ai web/mobile)omi-mcp-public.thebarnetts.info.

3. Local stdio fallback (if HTTPS flaps) → point at tp3_mcp_omi_stdio_server.py directly, env TP3_OMI_API_KEY.

4. Verify by calling twin_memory_list with limit: 3. If it returns rows, you're wired.

5. Announce yourself by writing a one-line memory: twin_memory_write with a session_start tag so the next agent sees you joined.


Source of truth