Connect Claude, Cursor, or another AI tool to Prusa's help articles, blog posts, and product info — so it can answer using real, up-to-date content instead of guessing. You sign in with your @prusa3d.cz Google account — no API tokens to manage.
"How do I clear a filament jam on the MK4S?"
"What's the official product name for our toolchanger printer?"
"What have we published on the blog about MMU3?"
"Is the MK4S setup guide available in Czech?"
Pick your tool below and follow the steps. Each one authenticates the same way: your browser opens a Google login and you sign in with your @prusa3d.cz account. No tokens, no keys to paste.
https://content-base-search-api.prusa3d.com/mcp@prusa3d.cz account.Run this once in your terminal (outside Claude Code):
MCP_CLIENT_SECRET="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" claude mcp add-json content-base '{"type":"http","url":"https://content-base-search-api.prusa3d.com/mcp","oauth":{"clientId":"187254738331-7k7mtaoubrkem1ius0bln7rgtpuc8u6k.apps.googleusercontent.com","callbackPort":29352,"scopes":"openid email profile"}}' --client-secret
Then restart Claude Code, type /mcp, select Authenticate, and sign in with your @prusa3d.cz account.
.cursor/mcp.json in your project root (or ~/.cursor/mcp.json for global).content-base server.@prusa3d.cz account.{
"mcpServers": {
"content-base": {
"url": "https://content-base-search-api.prusa3d.com/mcp"
}
}
}
Requires VS Code 1.101+ with GitHub Copilot.
.vscode/mcp.json in your project root.@prusa3d.cz account in the popup.{
"servers": {
"content-base": {
"url": "https://content-base-search-api.prusa3d.com/mcp"
}
}
}
Any MCP client that supports remote HTTP servers works. Point it at the server URL:
https://content-base-search-api.prusa3d.com/mcp
The server supports OAuth discovery via /.well-known/oauth-protected-resource — compliant clients handle the login flow automatically.
Replace the URL in any config above with the staging endpoint:
https://content-base-search-api-test.prusa3d.dev/mcp
For Claude Code staging, use a different server name (content-base-staging):
MCP_CLIENT_SECRET="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" claude mcp add-json content-base-staging '{"type":"http","url":"https://content-base-search-api-test.prusa3d.dev/mcp","oauth":{"clientId":"187254738331-7k7mtaoubrkem1ius0bln7rgtpuc8u6k.apps.googleusercontent.com","callbackPort":29352,"scopes":"openid email profile"}}' --client-secret
five new abilities — your AI picks the right one automatically based on what you ask:
hybrid_search
get_documents
get_metadata
get_multilingual_content
get_content_overview
@prusa3d.cz account.
MCP_CLIENT_SECRET=… prefix and the trailing --client-secret flag both need to be present.
invalid_scope, make sure the scopes are exactly openid email profile. For redirect_uri_mismatch, ask a team admin to add your redirect URI to the Google OAuth client.