Tunc Orb examples and agent setup prompts

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 Orb docs have every call; this page has setups that work.

Let your agent connect to Tunc Orb

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 Orb 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:

Connect Tunc Orb to this session. Its MCP server is https://mcp.tuncorb.com/mcp. If you can run commands, run: claude mcp add --transport http tunc-orb https://mcp.tuncorb.com/mcp. Otherwise add it to my MCP settings. Then tell me to sign in (in Claude Code: run /mcp, choose tunc-orb, then Authenticate) and wait for me to confirm. After that, test it: save a record named test/hello with the description "connection test" and the text "it works", read it back, then delete it. 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:

Read https://tuncorb.com/llms.txt and tell me, menu by menu, how to connect Tunc Orb 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:

https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=Tunc%20Orb&connectorUrl=https%3A%2F%2Fmcp.tuncorb.com%2Fmcp

claude mcp add --transport http tunc-orb https://mcp.tuncorb.com/mcp

{
  "mcpServers": {
    "tunc-orb": {
      "url": "https://mcp.tuncorb.com/mcp"
    }
  }
}

{
  "mcpServers": {
    "tunc-orb": {
      "httpUrl": "https://mcp.tuncorb.com/mcp"
    }
  }
}

Share one project brief across Claude, Cursor and ChatGPT

The job: you work on one project in several assistants and keep pasting the same background into each. The setup: one record holds the brief and one log holds the decisions. Every assistant connected to your Tunc Orb can read both.

Set it up once. Paste this into the assistant that knows the project best, with your own project name:

Set up project memory for "Acme website redesign" in Tunc Orb. Ask me for anything you do not know. Save a record named projects/acme-redesign/brief with the goal, who it is for, the current status, open questions and where the files live, and give it the one-line description "Acme redesign: brief and status". Keep it under 300 words and leave the decision history out of it. Then start a log named projects/acme-redesign/decisions, with the description "Acme redesign: decisions and why", by adding each decision so far as an entry with its date and the reason. Show me both names when you are done.

Pick it up in a different assistant, or in a new chat:

Check Tunc Orb for projects/acme-redesign/brief and the five newest entries in projects/acme-redesign/decisions, then tell me where we left off before you start.

At the end of a work session:

Update projects/acme-redesign/brief with the new status and open questions, and add one entry to projects/acme-redesign/decisions for each choice we made today, with the reason. Keep the brief under 300 words.

Tunc Orb checks the revision before it changes a record, so two assistants cannot silently overwrite each other: the second one reads again and retries. To make an assistant look without being asked, add one line to its standing instructions (Claude project instructions, CLAUDE.md or Cursor rules): "At the start of a session on the Acme redesign, read Tunc Orb projects/acme-redesign/brief."

Report from a scheduled job to a log your assistants can read

The job: a weekly check, a nightly import or an n8n workflow produces a result that nobody reads until something breaks. The setup: the job appends one entry to a log, and you ask any assistant what the last runs said. Tunc Orb stores the entries; it does not wake an agent or send a message.

Create an API key with only the access the job needs (read and save in Tunc Orb) at https://tunchub.com/account/keys/new?product=orb, and give it to the job as an environment variable or a secret. Then paste this to your coding agent:

Write a script, report.py, that runs my weekly traffic check and then appends one entry to the Tunc Orb log runs/weekly-traffic through the REST API at https://api.tuncorb.com/v1/write (operation append). Each entry: the date, ok or failed, the key numbers, and a link if there is one. The first entry creates the log; give it the description "Weekly traffic check results". Read the API key from the environment variable TUNC_API_KEY and never print it. Send a new mutation_id for each entry and reuse the same one if you retry. Use https://tuncorb.com/docs for the request shapes.

Later, in any connected assistant:

Read the five newest entries of the Tunc Orb log runs/weekly-traffic (one entry per run: date, ok or failed, key numbers). Did any run fail, and did the numbers move by more than 10% from the run before?

Handle every item once, even with several agents

The job: an agent triages tickets, emails or leads, and you cannot afford to handle one twice or lose your place when the chat ends. The setup: one record holds the ids already handled. Each agent reads it first, skips what is listed, and adds ids with a patch that names the revision it read. If another agent changed the record in the meantime, the change is refused with revision_conflict and the agent reads again.

You triage new support tickets from the helpdesk tools you have. First read the Tunc Orb record triage/support/processed; if it does not exist, create it with the one-line description "Ticket ids already handled" and the value {"ids": []}. Skip every ticket whose id is in that list. After you reply to or close a ticket, add its id with a patch (add /ids/-) at the revision you read. If Tunc Orb answers revision_conflict, read the record again, check whether the id is now listed, and add it only if it is not. Never delete the record. At the end, tell me how many tickets you handled and how many you skipped.

The same pattern fits an inbox, a lead list, a folder of files to convert or a queue of pages to check. Because the state lives in Tunc Orb and not in a chat, a new session or a different assistant carries on from the same list. The record is read whole each time, so for a busy queue start a new one each month, for example triage/support/processed-2026-10.

Keep a file’s id next to your notes

Tunc Art keeps the files your assistants make. Keep a file’s artifact_id in a Tunc Orb record and any assistant can open the file later: the id opens it, while the link is only for people. This needs both connected.

Save this report to Tunc Art as 2026-10-weekly-report.pdf. Then update the Tunc Orb record reports/latest with the file’s artifact_id, its name, when it expires and today’s date, and give me the link.

Good to know

• Records and logs stay until you delete them. A record holds up to 16 MiB, and one call sends at most 64 KiB, so a long record grows by patches.
• Names and one-line descriptions are stored unencrypted so agents can find records. Keep secrets out of them.
• A free account has one shelf, shared by all your connected agents, and every agent can read every record in it.
• Working for several clients? Every agent connected to a Tunc account can read all of its shelves, and an account has one organization. Use one Tunc account per client, and connect each client’s agents to their own account.