Tin MCP server

Tin

Open-source marketing system, designed for coding agents.

Why would you invent marketing from first principles when you can use a battle-tested marketing stack in 10 minutes?

Now with 26+ reliable workflows you can use right away.

Website · Try it in the browser

Quick Start

Connect from a coding agent

The hosted dashboard, API and MCP service use app.tin.computer. Add the MCP connection from your project directory.

Claude Code:

claude mcp add --transport http tin https://app.tin.computer/mcp

Then open Claude Code and use /mcp to authenticate Tin.

Codex:

codex mcp add tin --url https://app.tin.computer/mcp

Complete the browser login when prompted. For an existing connection that needs authentication, use codex mcp login tin.

Cursor, in .cursor/mcp.json:

{ "mcpServers": { "tin": { "url": "https://app.tin.computer/mcp" } } }

Use Cursor's MCP controls to connect and complete authentication.

Start a new agent session if Tin's tools have not appeared. To check the connection, ask it to call list_projects. Your agent can also delete a project you created when you ask it to; it confirms the exact name first, and billing history stays. Then ask:

Use Tin to grow my project like a pro!

A whole agentic marketing system, not a bunch of skills

• Work that continues between sessions. Save a workflow with its inputs and a schedule. Tin handles its timers, retries, and waits for your approval.
• Context that carries forward. Reports, research, and a project wiki live in a git repository. Later runs don't start from scratch.
• Workflows you can inspect. The catalog covers organic growth, content, outreach, product QA, and creative work. Each definition states what it needs, what it produces, and whether it needs review.
• Review before delivery. Read an article, request changes, or approve a campaign. GitHub delivery opens a pull request for you to merge.
• One project across your tools. Your coding agent and the browser share the same files, run history, and decisions, with the same project permissions.
• Workflow evaluation, coming. Each template gets an eval set and a blind second reader, so the workflows get sharper week after week.
• Growth experiment tracking, coming. Every change becomes an experiment with a before, an after, and a verdict.

Use the agent that already knows your project

Connect Tin over MCP in Claude Code, Codex, or Cursor. Your agent can read your local repository, ask you about the business, and use Tin's onboarding workflow to prepare a plan.

It starts with practical questions: what are you trying to achieve, how much time and budget can you put into it, and what should it avoid? The plan uses that context alongside the workflows and integrations available to your project.

For example, the setup conversation might look like this:

› Use Tin to grow my project like a pro!

I'll read the repository first, then help you choose a starting plan.

If organic growth is the priority, we can audit the site, research
buyer questions, and turn the findings into a content plan.
Search Console can add evidence from your current search traffic.
GitHub lets Tin propose site changes as pull requests.

What would a useful result look like in the next sixty days,
and how much time can you spend reviewing work each week?

You choose the plan and allow the connections it needs. After approval, Tin creates the selected configurations and starts the initial work it can run. It reports what was set up and what is still blocked.

From a useful prompt to work you can rely on

A good skill tells an agent how to do something. Running that skill every week adds other problems: which version should it use, where does its context come from, what happens after a failure, and who approves the result?

Shortened. The full README is on GitHub.