The MCP server

One base URL, https://xinquji.com/api/mcp, served over Streamable HTTP. No install, no local process, no API key to paste. Point a client at it and the tools show up.

Claude Code

claude mcp add --transport http xinquji https://xinquji.com/api/mcp

Claude Desktop, Cursor and other clients

{
  "mcpServers": {
    "xinquji": {
      "url": "https://xinquji.com/api/mcp"
    }
  }
}

No API keys

Search and reads are anonymous, so an agent can explore the catalog the moment it connects. The first time it tries to create a draft it hands you a one-time link. You approve it in a browser you are already signed into, and the connection is bound to your account from then on. No token ever passes through the transcript.

Nothing to generate, nothing to store in your dotfiles
One click in a browser you already trust
Revoke any connection at any time

Manage your connections How the link flow works

How the link flow works

1Your agent calls submit_product or submit_article with a product URL or article content.
2Xinquji fetches the site and drafts the listing.
3You get a review link and approve the connection in your browser.
4You finish it in the browser: images, badge, plan, then submit for review.
5A human reviews it before it goes live.

Optional durable token

Browser approval only binds the current client session, so a server restart means approving again. To skip that, generate a long-lived access token under MCP connections in your settings and add it to the client's Authorization header. The token lives in the database, survives restarts, and can be revoked at any time.

Tools

Every tool is callable from any MCP client. The read tools need no approval at all.

search_products
Find launched products in plain language.
get_product
The full public listing for one product.
list_topics
The topic/category catalog.
search_articles
Search published editorial articles.
get_article
One article with the products it links to.
get_feed
The public community activity feed.
get_user_profile
A maker's public profile and published work.
check_product_readiness
Audit a URL before submitting: badge, duplicates, listing quality, topic suggestions.
connect_account
Connect or check this session's account binding.
get_my_content
Status of your own products and articles.
submit_product
Scrape your site, draft the listing, hand back a review link.
update_product
Open an edit draft for a product you own.
claim_product
Claim an existing listing after badge verification.
submit_article
Open an article draft.
update_article
Open an edit draft for an unpublished article.

An agent can only open drafts

An agent can never publish, pick a plan, pick a launch date, or pay. It opens a draft and hands you the link; you take over in the browser. Claiming a product is the only direct write to the live catalog, and it requires the website badge to be verified.

You can review and revoke connected clients at any time: Open settings

https://xinquji.com/en/api-mcp