Inblog for AI agents
Inblog is an AI-powered blogging platform for managing posts, authors, tags, and analytics on a company blog. Product and engineering teams use it as a building block inside their own AI features. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in Inblog.
Publish a new blog post
Publish a drafted post to the company blog with the right tags and author.
Check post analytics
Pull analytics on a published post to see how it is performing this month.
Update a redirect with approval
Update a URL redirect only after the content team confirms the old link should point elsewhere.
10 Inblog actions, graded by risk.
Every Inblog action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
5Look things up. Allowed by default.
- inblog.get_blogGet Blog
- inblog.list_tagsList Tags
- inblog.list_postsList Posts
- inblog.get_analyticsGet Analytics
- inblog.list_redirectsList Redirects
write
5Create and change things. Allow, or ask the user first.
- inblog.create_postCreate Post
- inblog.update_postUpdate Post
- inblog.upsert_tagCreate or Update Tag
- inblog.upsert_redirectCreate or Update Redirect
- inblog.set_post_publicationSet Post Publication
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
Inblog in three steps.
- 01Your users connect InblogThey add their Inblog api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “create Post” can wait for the user to approve.
- 03Any agent can actYour agent calls Inblog through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('inblog', { read: 'allow', write: 'ask', // create_post destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Inblog connects.
Users add their Inblog api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
The same Inblog connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Inblog from any agent.
Inblog and Arc0, answered.
Can I use Inblog with Claude, ChatGPT or Cursor?
Yes. Connect Inblog to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Inblog actions you allow.
How do users connect Inblog?
Users add their Inblog api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
Which Inblog actions can my agent take?
10 in total: 5 read, 5 write and 0 destructive, such as “create Post”. Your policies decide which of them each agent may call.
Can I make my agent read-only in Inblog?
Yes. Allow read actions and deny writes in the Inblog policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call Inblog too?
Yes. The same Inblog connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Inblog into your agent.
Your users connect Inblog once, under your brand. Your agent gets 10 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan