Skip to main content
Galinum runs a hosted MCP server, so any MCP-compatible agent can create, target, launch, and measure product communications without you writing an integration. It exposes the same management API the skill uses, with the same authorization and the same lifecycle rules.

​
Skill or MCP?

Both drive the same API, and you can use either one. Install the skill when your agent supports skills: it carries the full routing and authority guidance inline. Use MCP when your client speaks MCP but has no skill mechanism.
If you enable both in the same agent, it sees two ways to do the same thing: the skill’s instructions and the MCP tools. That is safe but noisy. Prefer one per agent.

​
Endpoints

The full endpoint supports OAuth and project-secret bearer authentication. The read-only endpoint keeps project-secret authentication only. The subdomain root is not an MCP endpoint. Always include /mcp in the full endpoint URL. https://galinum.com/mcp is retired and returns 404. Galinum does not redirect it or expose another full-endpoint alias.
/mcp/readonly limits the MCP tool list only. Your project secret still authorizes the REST API and the full MCP endpoint. It is a guardrail against an agent writing by accident, not a restricted credential. To limit what a credential can do, do not share the secret.

​
Connect with OAuth

OAuth keeps the project secret out of your client configuration. Galinum asks you to sign in, choose one project, and approve the exact MCP read and write scopes. The grant lasts eight hours. You can revoke it immediately from Settings → Projects.
The login command opens the browser. Sign in, select the project, review the scopes, and approve the grant.

​
Connect with a project secret

Use a project secret when your client cannot complete OAuth, or when you need the read-only endpoint. Find the secret under Settings → Projects. Send it as Authorization: Bearer pk_your_secret.
~/.codex/config.toml

​
Keep credentials safe

An OAuth grant or project secret can create and launch campaigns for real users. Treat both as production credentials:
  • Store it in your client’s secret input or your OS keychain, never in a committed file.
  • Use a per-environment project so a development agent cannot reach production users.
  • Rotate a project secret in the dashboard if it leaks.
  • Revoke an OAuth grant under Settings → Projects when a client no longer needs access.

​
How your agent should use it

The server sends instructions with every connection, so a well-behaved client follows them without extra prompting. Direct by default. A communication is one message. Your agent should not add a goal, variants, or a delivery window unless you asked to measure an outcome or run an A/B test. Launch needs your say-so. “Draft” and “prepare” stop at draft. Only an explicit “launch”, “send”, or “announce” starts delivery. If that is ambiguous, your agent should stop at draft and ask. Pagination is exact. Tools that page use REST page and perPage and return pageCount unchanged. Your agent reads every campaign page through pageCount before treating a filtered result as complete. Errors are actionable. A failed call returns readable text explaining what to do next: a lifecycle conflict asks the agent to read the campaign back, a rate limit reports how long to wait, and an uncertain campaign creation tells the agent never to retry.

​
Inspect deployment activation

Use get_launch_policy and get_campaign_activation to inspect the project default, campaign override, approval, mapping coverage, launch evidence, and warnings. The full endpoint also exposes set_launch_policy and set_campaign_activation_mode with revision preconditions. Enabling automatic mode can activate existing approved drafts. A null override inherits the project default. The underlying activation operations are also supported by self-hosted servers. These tools never approve communications or configure deployment scope. Stock operator HTTP is separate from agent MCP. See GitHub integration for setup, manual fallback, and rollback behavior.

​
Revise an unlaunched campaign

Connect your agent to the full MCP endpoint and authenticate for the campaign’s project. Copy the campaign ID from its dashboard detail page. Replace the placeholders in this prompt:
Your agent reads the campaign with get_campaign and applies the requested revision with update_campaign. Refresh the dashboard to review the saved content. Approval survives revisions. An approved automatic campaign can become eligible to launch when its current changes are deployed. To keep it unlaunched, select manual mode before requesting the revision.

​
Images

MCP cannot carry a file upload, so upload_campaign_media takes the image as strict base64 in data, with contentType set to image/png, image/jpeg, image/webp, or image/gif. Over MCP the image must be at most 3 MiB decoded. For anything larger, upload through the REST endpoint POST /api/v1/campaign-media and reference the returned URL.

​
Compatibility

The server supports MCP revision 2026-07-28 only, over Streamable HTTP with JSON responses. An older client receives a clear unsupported-version error naming the revision we serve. Update your client rather than downgrading. It does not expose MCP prompts, resources, logging, or subscription streams. OAuth uses an authorization-code flow with Client ID Metadata Documents. The MVP does not issue refresh tokens and does not support DPoP, dynamic client registration, introspection, token revocation endpoints, userinfo, or OIDC metadata. Project-secret bearer authentication remains available.

​
Troubleshooting

For OAuth, run your client’s login again. The eight-hour grant may have expired or an organization owner may have revoked it. For a project secret, check the Authorization: Bearer pk_… header and do not use a publishable key (pk_pub_…).
Your client speaks an older MCP revision. The error names the revision we support; update the client to a build that speaks 2026-07-28.
You are connected to https://galinum.com/mcp/readonly. Switch to https://mcp.galinum.com/mcp to create, update, or launch.
Replace https://galinum.com/mcp with https://mcp.galinum.com/mcp. The old full endpoint has no redirect or compatibility route.