Context7
by upstash
Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.
Computer or cloud★ 64,224MITUpdated today
Install
BlogFactory
Overview
Description from the maker (original English)
Agent control plane for multi-site content ops: research, drafts, review, CMS draft delivery.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi3 of 3 passedChecked from public information; code not scanned yet
- UsageiNot measured yet★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs in the cloud
- Transport: Streamable HTTP
- Category: Search & AI memory
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 3 of 3 passed
- Runs on the maker’s server: what you ask it goes through their server.
- The registry lists no key to fill in.
You need
- Runs in the cloudNothing to install; it connects over the internet
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
- Open Settings → Connectors
- Press Add custom connector
- Paste the address below and press Add
- If it asks you to sign in, sign in with the maker
https://blogfactory.io/mcpRun this in your terminal
claude mcp add --transport http blogfactory https://blogfactory.io/mcpOr copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"blogfactory": {
"url": "https://blogfactory.io/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"blogfactory": {
"type": "http",
"url": "https://blogfactory.io/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
- Open ChatGPT on the web → Settings → Connectors (Apps)
- Press Create or Add (some plans need Developer mode under Advanced first)
- Paste the address below, give it a name and save
- If it asks you to sign in, sign in with the maker
https://blogfactory.io/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
The server asks you to sign in before it lists its tools.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified against the domain blogfactory.io (the registry checks domain ownership)
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- ✓ Pass
Endpoint responds
Responded in 645 ms (HTTP 401)
- ✓ Pass
Sign-in with OAuth
Declares OAuth sign-in, so your AI app can take you to log in
- … Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint
Compared with others in Search & AI memoryi
- More stars than 0% of the other 7243 servers in this category
- Published to the registry more recently than 94% of the other 7243 servers in this category
- Basic checks equal to or better than 100% of the other 7243 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is BlogFactory safe?
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
Is it still maintained?
The GitHub repo last changed –, and the latest version (0.5.1) reached the registry 2 days ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
What can I use instead?
In the same category: Context7, Codebase Memory, Exa
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Codebase Memory
by DeusData
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Runs on your computer★ 48,148MITUpdated 20 days ago
Install
Exa
by exa-labs
Connect AI agents to Exa for web search, content fetching, and multi-step research.
Runs in the cloud★ 5,213MITUpdated last month
Install
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
BlogFactory
The draft-only agent control plane for multi-site content operations.
Give agents useful authority through MCP. Keep people in control of review, approval, and CMS delivery.
Website · Self-host · MCP guide · Cloud billing · Release plan · AGPL-3.0-only
Self-hosted Bring your own AI Site-scoped access Never publishes live
A calmer content operation
BlogFactory keeps the operating context around AI-assisted content work in one place: source evidence, drafts, revisions, SEO metadata, review, preflight, delivery destination, and a sanitized operation record.
source evidence→ agent work or caller-authored draft → revision + SEO metadata → human review + preflight → selected CMS destination as a draft
Agents do the work through MCP. The web app is where operators see what needs attention, resolve blockers, review the current version, and approve a CMS handoff. The server-enforced authority ceiling is intentionally narrow: no live publishing, deletes, credential access, arbitrary providers, or admin tools through MCP.
Product captures
Search Growth turns evidence into reviewed action
Connect Search Console context, distinguish complete from preliminary data, rank work, plan it by date, and create a draft only when an operator is ready. Observation windows are shown as correlated signals, never as ranking guarantees.
MCP has useful authority and hard boundaries
Each connection is site-scoped. Clients discover the active catalog from the server, while provider credentials stay outside the agent conversation. The Review Card brings current revision context, warnings, destination selection, and explicit draft confirmation into compatible MCP clients.
Product captures from blogfactory.io . Values belong to the captured workspace; the tool catalog is discovered live.
What ships in v0.1.0
| Operate | Grow | Control | Deliver |
|---|---|---|---|
| Sources, content inventory, revisions, review queue, runs, and image workflows | Search Console diagnostics, optimization, growth plans, indexing, and internal links | Site-scoped access, MCP connections, integrations, brand voice, settings, usage, and audit history | Preflight, explicit destination selection, optimistic locking, idempotent CMS draft delivery |
Self-host BlogFactory for free. BlogFactory Cloud is the managed service operated from the private BlogFactoryHQ/blogfactory-cloud repository; its pricing, subscriptions, checkout, and entitlement code is not part of this open-source core and never gates self-hosted instances. Read the release plan for the distribution roadmap.
Companion projects
Explore both projects in the Free & Open Source Tools hub.
| Project | Use it when |
|---|---|
| Ghost Publisher MCP | You need a local, Ghost-specific MCP server for drafts, diagnostics, scheduling, and separately approved publishing. Overview and install |
| Source-Backed Blog Writer | You need a portable Agent Skill for researching, drafting, refreshing, or auditing evidence-backed articles. Overview and install |
Both projects work independently. They can supply or deliver content around BlogFactory, but they do not broaden BlogFactory's server-enforced draft-only authority.
Start locally
BlogFactory uses npm workspaces: a React/Vite web app and a Hono/TypeScript API, backed by PostgreSQL and S3-compatible storage.
git clone https://github.com/BlogFactoryHQ/blogfactory.gitcd blogfactory npm install cp .env.example .env npm run db:migrate npm run dev
The web app runs on http://localhost:8080 and the API on http://localhost:3000. Add only the credentials required for the flow you are testing; never point PostgreSQL integration tests at a shared production database.
Self-host with Docker
git clone https://github.com/BlogFactoryHQ/blogfactory.gitcd blogfactory cp .env.self-host.example .env
Fill every required value and set ADMIN_EMAILS.
docker compose build --pull api web docker compose up -d
The verified topology includes the web app, API, PostgreSQL, MinIO, migrations, persistent volumes, and the bounded scheduler. Follow the full self-hosting guide before exposing an instance to the internet.
Hosted production
The managed service uses Cloudflare in front of an immutable Docker Compose deployment on Hetzner in Nuremberg. PostgreSQL 18, the Bun/Hono API, the persistent worker, the backup scheduler, and the web app run in that stack; private EU Cloudflare R2 stores images and age-encrypted database backups. GitHub Actions builds immutable images in GHCR; Vercel retains the last clean deployment as a DNS rollback target rather than serving current production traffic.
This hosted topology and the Cloud-only billing/authentication overlay are maintained in the private BlogFactoryHQ/blogfactory-cloud repository. Shared product changes originate in this public core and sync one way into Cloud; the hosted topology does not change the community self-host contract above.
How the system is shaped
operators ── <instance-origin> ─────┐├─ shared tenant-scoped services ─ PostgreSQL + S3-compatible storage agents ───── /mcp ─┘ └─ CMS drafts / Search Console / configured AI providers
Web and MCP are transports over the same services. Queue classification, revision rules, review preflight, Search Console reads, permissions, and CMS draft delivery are not duplicated in the UI or agent tools.
| Surface | Purpose |
|---|---|
| Marketing | Open-source product overview and Cloud launch updates |
| Authenticated app | Operations, review, growth, settings, and audit |
https://blogfactory.io/mcp | Streamable HTTP agent work layer |
/.well-known/oauth-protected-resource | MCP protected-resource discovery |
Documentation
- Architecture and service ownership
- MCP, OAuth, tool catalog, and Review Card
- Operations, deployment, and production acceptance
- Cloud billing, entitlements, and Managed AI
- Self-hosting with Docker Compose
- Release plan and Cloud boundaries
- Documentation index
- Contributing
Development checks
npm run typechecknpm run lint --workspace=web npm run test --workspace=web npm run test:server npm run build git diff --check
Database, tenancy, ledger, and shared control-plane changes also require npm run test:postgres against a disposable database.
BlogFactory is licensed under AGPL-3.0-only.