Inblog

ai.inblogPublished by inblog.aiOfficial publisherv0.1.1Updated Oct 24, 2026

Run your company blog for SEO and AI search from your AI assistant.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Remote Inblog connector that lets an AI assistant run a company blog for SEO and AI search from the chat.

What you can do
  • Manage a company blog for SEO and AI search through the assistant.
  • No tool list is published, so the exact actions are not documented here; the connector is described only as running your blog from the assistant.
  • Expect blog content and publishing work to be handled through the Inblog platform rather than local files.
When to use it
Useful when a team already publishes on Inblog and wants an assistant to help run the company blog for SEO and AI search without switching tools.
Requirements
A remote streamable HTTP endpoint at inblog.ai; no packages or environment variables are declared. OAuth sign-in is required, so an Inblog account with access to the blog is needed.
Before you install
OAuth grants the assistant access to the connected Inblog workspace, and blog operations may create, edit or publish public content. Review what the assistant changes before it goes live. No tool list is published, so confirm the granted scopes and permissions before connecting.

Installation

In SourceWeft

  1. Open Inblog in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/ai.inblog%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "inblog": {
      "type": "http",
      "url": "https://inblog.ai/api/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

2
  1. v0.1.1LatestOct 13, 2026
  2. v0.1.0Sep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.