TapCue

TapCue API and AI connector

For TapCue Pro. Last updated October 12, 2026

Save a link to TapCue from your phone or browser, then let your own script or AI assistant pick it up. A common setup: a reason called For AI that goes to a TapCue inbox destination, so those saves are sent nowhere else, and an API key that can only see that reason.

1. Set it up

  1. In TapCue, add the destination TapCue inbox (Destinations). It keeps saves in your TapCue history and sends them nowhere.
  2. Point a reason at it, for example For AI (Categories). To also send those saves somewhere else, use "Also send to".
  3. At tapcue.app/app, under Settings, create an API key. Choose which reasons it can see, and whether it is read only or full (full can also add, change, mark done and delete saves). The key is shown once.

2. Connect an AI assistant (MCP)

TapCue has a connector for apps that support the Model Context Protocol, such as Claude, ChatGPT and Cursor.

Connector URLhttps://api.tapcue.app/mcp
Sign-inYour API key as a bearer token: Authorization: Bearer tck_…
URL onlyIf the app can't send a header, use https://api.tapcue.app/mcp/tck_… with your key at the end. Treat that URL like a password.

For example, in Claude Code:

claude mcp add --transport http tapcue https://api.tapcue.app/mcp --header "Authorization: Bearer tck_…"

The assistant can then list your saves, read one, and with a full key mark it done, reword it, move it, add one or delete it. A full key can also set TapCue up for you: list your destinations, check a template against a sample save, and create or change a reason and the exact format it writes. Ask it something like "What's new in my For AI saves? Summarise each link."

3. Ways to use it with an AI assistant

Once the connector is added, ask in plain words. These are prompts you can paste as they are. The ones marked full key change your saves, so they need a key with full access; the rest work with a read-only key. To read the pages behind your links, the assistant also needs to be able to browse the web.

Catch up

  • "What's new in my For AI saves? Give me two lines on each."
  • "Read everything I saved to Read later this week and tell me which three are worth my time, and why."
  • "Summarise the video I saved yesterday in five bullet points, with timestamps if you can find them."
  • "Turn this week's saves into a short newsletter I could send to my team."

Put a save to work

  • "Read the SEO article I saved and apply its tips to my website. List what you'd change first."
  • "I saved a post about speeding up web apps. Check my project against it and fix what's missing."
  • "Use the recipe I saved to Cook this to make a shopping list for four people."
  • "Compare the three laptops in Buy this: price, weight, battery. Which would you pick for travel?"
  • "Read the tutorial in my For AI saves and build what it describes in this project."

Organise full key

  • "Go through Just save and move each one to the reason that fits best. Tell me what you moved."
  • "Anything in Read later that is really a video? Move it to Watch later."
  • "Find saves about the same topic and tell me which reason I should create for them."
  • "Find links I saved more than once and delete the extra copies."

Rename full key

  • "Some of my saves have vague headlines like 'Twitter post to read later'. Open each link and give it a headline that says what it is."
  • "Rewrite the headlines in Buy this so each starts with the product name."

Work through a list full key

  • "Take my For AI saves that aren't done, one at a time: read it, give me the key points, then mark it done."
  • "Summarise what I saved to For AI since yesterday, then mark those saves done."
  • "Mark everything in Read later older than a month as done."

Save from the conversation full key

  • "Save this link to Read later with the note 'for the Q4 plan'."
  • "Save the three sources you just used to my For AI reason."

Tip: a reason set to TapCue inbox makes a tidy inbox for your assistant. Share a link to it from your phone, then ask the assistant to pick up what's new.

4. Use the API from a script

Base URL https://api.tapcue.app/v2/api. Send your key as Authorization: Bearer tck_…. Answers are JSON. Up to 120 requests a minute per key.

curl -H "Authorization: Bearer tck_…" "https://api.tapcue.app/v2/api/saves?category=For%20AI&done=false"
RequestWhat it doesKey
GET /meThe key's name, access and the reasons it can see.read
GET /savesList saves, newest first. Options: category (name, key or id), done=false or true, since (ISO time), q (search), limit (up to 100), order=oldest, cursor (the nextCursor of the page before).read
GET /saves/{id}One save.read
POST /saves/{id}/doneMark it done. Send {"done": false} to undo.full
PATCH /saves/{id}Change done, headline or category.full
POST /savesAdd a save: url and/or text, category, optional note.full
DELETE /saves/{id}Delete it from TapCue. Notes already written to your other apps stay there.full

A save looks like this:

{
  "id": "c41f…",
  "url": "https://example.com/article",
  "headline": "Article on sourdough starters for AI",
  "title": "The Complete Sourdough Starter Guide",
  "note": "compare with the other two",
  "text": null,
  "source": "example.com",
  "category": { "id": "…", "key": "ai", "name": "For AI" },
  "tag": "#for-ai",
  "savedAt": "2026-10-12T15:04:05.000Z",
  "savedFrom": "Android",
  "status": "delivered",
  "destination": "TapCue",
  "alsoSentTo": [],
  "done": false, "doneAt": null, "doneBy": null
}

TapCue keeps the link and what you wrote, not the page itself: fetch url to read the page. Errors come back as {"error": "…", "code": "…"} with a matching HTTP status (401 bad key, 402 the account is not on Pro, 403 the key is read only, 404 not found or outside the key's reasons, 429 too many requests).

Good to know

Questions: support@tapcue.app