Claude MCP
Connect Contengi to Claude and every agent, brand rule and data source comes with it. Ask in plain English, Claude does the work, and the results land in your library ready to review.
Request beta accessWhat Claude can do
Claude reads your knowledge base, tone of voice and hard rules first, then runs the same quality pass the app uses before anything is saved.
It searches the web, reads pages, and pulls your Search Console and GA4 numbers, so ideas start from what is already working.
Blogs, LinkedIn posts, newsletters, press releases, YouTube packages and notes land in your library word for word, ready to review.
Claude rewrites one section at a time, checks every link, and shows you a diff you can revert. The changes appear in the Contengi editor as they happen.
Build and run playbooks and workflows, approve the steps waiting on you, and kick off automations, all from the chat.
Finished articles go to your website on request. Edits to a live post stay in Contengi until you publish them.
"Turn yesterday's sales call transcript into a newsletter issue in our voice."
"Which posts lost clicks last month? Refresh the worst one section by section and show me the diff."
"Check every link in our pricing guide and remove the dead ones."
"Build a workflow that turns each new blog into three LinkedIn posts and waits for my approval."
When you research, write and edit through the connector, the reasoning runs on your own Claude plan with the model you pick. Contengi supplies the brand context, the rules and the tools, so the output meets the same standard as the app without touching your Anthropic API key.
Jobs that run inside Contengi, like a playbook, a workflow run or a full article refresh, still use your workspace's Anthropic key, the same as they do in the app.
FAQ
An MCP connector that plugs Contengi into Claude. Once connected, Claude can read your brand knowledge base, research with your Search Console and GA4 data, write and edit content that saves straight into Contengi, and run your playbooks and workflows, all from a normal chat.
Claude on the web and desktop through custom connectors, and Claude Code. Custom connectors need a Claude plan that supports them.
Research, drafting and editing through the connector run on your Claude subscription, with the model you choose. Jobs that run inside Contengi, like playbooks, workflow runs and full article refreshes, use your workspace's Anthropic API key, the same as in the app.
Everything Claude writes is saved as a draft, and edits to a live article stay inside Contengi until you publish. Contengi instructs Claude never to publish unless you ask it to.
No. MCP is the open standard Claude uses to connect to other apps. You paste one URL and sign in, and Contengi handles the rest.
Keep exploring