TinTinWorkflows
GitHubSign in

ChatGPT for SEO, with workflows that are already tested

ChatGPT knows your product because you have already told it about the business in your projects and conversations. What it lacks is a tested SEO process, live data and a place to keep results. Tin adds all three over MCP, as open-source workflows.

Find it on GitHub
codex mcp add tin --url https://app.tin.computer/mcp

Connect Tin to ChatGPT

Tin is a remote MCP server. In ChatGPT's settings, add a custom connector, paste https://app.tin.computer/mcp and sign in when the browser opens. Every call is checked against your Tin project membership. If your plan has no custom connectors, the same projects run in the browser at app.tin.computer.

Find out where you stand

Start with the audit. It covers technical SEO and whether AI answers recommend you, and it changes nothing.

Decide what to write

ChatGPT writes the buyer context from what it knows about your product. Tin does the research inside the cost ceiling you set and turns it into a roadmap.

Write it and ship it as a pull request

Drafts follow your captured voice and wait for your review. Approved articles and technical fixes arrive as unmerged pull requests, which you review on GitHub like any other change.

Or run the whole loop

One workflow runs audit, keywords, plan and the first draft, with the same review points.

What every workflow here comes with

Battle tested on real products

These are the workflows we run for real companies. Claw Messenger went from about $45 to $2,105 in monthly revenue in 124 days on them. Each one has declared inputs, bounded execution and tests, and anything public waits for your review.

See the case study →

Open source: read it, fork it, self-host it

Apache 2.0. Every workflow is a folder in the repository: the steps it runs, the data it reads and what it is allowed to do. Change it, or run the whole system on your own machine.

Open the repo →

Runs on the agent that already knows your product

Tin connects to Claude Code, Codex or Cursor over MCP. That agent has your repository open and knows your product, customers and voice, so it fills the inputs and reviews the output. You never brief a new tool from zero.

All workflows →

Questions

How do I add Tin to ChatGPT?

Add Tin as a custom connector (a remote MCP server) in ChatGPT's settings with the URL https://app.tin.computer/mcp, then sign in. Custom connectors depend on your ChatGPT plan and may need developer mode. If you work in a terminal, the Codex guide has a one-line install.

Does this work with other agents?

Yes. Tin is an MCP server, so Claude Code, Codex, Claude, Cursor and any other agent that speaks MCP can run the same workflows on the same projects.

Will ChatGPT publish to my site on its own?

No. Content waits for your review, and changes to your site arrive as unmerged pull requests.

Is Tin really open source?

Yes. Tin is licensed under Apache 2.0 and the source is at github.com/tin-computer/tin. You can read every workflow, change it, and self-host the whole system.

Which coding agents can run Tin workflows?

Any agent that speaks MCP, including Claude Code, Codex and Cursor. There is also an API, and the same projects run in the browser at app.tin.computer.

Why run marketing from a coding agent?

Because it already knows your product. It has the repository open, so it fills workflow inputs accurately, reviews output against what the product really does, and can act on the results in the same session.

Add Tin to your coding agent

Run this once in your terminal. It connects Tin to your agent and opens the sign-in. Then ask your agent to grow your project.

Find it on GitHub
codex mcp add tin --url https://app.tin.computer/mcp