Skip to main content

​
TypeScript

import { init } from "mcp-tap";

init({ apiKey: "tap_your_project_key" });

// That's it. All supported SDK calls are now captured automatically.

​
Python

import mcp_tap

mcp_tap.init(api_key="tap_your_project_key")

# All supported SDK calls are now captured automatically.
After calling init(), every call to Anthropic, OpenAI, MCP callTool, Composio executeAction, and HTTP requests to known AI APIs are intercepted, measured, and sent to the mcp-tap dashboard.

​
What happens next

Once initialized, mcp-tap captures events based on which integration path is active:
PathHow it worksBest for
SDK patchinginit() monkey-patches installed AI SDKsApplication code that calls LLM/tool APIs directly
Server instrumentationinstrumentServer() wraps MCP Server request handlersMCP server authors who want to log incoming tool calls
Stdio proxymcp-tap binary sits between an MCP client and serverIDE integrations, zero-code monitoring of any MCP server