Pressbotics
Sign inStart free
Docs

Any MCP client

One URL, OAuth, no key — the shape that works everywhere.

Pressbotics does not ship a per-client integration. It is a standard remote MCP server, so anything that speaks the protocol over HTTPS can use it.

What you need

  • The server URL: https://mcp.pressbotics.com/mcp
  • A client that supports remote MCP servers (not only local stdio ones).
  • A browser, once, to complete the OAuth authorization.
https://mcp.pressbotics.com/mcp

The steps

  1. 1Open your client's settings and find where custom MCP servers (sometimes called connectors, integrations or tools) are added.
  2. 2Add a server with the URL https://mcp.pressbotics.com/mcp.
  3. 3Leave any API key or token field blank — Pressbotics uses OAuth.
  4. 4Connect. The client opens Pressbotics in your browser.
  5. 5Sign in and click Authorize. The client now lists the Pressbotics tools.

Menu names and their nesting change between clients and between versions of the same client. The shape above is stable; the exact wording on your screen may not be. If you cannot find the setting, search your client's own documentation for "MCP server".

Verifying

Call list_sites. Then get_site_context for the site you intend to publish to — that returns the handle, the approval policy, existing categories and tags, brand voice notes and whether SEO fields are writable. An agent that reads context first makes far fewer wrong calls.

If OAuth is impossible

Some self-hosted and headless agents cannot run an interactive browser flow at all. Those use a static agent key instead — see Agent keys.