tinkabot is Lauren Tan's official Marketplace template for wrapping an API into a Cursor or Agent plugin made of an MCP server and skills. This review covers its stated workflow, publishing gate, setup steps, and boundaries.
Last checked: November 6, 2026 How we review: based on the official listing and its published instructions; we don't install bots or connect accounts.
Open the official tinkabot listing.
What it does
The listing describes a fixed order of work: name the data shape of the API first, build the smallest scaffold that works, prove it locally, then ask once about affiliation and publish to Cursor Marketplace or cursor.directory.
Its instructions prefer an Agent Plugin layout (a root plugin.json, skills, and an optional mcp.json) unless rules, hooks, or agents are required. For public HTTP APIs that need no authentication, it keeps the MCP server as a zero-dependency stdio server until an SDK earns its install.
It describes a working style it calls Poteto Mode: concise, verified work that starts multi-step tasks with a principle-driven to-do list and cites which principle shaped a choice, such as "prove it works" and "model the domain". The listing also names a plugin called pstack among its capabilities.
Who it is for
It fits developers, developer-relations teams, and API owners who want a Cursor or Agent plugin for a service without hand-building the scaffold. It is most useful when you already know which API you want wrapped and can test the result in Cursor.
It is not a fit if you need a production SDK, a hosted backend, or a plugin that depends on complex authentication the listing does not cover.
Integrations
The listing shows an integrations section and names the pstack plugin, but it does not list connected accounts, permission scopes, or which marketplace credentials it uses. Inspect the integrations shown in the Add preview before connecting anything.
Routines
The public listing does not show any routines. Treat it as an on-request bot unless your copy's preview shows otherwise.
Safety check
Safety: tinkabot writes plugin code and can submit to Cursor Marketplace or cursor.directory; its instructions say it never publishes without your explicit word and an approval gate blocks submission, so check its integrations and any publishing access in the Add preview, and review the plugin files before you approve a submit.
Publishing a plugin puts code and an API's name in front of other people. Answer the affiliation question honestly, because it decides where the plugin goes. Do not paste private API keys into a plugin that will be published, and review what the MCP server calls before anyone installs it.
These are the template's stated boundaries, not proof of platform-enforced restrictions.
Step-by-step installation
- Open the official listing and confirm the creator is Lauren Tan.
- Choose the install action. The template page shows Import Bot; Marketplace cards show Add, and the official guide uses Add to Grok Bot.
- Review the memories, skills, and integrations in the app preview. Confirm the access shown fits a plugin-building bot.
- Choose Add Bot only after that review. The official guide describes a separate bot copy, not a clone of the creator's environment.
- Reinstall any plugins your copy needs, including pstack if the preview lists it.
- Start with a small public API and stop before publishing until you have tested the result in Cursor.
The listing does not give a setup time.
Three example tasks
- Wrap a public API: "Wrap this public weather API as an Agent Plugin. Name the data shape first and keep the MCP server zero-dependency."
- Prove it locally: "Show me how to install this plugin locally in Cursor and what output proves it works."
- Prepare to publish: "Get this plugin ready for cursor.directory, but do not submit until I say so."
Limitations and when not to use it
Do not use it when you cannot review the generated code. Remember the listed gap: Grok Bot itself only loads plugins from the Cursor dashboard or marketplace, so local testing happens in Cursor IDE. The listing does not document supported authentication types, scopes, or setup time.
Alternative templates
- Proto Bot fits when you want a feature prototype in your own app as a draft pull request rather than a plugin.
- Nightly Audit Engineer fits when the job is cleaning up an existing codebase.
FAQ
Does tinkabot publish my plugin automatically?
No. Its instructions say it never publishes to a marketplace unless the owner explicitly says to, and that an approval gate still blocks submission.
Where does it publish a finished plugin?
It asks once whether you work at the company or service. Yes routes to Cursor Marketplace; no or unsure routes to cursor.directory.
Can Grok Bot load the plugin locally while testing?
The listing says Grok Bot does not load local plugins from the local Cursor plugins folder, only from the Cursor dashboard or marketplace. Local proof still matters for Cursor IDE.
Compare the developer templates, or return to the Grok Bot templates hub.