Features

Your Chomi content, inside the AI tools you already use

Connect Claude, ChatGPT, Cursor or any MCP client to your workspace, and pull briefs, interviews and approved pages straight into the work.

Get Chomi for your agency

Build the service page from the approved Chomi piece for this client.

Chomi MCP

The short answer

Chomi's MCP server connects your workspace to the AI assistants your team already works in. The assistant can read your clients, briefs, interviews and approved pages, and order new briefs, so nobody copies and pastes between tabs. It comes with every agency plan.

What your AI assistant can ask Chomi for

MCP, the Model Context Protocol, is the standard AI assistants use to reach tools outside the chat. Chomi speaks it, so an assistant you have connected can look things up in your workspace the same way it would search the web.

Almost all of it is reading. The one thing that spends anything is ordering a brief, which uses one from the month's allowance and still waits for a person to approve it. The assistant cannot approve, publish or change your content.

The ten things it can ask for

Ask for	What comes back
Your clients	Every client business in the workspace, so the assistant knows who it is working for.
A client's business profile	Services, audience, what sets them apart and their tone of voice.
Briefs	Every brief, newest first, filtered by client or status.
One brief in full	The plan for the page: headings, key points, FAQs, the answer box and the angles the interview covers.
Interviews	Which interviews have run and how far each one got.
One interview	The questions and answers in the expert's own words, plus the summary written from them.
The finished page	The approved content for a brief, as markdown, with its status and version.
A new brief	Orders one, from a topic. It spends a brief from the monthly allowance, and a person still approves it.
Usage	What the workspace has used this month and what the plan allows.
Page types	The kinds of page Chomi can plan and write, and what each is for.

Building websites with AI? Give it the real content

If you build sites with Cursor, Claude Code or another AI coding tool, this is where Chomi saves the most time. The assistant pulls the approved piece straight out of Chomi, headings, answer box, FAQs and all, and builds the page around it.

The wording that lands on the site is the wording the client approved, with nothing lost or retyped along the way, and the structure that makes a service page someone would hire from survives into the build.

Ask it to build the service page from the approved piece, lay out every FAQ as an accordion with its schema, keep the answer box word for word, or use the expert's line from the interview as the pull quote.

It is how the pages on chomi.io were built: written in Chomi, approved, then pulled into the site through this same connection.

A developer in glasses building a web page on her laptop with an AI coding assistant, working from approved content

MCP comes with every agency plan, alongside client switching and approval links.

Compare the agency plans

More ways agencies use it

Once Chomi sits inside the assistant, the questions an account manager asks ten times a day stop needing a login. The answers come back in the chat, already about the right client.

Interviews are the richest thing in the workspace. Pulled into an assistant, the expert's own answers become newsletters, social posts and sales notes that still sound like them, which is the first-hand expertise a reader can recognise, carried further than one page.

Ask it, without opening Chomi

Status: which briefs are waiting for a client's approval this week?
Repurposing: turn this interview into a LinkedIn post in the expert's own words.
Pitch prep: summarise what we know about this client before the call.
Planning: order briefs for the next three topics on the content plan.
Allowance: how many pieces are left this month across every client?

How to connect it

It takes four steps. Each key belongs to one workspace and can be revoked from the same page the moment it is no longer needed.

The assistant only ever sees the workspace the key was made in, and only what the brief, the interview and the approved piece already hold.

Step 1
Be on an agency plan
MCP comes with Freelance, Agency and Agency Scale. On a single-business plan the settings page explains it and links to the plans.
Step 2
Make a key in Settings
Under Connect an AI assistant. The key is shown once, so copy it then; Chomi only keeps a scrambled copy.
Step 3
Add Chomi to your AI tool
Paste the personal server address into Claude, ChatGPT, Cursor or any tool that takes an MCP server, or send the key as a bearer token.
Step 4
Ask in plain words
“What is waiting for approval for this client?” or “Build the page from the approved piece.” The assistant picks the right tool.

Questions people ask

Any tool that can connect to an MCP server, including Claude, ChatGPT and Cursor. Paste the personal server address from Settings, or send your key as a bearer token if the tool asks for one.

No. MCP comes with the agency plans: Freelance, Agency and Agency Scale. On a single-business plan the settings page explains it and links to the plans, and a key made earlier stops working.

No. It can read your clients, briefs, interviews and finished pages, and order a new brief. Approving, editing and publishing stay with the people in your workspace.

It uses one brief from your monthly allowance, exactly as ordering it in the app would. The brief still needs a person to approve it before the interview goes out.

Yes, and it is one of the best uses for it. A coding assistant can pull the approved piece, with its headings, answer box and FAQs, and build the page from it, so the client's approved wording reaches the site intact.

It is shown once when you make it and stored only as a scrambled copy, so nobody can read it back. Each key belongs to one workspace, and you can revoke it at any time.