Troubleshooting

Common issues when connecting to or using the Mixpost MCP server, and how to fix them.

Symptom	Likely cause and fix
401 / "Unauthenticated"	The token is missing, mistyped, or expired. Check the Authorization: Bearer <token> header and generate a fresh token if needed.
The agent can't see a workspace	Its owner is not a member of that workspace. Add the user to the workspace, then ask the agent to list workspaces again.
"You do not have permission…" on create / update / delete	The token owner has the Viewer role. A Member or Admin role is required for write operations.
The client can't connect at all	The API access tokens feature may be disabled (MIXPOST_API_ACCESS_TOKENS=false), or the URL is wrong. Confirm the endpoint resolves to …/<MIXPOST_CORE_PATH>/mcp.
The client won't add an HTTP server	Some clients only support local (stdio) servers — connect through the mcp-remote bridge shown in Connect your client.