Skip to main content
The MCP endpoint is https://api.refmatter.com/mcp (Streamable HTTP). It holds no credentials of its own: every client sends its workspace API key as a bearer token, and the server forwards it to the API. Requests without a key get 401.

Tools

lookup_item, lookup_account, and the four page tools charge for a live or first served page with rows. Their descriptions state the price and what is free, so an agent can decide before calling. Point an agent at resolve_url first when it is unsure about a link: the answer is free and immediate. Use import_url instead when the media bytes have to be kept. list_items takes one account selector that carries the platform — a natural key, <platform>:@handle, or an account URL — and reads only the parameters that platform supports; see Naming the account. A parameter the platform does not read is refused with a hint rather than ignored, so an agent learns the right call from the error instead of getting a silently different page. Tool errors carry the API’s safe details, so an agent sees retryAfterSeconds on a rate limit and the hint on an unsupported link rather than retrying blindly. The social://openapi resource exposes the API contract so an agent can read the exact schemas.

Example prompts

  • “Look up this TikTok link and tell me its view count and caption.”
  • “Read the transcript of this YouTube video without saving it.”
  • “Is this link something you can read? Don’t spend a credit finding out.”
  • “Save this YouTube video as a reference and tell me when the media is ready.”
  • “List my references tagged hook from the last week and summarize their titles.”
  • “Extend the media hold on the last reference to 90 days.”
  • “List the newest reels on the NASA Instagram profile and summarize the captions.”
  • “Which ads is Dot & Key running in India right now, and how many are there in total?”