SwipeHarbor MCP

npx add-mcp 'https://swipeharbor.com/api/mcp'

Your research, connected.

Use your MCP-compatible assistant to search stored ads, inspect their evidence, and compare creative ideas.

Included with your paid membership. Check your current MCP access status in your account.

Manage MCP connections →

Four tools. Stored evidence.

Each tool reads the existing archive. It does not create a capture, transcript, or AI generation. Results include evidence text and library links. They do not include signed media URLs or private collection notes.

search_ads

Search up to 12 stored ads per page.

4 data units

get_ad_evidence

Read the stored evidence for one ad.

1 data unit

get_funnel

Inspect the recorded destination steps for one ad.

1 data unit

compare_ads

Compare two to four stored ads.

1 data unit per ad

Observed dates and recorded destinations are research evidence. They do not prove spend, conversions, profit, or continuous ad delivery.

Connect in three steps

1. Open MCP connections in your account and check your access status.
2. Create a named token. Copy it once and keep it private.
3. Use Streamable HTTP and the server URL below. Supply your token in the Authorization header as Bearer YOUR_TOKEN.

Server URL
https://swipeharbor.com/api/mcp

Your client must support custom authorization headers. The account page provides a configuration you can copy; the required format can differ by client. Use its connection check to verify access without an ad query.

Keep up to five active tokens. New tokens expire after 30 days. You can revoke a token at any time, including after membership expiry or when your research quota is full.

Shared account limits

MCP requests

20 per rolling minute · 2,000 per UTC month

All tools/API requests

60 per rolling minute · 20,000 per UTC month

Data units, shared with Tools

20 per rolling minute for machine reads · 10,000 per UTC month

All tokens use the same account allowance. Requests and data units have separate limits. Five search requests can use the 20-unit minute allowance. Shared service capacity can also limit a request.

Connection checks send initialize and tools/list: two requests and zero data units. Authenticated protocol requests and failures use request quota. An admitted source read uses its data units even if the source fails.

A limit returns HTTP 429 with its scope, remaining allowance, UTC reset, and retry delay. Your account shows the current usage. If usage cannot be read, it shows Usage unavailable.

Current access

MCP requires a verified account and an eligible, active paid membership. Founding and standard members receive the same allowances. Trials and complimentary access do not include MCP. An unsupported or retired paid plan shows its own eligibility reason.

The account page shows the current decision before token creation. If membership facts are unavailable, access stays unavailable until they can be checked. This is part of the current membership, with no separate MCP sales tier.

A protocol example

Example · 13 October 2026. This fixed example contains no ad source data and sends no request.

{"jsonrpc":"2.0","id":2,"method":"tools/list","params":{}}

The response lists search_ads, get_ad_evidence, get_funnel, and compare_ads.

{
  "jsonrpc": "2.0",
  "id": 2,
  "result": {
    "tools": [
      {
        "name": "search_ads"
      },
      {
        "name": "get_ad_evidence"
      },
      {
        "name": "get_funnel"
      },
      {
        "name": "compare_ads"
      }
    ]
  }
}

This response excerpt omits the tool schemas. It is an example, not a live access check.

Cost and availability

SwipeHarbor makes no model call for these MCP tools. Your external assistant may charge its own fees.

This release supports the four MCP operations above. A separate REST API is not available.

Open your MCP connections or return to the ad library.