Connect

Ziyarex MCP server

Add one URL to Claude, Cursor or ChatGPT and these tools become things it can run, not just pages it can link you to. Make a QR code, build a store link, check what a link is getting clicked on, without leaving the conversation.

  • One endpoint
  • No account for most of it
  • Any MCP client
All the tools

The address

Wherever your client asks for an MCP server URL, this is it.

https://ziyarex.com/api/mcp

No key, no sign-up, nothing to provision. Paste it and the tools appear.

Adding it to your client

Three shapes cover almost everything. Restart the client afterwards.

Claude CodeOne command in your terminal.
claude mcp add --transport http ziyarex https://ziyarex.com/api/mcp
Claude Desktop, Cursor, WindsurfAdd it to the MCP section of the client's config file.
{
  "mcpServers": {
    "ziyarex": {
      "url": "https://ziyarex.com/api/mcp"
    }
  }
}
A client that only speaks stdioOlder clients can't open an HTTP connection themselves. mcp-remote bridges one.
{
  "mcpServers": {
    "ziyarex": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://ziyarex.com/api/mcp"]
    }
  }
}

What you can then ask for

You do not call the tools by name. You ask, and the assistant picks.

QR codes
  • Make a Wi-Fi QR code for the office network and save it as an SVG.
  • Make a dynamic QR code for the poster, pointing at the beta signup.
  • Point that printed code somewhere else now the beta is over.
  • How many times has it been scanned?
App links
  • Make one link that sends iPhones to the App Store and everyone else to the site.
  • Read the name, icon and rating off this Play listing.
  • Which countries clicked the launch link last week?
  • Pause that link.
Store sizes
  • What size does an iPhone 6.9-inch screenshot have to be?
  • List every icon file an Android app needs, with the paths.

The one thing that needs a key

The ASO audit reads every screenshot on a store listing through a vision model, so it costs a credit and has to know whose. Sign in, generate a key at ziyarex.com/aso/connect, and add it as a header:

{
  "mcpServers": {
    "ziyarex": {
      "url": "https://ziyarex.com/api/mcp",
      "headers": { "Authorization": "Bearer zyx_your_key_here" }
    }
  }
}

A key can spend your credits and read the audits you have run. It cannot buy anything or change your account. Revoke it on the same page and it stops working on the next call.

What is deliberately not on it

  • The PDF tools, the icon generator, the screenshot resizerThese do their work on your own device and never upload the file. Putting them on a server to make a longer list would break the one promise those pages make, so they stay where they are.
  • Their numbers, though, are hereAsk what size an App Store screenshot has to be, or which icon files an Android app needs, and you get the same table the tools are built on, without handing over a file.

Questions

What is MCP?

The Model Context Protocol: a standard way for an assistant to use an outside service. Adding this endpoint to your client is the whole setup — after that you ask for things in plain language and it calls the tool itself.

Do I need an account?

Not for the QR codes, the dynamic codes, the smart app links, their click stats or the store size tables. The only thing that needs one is the ASO audit, because it spends a credit.

Is anything I send stored?

Only what the tool has to store to work at all. A static QR code stores nothing. A dynamic code and a smart app link store their destination, because forwarding to it later is the point. Nothing else is kept, and there is no account behind an anonymous connection to keep it against.

Why can't it edit my PDFs or resize my screenshots?

Those tools run on your own device and never upload the file, which is a promise we would have to break to run them on a server. They stay in the browser. What is available over MCP is their reference data, so you can still ask what size a screenshot has to be or what icon files a platform needs.

What happens to the edit token for a link or code I make this way?

It comes back in the conversation, which is the only place it exists. On the website it is kept in your browser's own storage; a client has nowhere to put it, so it lands in the transcript and in whatever logs that client keeps. Save it somewhere you would keep a password, because it is the only key to that link.

Can I use this from a browser-based client?

Not yet. The endpoint sends no CORS headers, so a client that calls it from inside a web page will be blocked. Clients that connect from their own server, which is most of them, are fine.