Claude Code for SEO, with workflows that are already tested
Claude Code knows your product because it has your repository open. 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.
claude mcp add --transport http tin https://app.tin.computer/mcpWhy prompts and skills alone fall short
An SEO skill file gives Claude instructions. It does not give it keyword data, a crawler, a spend cap, a review step or memory between sessions. Tin workflows are bounded jobs with declared inputs and outputs, so each run is repeatable and the result is saved to your project.
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
Claude 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 Claude can review against your conventions.
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 Claude Code?
Run: claude mcp add --transport http tin https://app.tin.computer/mcp. It connects Tin and opens the sign-in. Then ask Claude to grow your project.
Does this work with other agents?
Yes. Tin is an MCP server, so Codex, Claude, ChatGPT, Cursor and any other agent that speaks MCP can run the same workflows on the same projects.
Will Claude 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.