API and MCP Authentication
Choose granular API key permissions for automation, or connect the MCP server with OAuth that inherits your existing Inblog role.
Inblog has two different authentication models. Choose the one that matches how you work.
API keys for automation
Use an API key with the REST API, CLI, or AI Skills when you are running a script, integration, or coding workflow. Create it in Dashboard → Settings → API Keys.
Each API key has granular API permissions. Select only the permissions that the automation needs, such as posts:read or posts:write, and keep the key secret. The required API-key permissions for every operation are listed in the OpenAPI document.
MCP OAuth for a signed-in user
Use the MCP server when a person connects Inblog to Claude or ChatGPT at https://inblog.ai/api/mcp. The person signs in to Inblog and approves the connection through OAuth.
MCP OAuth inherits the signed-in user's existing Inblog role and access. It does not use API-key permission labels such as posts:read as OAuth scopes, and it cannot narrow the connector to a custom list of those labels. The connector can access every blog that the signed-in account can access, subject to that account's normal role permissions.
If a person should have less connector access, change their Inblog role or remove their blog access before they connect. Disconnecting the connector stops future MCP access.
Choose the right model
| Use case | Authentication |
|---|---|
| Scheduled job, CI workflow, terminal command, or coding assistant skill | API key with the minimum API permissions |
| Claude or ChatGPT conversation run by a signed-in team member | MCP OAuth with that member's existing role and blog access |
Related links
Last updated 2026-08-24