TUNC.AI / Tunc SRC examples

Tunc SRC examples and agent setup prompts

Three working setups for Tunc SRC, each with a prompt your agent follows: a version after each change, picking up a project, and going back a version.

Updated

Each setup below starts with a prompt you paste to your agent, so the agent does the work. Keep API keys out of prompts: give them to your tools as environment variables or secrets. The Tunc SRC docs have every call; this page has setups that work.

Let your agent connect to Tunc SRC

In Claude, the quickest way is a prefilled link. It opens Add custom connector with the name and URL filled in; check them and confirm.

Add Tunc SRC to ClaudeClaude’s Free plan allows one custom connector. On Team and Enterprise an Owner adds it.

In Claude Code, Cursor or any agent that can run commands or change its own settings, paste this. It adds the connection, waits while you sign in, then tests it:

Paste this to your agent
Connect Tunc SRC to this session. Its MCP server is https://mcp.tuncsrc.com/mcp. If you can run commands, run: claude mcp add --transport http tunc-src https://mcp.tuncsrc.com/mcp. Otherwise add it to my MCP settings. Then tell me to sign in (in Claude Code: run /mcp, choose tunc-src, then Authenticate) and wait for me to confirm. After that, test it: create a project named connection-test, save one file hello.txt that says "it works" with the sentence "Connection test.", read the file back, then delete the project. Tell me what you did and what came back.

In ChatGPT, or any app where you add connectors through menus, ask the agent to read the instructions and walk you through them:

Paste this to your agent
Read https://tuncsrc.com/llms.txt and tell me, menu by menu, how to connect Tunc SRC to this app. Use the sign-in option, not an API key. If this app needs a special mode to add connectors, tell me which.

An agent can add the connection but cannot sign in for you: you approve it once in your browser and choose what it may do. The same steps for every client, if you would rather do it by hand:

ClientSteps
claude.ai, Claude Desktop and Claude mobileCustomize → Connectors → Add custom connector → name Tunc SRC, URL https://mcp.tuncsrc.com/mcp → Add → Connect. The Free plan allows one custom connector; on Team and Enterprise an Owner adds it under Organization settings → Connectors. This link opens the dialog with the name and URL filled in:
https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=Tunc%20SRC&connectorUrl=https%3A%2F%2Fmcp.tuncsrc.com%2Fmcp
Claude CodeAdd the server, then run /mcp, choose tunc-src and Authenticate.
claude mcp add --transport http tunc-src https://mcp.tuncsrc.com/mcp
ChatGPTSettings → Apps & Connectors → Advanced → turn on Developer mode → Create → name Tunc SRC, URL https://mcp.tuncsrc.com/mcp, Authentication OAuth → Create → Connect.
CursorAdd it to ~/.cursor/mcp.json, then Settings → MCP: it shows “Needs login” → Login.
{
  "mcpServers": {
    "tunc-src": {
      "url": "https://mcp.tuncsrc.com/mcp"
    }
  }
}
VS Code (Copilot)Command Palette → MCP: Add Server → HTTP → https://mcp.tuncsrc.com/mcp → name tunc-src → allow the sign-in prompt.
Gemini CLIAdd it to settings.json, then run /mcp auth tunc-src.
{
  "mcpServers": {
    "tunc-src": {
      "httpUrl": "https://mcp.tuncsrc.com/mcp"
    }
  }
}
Copilot StudioTools → Add a tool → New tool → Model Context Protocol → URL https://mcp.tuncsrc.com/mcp → Authentication OAuth 2.0, Dynamic discovery.

Keep a website in Tunc SRC and save a version after each change

The job: an assistant is building a website (or any set of files) with you over many chats, and you want every change kept so nothing is lost. The setup: ask your agent to create a project in Tunc SRC and save a version after each change.

Paste this to your agent
Create a Tunc SRC project named my-site with src_repo (operation "create"). Save the website files we have so far with src_write: each file in changes with its path and content, and a summary that says in one plain sentence what this version is. From now on, after every change I approve, save a new version with src_write, passing the latest version as if_version, and tell me the sentence you saved it with.

Every save is one version with one sentence. If a save is refused with version_conflict, someone saved in between: the agent reads the project again and redoes its change.

Pick up a project another assistant left

The job: one assistant worked on a project yesterday, and today you are in a different app or a new chat. The setup: the new assistant reads the project and its versions from Tunc SRC, so it starts from what was actually saved.

Paste this to your agent
List my Tunc SRC projects with src_repo (operation "list"). For the project my-site, list the latest versions with src_read (operation "versions") and tell me who saved each one, when, and its sentence. Then show me what the newest version changed with src_read (operation "changes", with version set to that version), and read the top folder with src_read (operation "folder") so you know what the project holds.
Paste this to your agent
Check with src_events what happened in my-site since we last looked, and keep the next value so you can ask again from there.

The list of versions says who saved what and when; src_events is a feed that can be followed. It does not wake an agent: the agent asks.

The last change broke it: go back one version

The job: the newest change broke the site and you want the previous version back. The setup: the agent lists the versions and restores the one before, which is saved as a new version, so the broken version is still there to look at.

Paste this to your agent
In the Tunc SRC project my-site, list the versions with src_read (operation "versions") and show me the newest two with their sentences. Then bring back the version before the newest one with src_write: pass that version as restore, the newest version as if_version, and the summary "Go back to the version before the change that broke the site." Tell me the new version when it is saved.

Restoring never removes anything: the earlier version’s files are saved as a new version on top of the others.

The same project, with git too

The tools are how agents use Tunc SRC. If you use git as well, the regular git program works with the same project: a push and a save from a tool land in the same history. There is nothing to install from Tunc.

Paste this to your agent
Describe my Tunc SRC project my-site with src_repo (operation "describe") and give me the address the git program uses, so I can clone it. Do not print any API key.

Good to know

  • One save holds up to 1000 file changes and a sentence of up to 500 characters. One file can be up to 100 MiB through a tool, src_read does not return a file over 2 MiB whole, and a tool request to the Tunc SRC hosts is at most 12 MiB.
  • Every save names the version it started from (if_version). A stale one is refused with version_conflict, so two agents cannot silently overwrite each other.
  • A project kept in a workspace is shared with that workspace’s members; a project kept without one is your own.
  • Deleting a project removes all its versions and cannot be undone. Ask an assistant to delete only when you want that.
  • Your account page at https://tunchub.com/account shows your storage and connected agents.