MCP.so
ログイン

Tyton MCP Server認証済み注目

@usetyton

Tyton MCP Server について

Meta Pixel が動かない、または Meta トラッキングの監査が必要ですか?Tyton MCP が不具合の原因を見つけ、Meta Pixel と Conversions API をセットアップします。https://usetyton.com

#meta-ads#meta-pixel#conversion-tracking#facebook-capi#attribution#analytics#marketing#server-side-tracking

Tyton MCP Server の設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

{
  "mcpServers": {
    "tyton": {
      "url": "https://mcp.usetyton.com/audit"
    }
  }
}

Tyton MCP Server のツール

15

Creates a Tyton signup and Connect link for one website. Takes either a saved free audit (audit_id and audit_key, which brings the report along) or site_url, the customer's live https website. customer_approved records that the customer agreed to set up Tyton. Returns authorization_url for the customer, plus a private request_id and poll_token for checking the request's status. The customer can pick the free plan or a paid one; existing accounts with a plan skip that step. The link grants no access and starts no tracking by itself.

Checks a signup and Connect request using its request_id and private poll_token. Returns waiting, unavailable or expired, or, after the site owner approves, this connection's server URL, private server key, public browser key and project. The suggested polling interval is 5 seconds. A connection is not tracking approval or activation.

Starts a new free audit session for a URL. Returns a private capability (audit_id and audit_key), revision 0 and an initial request_id for the first evidence save, so a lost save response can be retried safely. Saves nothing. The capability covers only this audit record, not access to the website.

Reads an existing audit using its private capability. Returns recorded context, scoped observations, provenance, component coverage, the current decision with open questions, and the report link. Read-only; does not verify the site's backend or grant access to it.

Saves answers about one audited component to the audit. audit_scope records the customer's choice between continuing the investigation and a public-only audit; availability_expectation records whether unavailable controls are expected. Both must have source human_reported. Earlier topics are kept; a new answer replaces the same topic. A public-only choice allows a partial report without further access requests. Returns the updated audit decision and report link.

Saves bounded runtime evidence to the same audit run: sanitized observations from a real browser, authorized backend inspection or a destination UI, with the consent state and observation time. Does not run a browser or send events. A check whose evidence type does not prove it is stored as unknown. Returns the updated findings and report link.

Connects a Tyton site to this connection using a single-use pairing code from the site's card on usetyton.com (valid for 15 minutes). Returns the site's server key and browser key, shown only once, with configuration examples for common MCP hosts.

Inspects one public page's HTML and saves a partial audit report, without signup. Takes the audit session fields and the page URL, plus optional sanitized HTML supplied by the agent, which is stored as unverified evidence. One session can hold several related components. Returns evidence, limitations and discovery actions, not a full tracking-health verdict.

Discovers or configures reviewed v2 setup for a site. With only a URL it is read-only, needs no Pixel and returns setup guidance. With a real Pixel ID on a connected project, it saves the project's site URL and Pixel ID; switching an existing Pixel or site requires confirm_change. Does not approve, install or activate tracking.

Saves checkout and landing answers (payment provider, landing type and route, checkout domains) for the connected project and returns the reviewed server SDK success-callback contract. Does not install an integration or prove provider support; approval and activation are separate. Requires a connected site.

Reads the connected project's configuration: site URL, Pixel ID, token status and saved checkout answers. Read-only. Configuration and token status are not plan approval, callback verification, activation or Meta receipt. Requires a connected site.

Checks a page's static HTML for Tyton container and Meta Pixel references, using a public fetch or HTML supplied by the agent, and compares them with the connected project. Read-only. Does not verify runtime callbacks, activation, consent behavior or Meta receipt. Requires a connected site.

Reads aggregate browser and server event observations, delivery statuses, and the known-crawler protection mode and counts for the connected site. Read-only. Counts are not unique business conversions, current installation verification or proof of Meta deduplication. Requires a connected site.

Saves code review findings from the customer's repository to the audit: server-side events, dedup IDs, Pixel and container presence, payment provider, framework, backend location and existing Conversions API quality, plus the relative paths reviewed and any inapplicable checks with reasons. Unknown values stay unknown, not failed. Findings are stored as agent-reported, not verified deployed behavior. A group label is a label only; each report stays separate. Returns the updated audit decision and report link.

Returns Tyton guidance on one topic. meta_setup is the dashboard's nine-step Meta checklist (business, dataset, website, Conversions API token, testing), optionally a single step. website_management covers the website selector, per-project agent connections and deletion. Other topics: install, events, dedup, crawler_protection, create_pixel, create_business, consent, pricing, privacy, performance, gtm, platforms, faq. Read-only reference text, not saved checklist state or proof of delivery.

概要

What is Tyton MCP?

Tyton MCP is a hosted MCP server from Tyton that lets an AI coding agent audit a website's Meta Pixel and Conversions API tracking, then install the pixel, server events and deduplication on the site you already have. The audit is free and needs no account.

Tyton covers Meta only: the Pixel in the browser, the Conversions API (CAPI) on the server, and one shared event_id so Meta counts each conversion once. It uses Meta's official event names (Purchase, Lead, AddToCart, InitiateCheckout, ViewContent, CompleteRegistration and the rest). Next.js and React are the setups Tyton is built around. On Webflow, Framer or Shopify the audit can still inspect the page and the browser container can be added, but server events need a backend the agent can edit. Tyton is a product of Kitra LLC.

How to use Tyton MCP?

Tyton runs two remote endpoints over streamable HTTP:

  • https://mcp.usetyton.com/audit is the endpoint shown on the Tyton website and on this listing. It carries the free audit tools plus signup and pairing.
  • https://mcp.usetyton.com/mcp is the endpoint in the README. It carries everything above plus the setup tools (conversion plans, CAPI token storage, SDK installation, live checks).

The audit works with no key. When you want the working setup, create an account on usetyton.com. The Free plan needs no card. Setup tools then either show a "Sign in with Tyton" prompt, where you sign in and approve one website in the browser, or you use the pairing code from the site card on usetyton.com: the agent calls connect with that code and gets a server key for that project only.

Claude Code

claude mcp add --transport http tyton https://mcp.usetyton.com/mcp

Claude Desktop and claude.ai

Open Settings, Connectors, Add custom connector, and paste https://mcp.usetyton.com/mcp (or the /audit URL if you only want the free audit).

Cursor

Add Tyton to .cursor/mcp.json (or ~/.cursor/mcp.json):

{
  "mcpServers": {
    "tyton": {
      "url": "https://mcp.usetyton.com/mcp"
    }
  }
}

VS Code

Add the server to .vscode/mcp.json:

{
  "servers": {
    "tyton": {
      "type": "http",
      "url": "https://mcp.usetyton.com/mcp"
    }
  }
}

Then send your agent a prompt such as "Audit tracking on [my website URL]."

Key features of Tyton MCP

  • Free audit of Meta Pixel and Conversions API tracking, with no account or payment.
  • A Free plan for 1 site and 10,000 events a month, with no card needed.
  • Browser Pixel plus server-side Conversions API events, sent through Tyton to Meta.
  • Deduplication: browser and server reports of one action share the same event name and event_id.
  • A conversion plan you review and approve before anything is activated.
  • Delivery status per event: received, sent to Meta, retrying or needing attention.
  • Consent-aware setup, so browser tracking waits for permission.
  • Emails and phone numbers are hashed on arrival; raw event rows are deleted after 30 days on Pro and 7 days on Free and Starter.

Tyton MCP tools

The server reported 24 tools on /mcp and 16 on /audit when we checked.

  • Audit: begin_audit starts a free audit session, audit_site inspects one public page's HTML, submit_findings saves code review findings from your repository, and read_audit, record_audit_context and record_audit_runtime resume an audit and add evidence.
  • Signup and pairing: start_signup, get_signup_status and connect (single-use pairing code, valid for 15 minutes).
  • Setup: setup_tracking, setup_server, setup_status, verify_install, get_sdk_installation and save_capi_token.
  • Conversion plans (on /mcp): propose_conversion_plan, read_conversion_plan and approve_conversion_plan, which requires an explicit yes from the customer.
  • Monitoring: tracking_status, check_live_setup and get_setup_progress.
  • Docs: read_docs returns guidance such as the nine-step Meta setup checklist.

Use cases of Tyton MCP

  • Finding out why Meta tracking stopped: "Check the tracking on [my website URL]. Tell me what needs fixing."
  • Fixing purchases, leads or other events missing from Events Manager.
  • Removing duplicate Purchase events after adding the Conversions API: "Check whether my purchase events are being counted twice."
  • Adding server-side Meta tracking to a Next.js or React app because the browser pixel misses events.
  • Improving low Event Match Quality.

Troubleshooting Tyton MCP

  • Setup tools are missing: the /audit endpoint only carries the audit and pairing tools. Switch to https://mcp.usetyton.com/mcp for the full setup.
  • Server events can't be installed: server events need a backend the agent can edit. On Webflow, Framer or Shopify only the browser container can be added.
  • Pairing code rejected: pairing codes are single-use and valid for 15 minutes. Generate a new one from the site card on usetyton.com.
  • Events not showing as live: after activation, the agent checks fresh event IDs with check_live_setup, which looks at the last 24 hours.

よくある質問

1

Is the Tyton MCP audit free?

Yes. The audit runs with no key, no account and no payment. An account is only needed when you want Tyton to set up and run the working tracking.

2

How much does Tyton cost?

Tyton has a Free plan for 1 site and 10,000 events a month, with no card needed. Browser and server copies each count as an event. At 10,000, server tracking (Conversions API) pauses until the 1st of next month or until you upgrade. The browser Pixel keeps running, and events from the paused days aren't saved or sent later. Starter is $17 a month for one site and 100k events a month, and Pro is $49 a month for up to three sites and 500k events a month. Yearly billing saves 20%. All plans include Pixel and Conversions API setup and deduplication.

3

Which MCP URL should I use?

Use `https://mcp.usetyton.com/audit` for the free audit only, or `https://mcp.usetyton.com/mcp` for audit plus paid setup. The README documents the `/mcp` URL for all clients.

4

Does Tyton work with Claude Code and Cursor?

Yes. The README gives a `claude mcp add --transport http` command for Claude Code and a `.cursor/mcp.json` entry for Cursor. The website also lists Codex, Windsurf, Lovable, Bolt and v0.

5

Does Tyton support Google Ads or TikTok tracking?

No. Tyton covers Meta only: the Meta Pixel and the Meta Conversions API.

6

Will the agent change my tracking without asking?

Tyton requires you to approve the conversion plan in chat before it is activated, and its tools tell agents never to infer approval or activate tracking manually.

コメント

「データと分析」の他のコンテンツ